-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
awesome-flake8-extensions
:octocat: A curated awesome list of flake8 extensions. Feel free to contribute! :mortar_board:
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Many codebases are using `black` as an opinionated code-formatter. Other tools that go well with it are `autoflake`, `flake8`, `isort` (they all need a little config to play nice together). A good way to run these linters is as a git pre-commit hook. There are a number of tools that help manage those, one I've used is https://pre-commit.com/. This means that the linters run locally and prevent committing un-linted code.
Recommend using a code formatter with this, such as black! Automatically formats everything for you each time you commit and makes sure you don't commit unformatted code.
And if you're using flake8, make sure to check out its plugins. Here's a good list: https://github.com/DmytroLitvinov/awesome-flake8-extensions
I recommend Poetry -- it fixes a lot of the issues that I have had with pipenv. For example, Poetry has sane environment identification, doesn't arbitrarily remove features, works with pyenv, has maintainers that care and are active, and actually follows PEP 518 (which pipenv blatantly ignores). Also bonus points that poetry has never had Reitz's grubby hands on it if you care about that sort of thing.
Related posts
-
How to setup Black and pre-commit in python for auto text-formatting on commit
-
Packaging Python projects in 2023 from scratch
-
Automate Python Linting and Code Style Enforcement with Ruff and GitHub Actions
-
How do you go about a PR as a Senior Developer?
-
Chatting with Sebastian Witowski - Part I: Code Standards, Tooling, and Working in Teams