Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I might not be following: what would that protocol entail? pyx uses the same PEP 503/691 interfaces as every other Python index, but those interfaces would likely not be immediately useful to PyPI itself (since it already has them).

> or is one simply paying for access to Astral's particular server that runs it?

pyx is currently a service being offered by Astral. So it's not something you can currently self-host, if that's what you mean.



> pyx uses the same PEP 503/691 interfaces as every other Python index

... Then how can it make decisions about how to serve the package request that PyPI can't? Is there not some extension to the protocol so that uv can tell it more about the client system?


The repository API allows server-driven content negotiation[1], so pyx can service specialized requests while also honoring the normal 503/691 ones.

[1]: https://packaging.python.org/en/latest/specifications/simple...


Interesting. I'll have to look into this further. (I've bookmarked the entire thread for reference, especially since I'm a bit attached to some of my other comments here ;) )


Ah.

> honoring the normal 503/691 ones.

Embrace

> pyx can service specialized requests

Extend

... ;)


Snark aside, you're missing the part where pyx doesn't compete with PyPI. It's a private service.


How does it being private mean it doesn't compete with PyPI?


Its purpose is to serve as a repo for stuff that was never going to go on PyPI, whether or not PYX exists.


Oh, I see, I misunderstood the use of the word "private" there.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: