211–215 of 215 posts
Earlier quoted context omitted.
The leadership was that the science community would benefit from a science-specific tool, like Conda, and that making one ring to rule them all would be too difficult. Also, yes, Guido and many other early contributers have been been active for 30ish years.
Conda isn't really science specific, just like pip isn't webdev specific.
Earlier quoted context omitted.
I sympathize. It is unfortunate that the python community never settled around a tool like leiningen for clojure or cargo for rust or npm for node. What we saw with npm was the entire community iterating towards a feature set and everyone reaping the benefits automatically with npm updates. package-lock.json is a good example of this.
I think the Python community have largely settled on pip, just like the JavaScript community have mostly opted for npm. Personally I much prefer pip over npm, it feels much more polished.
Just use Poetry [1]. It's popular and works well. [1] https://python-poetry.org/
Earlier quoted context omitted.
Where is there a comprehensive poetry packaging tutorial?
Right here: poetry build -f wheel poetry publish You asked for packaging, and that is pretty much it. Of course, setting up a project and its dependencies take a bit more work; the basic intro for that is here: https://python-poetry.org/docs/basic-usage/