Hypermodern Python
I don&#x27;t see what&#x27;s modern about it.<p>Those tools have been existing for years, and as always with Python, they serve only a subset of the Python users.<p>Not that it&#x27;s a bad article. If you don&#x27;t know about them, give it a read, it&#x27;s good to know it exists and the post is well written.<p>But don&#x27;t think it&#x27;s the ultimate stack or whatever.<p>And if you learn Python, you should always strive to master the basics first:<p>- installing python.org for windows and mac, or apt&#x2F;yum on Linux (those ones are tricky, it&#x27;s more than just the &quot;python&quot; package to get pip and venv)<p>- don&#x27;t try to get the latest and greatest version (which is 3.8, or 3.9 alpha today). 3.6 is great already and is wildly available. I personnally strive for 3.7 now, but I&#x27;m happy with 3.6 if I don&#x27;t have to use asyncio. So get the most modern version that is easy to install for you.<p>- be comfortable with &quot;-m&quot;, the &quot;py&quot; command on windows, &quot;pip&quot; (-m, --user, install, install -r, freeze), and &quot;-m venv&quot;.<p>- make sure you understand what the PYTHON PATH is and how it works regarding the import system<p>- know how to configure your favorite editor to work with those<p>Once you have those basics, you can go and try whatever have you: peotry, pyenv, pew, virtualenvwrapper, pipenv and so on. It will be easy because you will have a solid understanding of where it comes from and how it plugs in into the ecosystem. You will be able to chose if they are worth it or not for you. And more importantly, when you will have to move away from them (because of work, because they don&#x27;t suit you, because they are abandonned...), you will always be able to fall back to basics.<p>But franckly, there are so many things that you should be learning before those extras: pdb, black, pylint, zipapps... Or even concepts like generators, decorators, unpacking, etc. They all have a better value for the time you spend on them than learning a new &quot;modern&quot; stack.<p>Not that it&#x27;s not useful to have a modern stack. I update my stack all the time.<p>I&#x27;m currently using pip + pew + doit + nox + pytest, and I&#x27;m experimenting with dephell.<p>But it&#x27;s my full time job. I&#x27;m an expert.<p>Most Python devs have a much limited amount of resource to spent in learning stuff. They have deadlines, and other stuff to care about than Python.<p>I know because I go from company to administrations to students to train them, and it&#x27;s always the same: they chose Python because it&#x27;s an efficient use of their time.