PYX: The next step in Python packaging
1–10 of 479 posts
Re: PYX: The next step in Python packaging
#2Probably the more useful blog post: https://astral.sh/blog/introducing-pyx
Re: PYX: The next step in Python packaging
#3[flagged]
Re: PYX: The next step in Python packaging
#4Been waiting for something like this to make it easier to manage multi-package projects.
Re: PYX: The next step in Python packaging
#5Been waiting to see what Astral would do first (with regards to product). Seems like a mix of artifactory and conda? artifactory providing a package server and conda trying to fix the difficulty that comes from Python packages with compiled components or dependencies, mostly solved by wheels, but of course PyTorch wheels requiring specific CUDA can still be a mess that conda fixes
Re: PYX: The next step in Python packaging
#6Pyx is just a registry, just like Pypi, or did I misunderstood it?
Re: PYX: The next step in Python packaging
#7Been waiting to see what Astral would do first (with regards to product). Seems like a mix of artifactory and conda? artifactory providing a package server and conda trying to fix the difficulty that comes from Python packages with compiled components or dependencies, mostly solved by wheels, but of course PyTorch wheels requiring specific CUDA can still be a mess that conda fixes
Given Astral's heavy involvement in the wheelnext project I suspect this index is an early adopter of Wheel Variants which are an attempt to solve the problems of CUDA (and that entire class of problems not just CUDA specifically) in a more automated way than even conda: https://wheelnext.dev/proposals/pepxxx_wheel_variant_support...
Re: PYX: The next step in Python packaging
#8As I said a couple weeks ago, they're gonna have to cash out at some point. The move won't be around Uv -- it'll be a protected private PyPi or something.
https://news.ycombinator.com/item?id=44712558
Now what do we have here?
Re: PYX: The next step in Python packaging
#9I wonder whether it will have a flat namespace that everyone competes over or whether the top-level keys will be user/project identifiers of some sort. I hope the latter.
Re: PYX: The next step in Python packaging
#10I've been burned too many times by embracing open source products like this.
We've been fed promises like these before. They will inevitably get acquired. Years of documentation, issues, and pull requests will be deleted with little-to-no notice. An exclusively commercial replacement will materialize from the new company that is inexplicably missing the features you relied on in the first place.