3 ms·
Context is important. Developing applications vs libraries vs scripts is different, developing internal company software vs external software is different. If
by greenshackle2 6y ago
Context is important. Developing applications vs libraries vs scripts is different, developing internal company software vs external software is different.
If you're shipping a package on pypi, you will want to develop and automatically test using multiple Python versions and maybe a range of versions of your dependencies. Having good tools to manage multiple sets of Python versions and dependencies and parallel automated testing is a godsend.
If you're writing an internal or web application that will run only in a single well-known environment, pip + venv + pytest might well be good enough.
- BiteCode_dev 6y agoSure, but again, there is nothing modern about this. And certainly not, hyper modern. Besides, if you want to develop and automatically test using multiple Python versions and a range of versions of your dependencies, none of the tools from the article will do it. At best they are one of the ways to get dependancies before you use a tool to do it. You can do that with raw pip and venv as well. What you need though, is something like tox, which has existed for years. As mentioned in my comment, I personnally use nox for this, as it is, ironically, more modern to my taste. Nox doesn't care if you use poetry, pew, virtualenv wrapper or venv manually. I would certainly advice to learn something like nox or doit before learning poetry, for example. Now I don't advice against learning poetry, mind you. It's a good tool, well written. Pyenv is another matter entirely. The day one really need what pyenv gives you to the point it's worth investing in it, they can discard all my advices entirely, as they would have the skill and experience to not need my explanations.
- greenshackle2 6y agoNot sure if you've read just the first article, it's a whole series, they cover nox later on. I don't see how this stack is "hypermodern" either, mind you. My point was just that these articles and other like it tend to omit context completely. What is this stack good for? Who should use it? Who shouldn't? Without answering these questions the articles are not all that useful, or even could be harmful, if a dev who doesn't know better apes a complicated stack for no good reason.
- BiteCode_dev 6y agoI missed that it was serie, indeed.