19 ms·
I find myself coming back to this guide whenever I set up a new project: https://sourcery.ai/blog/python-best-practices/ https://sourcery.ai/blog/python-best-pr
by buschkowitz 7y ago
I find myself coming back to this guide whenever I set up a new project: https://sourcery.ai/blog/python-best-practices/ https://sourcery.ai/blog/python-best-practices/
- calpaterson 7y agoA general ignore_missing_imports=True in mypy.ini is very bad advice. This will hide lots of real errors. It's surprisingly easy to set up mypy such that it will silently not check types in many files. Additionally I can't be the only person who utterly despises pipenv. It is confusing for most people who don't know python packaging internals, phenonomially slow for everyone else and besides discourages building proper distributables (or:wheels).
- greymalik 7y agoWhat do you do instead of pipenv?
- calpaterson 7y agoPipenvs attempts to replace all other tooling to the answer is: all other tooling. Specifically, setuptools via either setup.py or setup.cfg. pbr, virtualenvs, tox, pip-tools, pip, etc are all useful. Anything that does not take 5-10 minutes to recompute dependencies basically!
- buschkowitz 7y agoThat is a big weakness, I agree. But the mental tax of having to remember how to use >5 cli tools vs one is definitely pro pipenv for me.