Oh finally.
The news on this is mixed. “All the tool authors have signaled they can and would implement the PEP as an export format,” said Cannon, but that does not mean they would adopt it as their sole lock file format. The creator of uv, Charlie Marsh, said that “today, the PEP 751-style pylock.toml files are not sufficient to replace uv.lock,” but that support will be added for export.
This sounds little better then “here is 13th standard” even though it’s not feature full.
nah, the main reason we have 15 standards was the lack of an official one. This is good.
congrats python, you’re 20 years late…again…
python is the IE of programming languages
Python EEE incoming!!!
Viva la package dependencies!
Does it do away with setuptools? After my experience interacting with the maintainers, now refer to that package as, The Deep State
The Deep State only supports loading dependencies from pypi.org Which has many advantages right up until it doesn’t.
This new standard contains dependency host url. Hope there is a package other than setuptools that supports it.
When bring it up, and prove it, the responses alternate between playing dumb and gaslighting. The truth is The Deep State are gate keepers. And they are in the way.
Training wheels off mode please! So there is support for requirements files that contain on which server dependencies are hosted with more than one choice. Would like the option to host packages locally or remotely using pypiserver or equivalent.
On the positive side, setuptool maintainers did not suggest voodoo dolls, try to wait out the planetary alignment, better economic conditions, or peace on Earth.
That’s how the conversation comes off to my eyes. But form your own opinion. Especially enjoyable for folks who also enjoyed the TV series, The Office.
What are the alternatives to being stonewalled by setuptools?
Disclosure: Wrote requirements rendering package, wreck. I have my own voodoo dolls and plenty of pins
Have you tried hatch?
I don’t know why people are still bothering with setuptools for new projects.
From the hatch docs, not seeing where it discusses publishing to alternative package warehouses.
AFAIK setuptools and hatch are for building. Publishing is a different process. You can try
uvfor publishing, but idk if it supports publishing to alternatives to PyPI.
Will look at it again
I really don’t understand what you are complaining about. There has been a “training wheels off I want to do things manually” option for ages.
https://stackoverflow.com/questions/16584552/how-to-state-in-requirements-txt-a-direct-github-source
How is this different from regular dependencies?
Here I am still using requirements.txt and the built in venv. Sure poetry looks cool. I just don’t have it everywhere. Now I just have to wait 5 years before I can reliably use a pylock.toml. Progress!
