Astral took over python-build-standalone, and uv uses its custom Python builds in deployments.
I do not want OpenAI putting their fingers in my Python binaries, nor do I want their telemetry.
Astral to Join OpenAI
811–820 of 951 posts
Re: Astral to Join OpenAI
#812A concern: More and more plainly, OpenAI and Anthropic are making plays to own (and lease) the "means of production" in software. OK - I'm a pretty happy renter right now. As they gobble up previously open software stacks, how viable is it that these stacks remain open? It seems perfectly sensible to me that these providers and their users alike have an interest in further centralizing the dev lifecycle - eg, if Clau…
It's even worse than that, Astral took over python-build-standalone and uv uses its Python builds on all platforms.
That means OpenAI will be able to do whatever they want to your Python binaries, including every Python binary in your deployments, with whatever telemetry that want to instrument in the builds.
Re: Astral to Join OpenAI
#813Earlier quoted context omitted.
Private package hosting sounds like a commodity that would be hard to differentiate.
It's also a crowded and super mature space space between JFrog (Artifactory) and Sonatype (Nexus). They already support private PyPI repositories and are super locked in at pretty much every enterprise-level company out there.
I've used JFrog Artifactory before and I wish I didn't.
Re: Astral to Join OpenAI
#814Earlier quoted context omitted.
Sure, but if tomorrow uv and ruff ceased to exist, we could all go back to any number of other solutions.
Ruff is nice, but not important, uv is one of the few things making the python ecosystem bearable. Python is a language for monkeys, and if you don't give monkeys good tools, they will forever entangle themselves and you . It is all garbage wrapped in garbage. At least let me deploy it without having to manually detangle all that garbage by version. I'm done pretending this is a "right tools for the right job" kind o…
uv is nice, but not irreplaceable. An open source, maintenance mode fork would work just as fine. And even if all of uv disappeared today, I’d go just back to Poetry. Slower? Sure, a bit.
...and then I’ve read the rest of your comment. Please do go read the HN guidelines.
Re: Astral to Join OpenAI
#815This is feeling weird, like now if the AI bubble pops it will bring core technologies like runtimes (bun) and package managers (astral)
now what's next? vite?
Re: Astral to Join OpenAI
#816Earlier quoted context omitted.
Python existed for years before uv with a huge ecosystem, and will continue to do so after/if it dies
uv, yes*, but really PEP 723: https://peps.python.org/pep-0723/ * disclosure: We are a commercial client of astral.sh
It’ll probably be a game changer for scripts, yes. Writing “portable” Python scripts was a nice exercise, though (and will be, for a while).
Re: Astral to Join OpenAI
#817Earlier quoted context omitted.
I agree uv is great but let’s not get carried away here. Poetry is good, pip was fine for many use-cases after they added native lock files.
if you are working on one tiny project on your machine that pips in four packages you probably think pip was OK. Circa 2017 I was working on systems that were complex enough that pip couldn't build them and after I got to the bottom of it I knew it not my fault but it was the fault of pip. I built a system which could build usable environments out of pre-built wheels and sketched out the design of a system that was r…
> everybody else was blaming themselves for a problem and didn't have a clear understanding of what was wrong with pip or what a correct model for managing python dependencies is (short answer: see maven)
I always looked down on the Java ecosystem but if it turns out Maven had a better story all along and we all overlooked it, that's wild.
Re: Astral to Join OpenAI
#818Earlier quoted context omitted.
relax, soon u be rewriting the essence of all these libs into something new. python has its days numbered also perhaps for many engineering decisions that are now cheap via llms.
The LLMs write bad python as easily as any other language. To make it good, you need to review and interate.
I think this means reviewing is the main thing with AI, and therefore the language to use should be one where reviewing is easy, for humans.
Re: Astral to Join OpenAI
#819Earlier quoted context omitted.
Also, Microsoft does not allow use of their LSP for python. You have to use the barebones Jedi LSP.
Fortunately, there are competing LSPs of reasonable quality now. I'm using pyrefly. Not sure if ty/ruff have one too.
Did not know about this, thanks. Now I don't have to do half of my development in Zed and half in VSCodium :)
Re: Astral to Join OpenAI
#820Earlier quoted context omitted.
How is uv awesome and Poetry so bad? They do basically the same things except Astral re-invents the wheel but only part way instead of just relying on the existing tools. uv is fast. As far as I can tell, there's hardly any difference in functionality except for it also replacing PyEnv, which I never use anyway.
uv has a lot of sensible defaults that prevent clueless developers to shoot their own feet. Uv sync, for example, would uninstall packages not in pyproject.toml
i kind of disagree with this. uv run is clunky, i don't want that. i want to keep the activate the venv and do shit model. i hate uv run as a primitive.