3 ms·
I was wondering why they are going in about pipenv? I was reading the instructions on the python packaging guide [1] (which the author is referring to as we) an
by 0x008 5y ago
I was wondering why they are going in about pipenv? I was reading the instructions on the python packaging guide [1] (which the author is referring to as we) and by following the instructions word by word I was able to publish my package without having to touch anything other than pip and twine.
The author repeats this experience so I wonder why pipenv is out in the spotlight here?
[1] http://packaging.python.org/tutorials/packaging-projects.html http://packaging.python.org/tutorials/packaging-projects.htm...
- deleted 5y ago[deleted]
- atoav 5y agoAs someone who uses both python and Rust what I want is basically cargo but for python. So a solution that easily lets you create, run, build, publish, install python packages or software — something that has dependency managment and testing built in and is extendable with extra modules. Stuff that every python dev needs to do a hundred times a month. Poetry comes close but it is quirky at times, and it isn't the official standard. I understand that everything I mentioned would also be possible with the standard tools, but I don't get why the things nearly every python dev has to deal with were designed to be so convoluted, so developer-unfriendly, so unpythonic. Good tooling like this is not only about comfort and ease of entry, it is also a way to encourage best practise.