Live data from Hacker News

PYX: The next step in Python packaging

astral.sh

241–250 of 479 posts

Re: PYX: The next step in Python packaging

#241
post #55

Is there a big enough commercial market for private Python package registries to support an entire company and its staff? Looks like they're hiring for $250k engineers, starting a $26k/year OSS fund, etc. Expenses seem a bit high if this is their first project unless they plan on being acquired?

Ask Docker how that worked out.

Re: PYX: The next step in Python packaging

#242
post #39

I'm brushing up with Python for a new job, and boy what a ride. Not because of the language itself but the tooling around packages. I'm coming from Go and TS/JS and while these two ecosystems have their own pros and cons, at least they are more or less straightforward to get onboarded (there are 1 or 2 tools you need to know about). In Python there are dozens of tools/concepts related to packaging: pip, easy_install,…

Python gained popularity in academic circles because it was easy, not because it was good.

Its a pain in the ass to work with professionally.

Re: PYX: The next step in Python packaging

#243
post #234

The real pyx is an absolutely wonderful graphing package. It's like Tex in that everything looks wonderful and publication-quality. https://pyx-project.org/gallery/graph/index.html

there's something about these comments ("name-collision") that drives me up the wall. do y'all realize multiple things can have the same name? for example, did you know there are many people with exactly the same names: https://www.buzzfeed.com/kristenharris1/famous-people-same-n... and yet no one bemoans this (hospitals don't consult name registries before filling out birth certificates). that's because it's almost…

Human naming has nothing to do with software naming which seems obvious but apparently not. Python package creators should check the pypi registry for names and generally avoid name collisions where reasonable. Common sense applies for reduced confusion for users globally and also for potential legal issues if any party trademarks their software name. What makes one pyx more real than the other is one was first and took the spot on pypi. Simple as that. https://pypi.org/project/PyX/

Re: PYX: The next step in Python packaging

#244
post #127

Earlier quoted context omitted.

Thanks that’s bit less cryptic than the linked page. Still don’t get how they are solving what they claim to solve.

I'm guesssing from the UV page [0] its mainly if the speed of pip is a problem for you? [0] https://docs.astral.sh/uv/

I'm guessing it's the right PyTorch and FlashAttention and TransformerEngine and xformers and all that for the machine you're on without a bunch of ninja-built CUDA capability pain.

They explicitly mention PyTorch in the blog post. That's where the big money in Python is, and that's where PyPI utterly fails.

Re: PYX: The next step in Python packaging

#245

Earlier quoted context omitted.

Ah interesting, thanks for that! I was frustrated once again recently to note that `pip install --dry-run` required me to pre-download all packages, so I assumed nothing had changed.

You could do worse than to start using --only-binary=:all: by default. (It's even been proposed as default behaviour: https://github.com/pypa/pip/issues/9140 ) Even if you can't actually install that way, it will point out the places where sdists are needed. In principle, separate metadata availability should still at least be possible for most sdists eventually . But I'm not the one calling the shots here.

For clarity, if I do

    pip install -r requirements.txt --dry-run --only-binary=:all:`
Should I expect that to download only metadata and not whole wheels/sdists for everything? Or does that depend on everything in my requirements file being available as a wheel?

Re: PYX: The next step in Python packaging

#246

All python packaging challenges are solved. Lesson learned is that there is not a single solution for all problems. getting more strings attached with VC funded companies and leaning on their infrastructure is a high risk for any FOSS community.

Try doing CUDA stuff. It's a chemical fire. And the money would make solving it would fund arbitrary largesse towards OSS in perpetuity.

Re: PYX: The next step in Python packaging

#247
post #212

Earlier quoted context omitted.

You can turn that off and allow global packages again if you want. Or install it with the os package manager or something simmilar

You assume the OS package manager I happen to be using even has packages for some of the libraries I want to use.

Nothing about their post indicated they assumed that.

They offered two options, so you can go do the other one if it doesn't work for you.

Re: PYX: The next step in Python packaging

#248

Earlier quoted context omitted.

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?

Re: PYX: The next step in Python packaging

#249

Earlier quoted context omitted.

You assume the OS package manager I happen to be using even has packages for some of the libraries I want to use.

Nothing about their post indicated they assumed that. They offered two options, so you can go do the other one if it doesn't work for you.

[dead]

Re: PYX: The next step in Python packaging

#250
post #28

Earlier quoted context omitted.

For what it's worth, I understand this concern. However, I want to emphasize that pyx is intentionally distinct from Astral's tools. From the announcement post: > Beyond the product itself, pyx is also an instantiation of our strategy: our tools remain free, open source, and permissively licensed — forever. Nothing changes there. Instead, we'll offer paid, hosted services that represent the "natural next thing you ne…

The entire reason people choose "permissive licenses" is so that it won't last forever. At best, the community can fork the old version without any future features. Only viral licenses are forever.

This is just plain false and honestly close-minded. People choose permissive licenses for all sorts of reasons. Some might want to close it off later, but lots of people prefer the non-viral nature of permissive licenses, because it doesn't constrain others' license choice in the future. Still others think that permissive licenses are more free than copyleft, and choose them for that reason. Please don't just accuse vast groups of people of being bad-faith actors just because you disagree with their license choice.
Post reply on HN