Python now has a standard package lock file format – though winning full adoption will be a challenge
Python now has a standard package lock file format – though winning full adoption will be a challenge • DEVCLASS
nah, the main reason we have 15 standards was the lack of an official one. This is good.
Python EEE incoming!!!!
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
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
Have you tried hatch?
I don't know why people are still bothering with setuptools for new projects.
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!
i love requirements files, venv, and pyenv.
Bringing requirements into pyproject.toml does not have enough value add to bother with. My requirements files are hierarchical. Extensively using -r and -c options AND venv aware.
pep751 does bring value, by stating both the host url and the hash of every package.
setuptools will fight this to continue their strange hold on Python
How is this different from regular dependencies?
Regular dependencies lack host url and hashes. Those are most important.
For the full details, encourage you to read pep751
^^ look a link! Oh so clickable and tempting. Go ahead. You know that pretty blue font-color is just asking for it. And after clicking the font-color changes colors. Wonder what font-color it'll become? Hmmmm
wreck 0.3.4.post0 no longer emits build front end options into .lock files wreck#30.
Background of efforts to beg and plead for setuptools maintainers to bend ever so slightly.
Continuing from denied way to pass build front end options thru requirement files so know non-pypi.org hosts setuptools#4928
This hurts those hosting packages locally or remotely on non-pypi.org package index servers. For those who are, the packages themselves give no clue where the dependencies and transitive packages are hosted.
Each and every user would need to have a ~/.pip/pip.conf or pass --extra-index-url pip install cli option. And somehow know all the possible package index servers.
This allows the pypi.org cartel to continue along it's merry way unimpeded.
Wish pep751 good luck and may there be a .unlock equivalent. Do not yet understand how the pep751 implementers will bypass setuptools and build.
Oh finally.
This sounds little better then "here is 13th standard" even though it's not feature full.