News for hackers. Stuff that matters.
Re:Trying Out Rye by adamgordonbell on Friday April 12, 2024 @08:16AM (#40011706)
Wouldn't the whole python world be better if the Python Steering Council made it known it intended to standardize on Rye/Hatch/Poetry or whatever.

Choosing anything, stating that out-loud and slowly forcing convergence would benefit all.

Lot's of options are great to explore the solution space, but it feels like we are way past that.

Re:Trying Out Rye by IshKebab on Friday April 12, 2024 @11:45AM (#40014211)
It absolutely would. But there are many many things that would make the Python world better that the Python developers seem generally oblivious to so I wouldn't hold your breath.

Probably a little early to officially bless Rye though anyway.

Re:Trying Out Rye by ploxiln on Friday April 12, 2024 @11:48AM (#40014242)
pip and venv are officially sanctioned. (venv and "ensure-pip" are included in python-3.x) That's all you really need (after you have the desired version of python).
Re:Trying Out Rye by lambdaxyzw on Friday April 12, 2024 @05:11PM (#40017701)
I have never used anything other than pip and venv. Maybe I'm missing something, but I never felt like I'm missing anything. And Python package management is so easy and simple if you stick to that (well, except version conflicts, but that's always a pain somehow).
Re:Trying Out Rye by adamgordonbell on Saturday April 13, 2024 @10:37AM (#40023428)
If you use pip and requirements.txt, the dependency resolution is not great, it just installs things in order.

There isn't a lock file. How do you deal with dev dependencies? How do you work on a lib and its calling code without pushing it to pypa? Working with c deps?

All this stuff feels harder to do then it should be.

Re:Trying Out Rye by ploxiln on Monday April 15, 2024 @06:25PM (#40046403)
1) dev-requirements.txt

2) pip install . (optionally with -e)