There should be an article like this for every language, as the author mentions it's not just syntax to change a language. Much of it is experience based knowle

There should be an article like this for every language, as the author mentions it's not just syntax to change a language. Much of it is experience based knowledge. However, this is how you would setup for a new project only and in a piecemeal manner, if you didn't already have some existing template. Compatibility issues with your main dev tool would rule out using Poetry, in the same way running the latest versions of any software without reason is a rookie mistake. Chasing a higher version number is a jr / intermediate folley. If you're developing python professionally, save your money and just pay for pycharm. The morning of fluffing with a dozen new tools which then have their own maintanence overheads is less cost effective than buying a product that gives you >70% of what the author has recommended and it does so in a generally consistent manner. This blog post was a great reminder of how much pycharm gives me on a day to day basis, how people get lost in their +1 more tool mindset and how switching languages is an intial cognitive overload.