Was this note at the bottom not there earlier? It seems to me like a clear enough disclaimer.
Please note: this code is shared to show the algorithm, not as a drop-in application that just runs. It depends on two private modules configmanners and Points. Both of these are on git hub, but to put them upload them to pip would be to commit to supporting them in perpetuity. I'm not willing to do that.
This is a valid criticism of the Python community and something the core language maintainers should look to address.
Working in Python in the 2000s, I was extremely happy. Working in Python (especially ML and data science applications) in the 2020s is a nightmare. The world has come a long way, and Python has actually taken a backslide.
Python would do well to learn from the Rust project and their Cargo package manager and tooling.
> This is a valid criticism of the Python community and something the core language maintainers should look to address.
The author didn't include one of his custom source libraries that's not needed to understand the code, so that makes this a valid criticism of the Python community? lol
The code shouldn't build, go green, or be in any shareable state. This is horrifically bad practice.
A language should remove all of these thorns in a first-class manner.
Until you use a package manager like Cargo, you probably can't intuit the wide gulf here. A good analogy might be imagining the world before version control.
Dependency control matters immensely. Hermeticity and repeatability matter immensely. We should strive to build these into the very foundations.
Please note: this code is shared to show the algorithm, not as a drop-in application that just runs. It depends on two private modules configmanners and Points. Both of these are on git hub, but to put them upload them to pip would be to commit to supporting them in perpetuity. I'm not willing to do that.