mirrors-mypy
LocalStack
mirrors-mypy | LocalStack | |
---|---|---|
4 | 154 | |
243 | 52,145 | |
1.6% | 0.7% | |
5.3 | 9.9 | |
7 days ago | 6 days ago | |
Python | Python | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mirrors-mypy
-
How I start every new Python backend API project
repos: - repo: https://github.com/pre-commit/pre-commit-hooks rev: v4.3.0 hooks: - id: trailing-whitespace - id: check-merge-conflict - id: check-yaml args: [--unsafe] - id: check-json - id: detect-private-key - id: end-of-file-fixer - repo: https://github.com/timothycrosley/isort rev: 5.10.1 hooks: - id: isort - repo: https://github.com/psf/black rev: 22.8.0 hooks: - id: black - repo: https://gitlab.com/pycqa/flake8 rev: 3.9.2 hooks: - id: flake8 - repo: https://github.com/pre-commit/mirrors-mypy rev: v0.971 hooks: - id: mypy args: [ --warn-unused-configs, --ignore-missing-imports, --disallow-untyped-defs, --follow-imports=silent, --install-types, --non-interactive ]
-
Should I follow the warnings in Pycharm? Does anyone do this?
repo: https://github.com/pre-commit/mirrors-mypy rev: v0.961 hooks:
-
Error: Cannot find implementation or library stub for module named "pytest" when run from pre-commit
default_language_version: python: python3.10 default_stages: [commit, push] repos: #... Other hooks - repo: https://github.com/pre-commit/mirrors-mypy rev: v0.961 hooks: - args: ["--verbose"] description: Type checking for Python id: mypy
-
Python Code Quality - Improve the quality of your Python code with linters, code formatters, and security vulnerability scanners
yaml repos: - repo: https://github.com/myint/autoflake rev: v1.4 hooks: - id: autoflake args: - --in-place - --remove-all-unused-imports - --expand-star-imports - --remove-duplicate-keys - --remove-unused-variables - repo: https://github.com/asottile/pyupgrade rev: v2.29.0 hooks: - id: pyupgrade args: [--py36-plus] - repo: https://github.com/PyCQA/isort rev: 5.9.3 hooks: - id: isort - repo: https://github.com/psf/black rev: 21.10b0 hooks: - id: black args: [--safe, --quiet] - repo: https://github.com/PyCQA/flake8 rev: 4.0.1 hooks: - id: flake8 - repo: local hooks: - id: pylint name: pylint entry: pylint language: system types: [python] args: [ "-rn", "-sn", ] - repo: https://github.com/pre-commit/mirrors-mypy rev: v0.910-1 hooks: - id: mypy name: mypy entry: mypy language: python types: [python] args: [] require_serial: true - repo: https://github.com/pre-commit/mirrors-prettier rev: v2.4.1 hooks: - id: prettier args: [--prose-wrap=always, --print-width=88]
LocalStack
- LocalStack – a functional local AWS cloud stack
-
Let's build a screenshot API
Later you can use any S3 compatible storage because the code I write will still work, but for testing purposes on my local machine, I will use LocalStack:
-
LocalStack e AWS CLI: Como desenvolver localmente com a AWS
Acesse o site da LocalStack e faça login.
-
Cutting down AWS cost by $150k per year simply by shutting things off
To give this a slightly different spin:
--> "The best optimization is simply not spinning things up."
At least for local development and testing, as made possible by LocalStack (https://localstack.cloud), among other local testing solutions and emulators.
We've seen so many teams fall into the trap of "someone forgot to shut down dev resource X for a week and now we've racked up a $$$ bill on AWS".
What is everyone's strategy to avoid this kind of situation? Tools like `aws-nuke` (https://github.com/rebuy-de/aws-nuke) are awesome (!) to clean up unused resources, but frankly they should not be necessary in the first place.
-
Getting Amazonka S3 to work with localstack
(For others who hadn't heard of it: localstack is
- LocalStack v3.0.0
- Localstack, a "AWS" local para desenvolvimento em cloud
-
Integration tests with AWS S3 buckets using Localstack and Testcontainers
LocalStack Website
- LocalStack: A functional local AWS cloud stack
-
Simulando a AWS no seu ambiente Local
O Localstack: https://localstack.cloud/, é um recurso que possibilita simular diversos recursos AWS (dynamoDB, s3, iam, cognito, ses), dentro da sua máquina, utilizando o docker.
What are some alternatives?
autoflake - Removes unused imports and unused variables as reported by pyflakes
Moto - A library that allows you to easily mock out tests based on AWS infrastructure.
pyupgrade - A tool (and pre-commit hook) to automatically upgrade syntax for newer versions of the language.
sst - Build modern full-stack applications on AWS
mirrors-prettier - mirror of the `prettier` npm package for pre-commit
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
flake8
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
reorder-python-imports - Rewrites source to reorder python imports
eks-anywhere - Run Amazon EKS on your own infrastructure 🚀
isort - A Python utility / library to sort imports. [Moved to: https://github.com/PyCQA/isort]
Appwrite - Build like a team of hundreds_