While I think your concern is a bit overblown, I would concur that tooling is a Python gap. Not because there is any big deficiency in what they can do to manage a project, but because there are just too many options. There is no blessed workflow.
The Python leadership has refused to take a stance on picking a winner. The power vacuum has lead to multiple competing tools, which all do things a little differently.
I have taught Python to a few people and the initial ramp up is embarrassing. I cannot point to a guide on Python.org that says This Is The Way(TM). Instead, I have to give an opinionated workflow full of caveats on how to setup an environment, because there is no “correct” way to get started.
I really do not care who wins. I have had to adopt and transition many packages over the years. Just pick something.
The Python leadership has refused to take a stance on picking a winner. The power vacuum has lead to multiple competing tools, which all do things a little differently.
I have taught Python to a few people and the initial ramp up is embarrassing. I cannot point to a guide on Python.org that says This Is The Way(TM). Instead, I have to give an opinionated workflow full of caveats on how to setup an environment, because there is no “correct” way to get started.
I really do not care who wins. I have had to adopt and transition many packages over the years. Just pick something.