Codex maker says it will "continue to support these open source projects" after deal closes.
See full article...
See full article...
I'm guessing that a fair amount of stuff around AI (be it agentic, bots, tools, APIs, MCPs) are being built with Python due to the relative ease. People use uv for the convience of having virtual environments and a lot of the tooling and packaging that it brings to the Python ecoysystem.Seriously? Astral's tools aren't even AI-focused, and now they're tied to a company that's losing money hand over fist?
I view building tools as an incredibly high-leverage endeavor. As I wrote in our launch post three years ago: "If you could make the Python ecosystem even 1% more productive, imagine how that impact would compound?"
Today, AI is rapidly changing the way we build software, and the pace of that change is only accelerating. If our goal is to make programming more productive, then building at the frontier of AI and software feels like the highest-leverage thing we can do.
It is increasingly clear to me that Codex is that frontier. And by bringing Astral's tooling and expertise to OpenAI, we're putting ourselves in a position to push it forward. After joining the Codex team, we'll continue building our open source tools, explore ways they can work more seamlessly with Codex, and expand our reach to think more broadly about the future of software development.
Through it all, though, our goal remains the same: to make programming more productive. To build tools that radically change what it feels like to build software.
Maybe it's small potatoes, but FOSS naming in general is a tire fire. Every package or project is seemingly designed to be as comprehensively unsearchable as possible.Only tangentially related, but it annoys me every time I see the uv package manager because they chose a name that very much conflicts with the libuv asynchronous I/O event loop, which (at least historically) had a reasonable amount of prevalence even in python. Always confuses me.
There are companies who I trust slightly further than I can throw them. Honeywell, to pick one example, may be a little staid and stodgy, but they've been making thermostats for a good long while now. I bet they'll treat their thermostat business as not-google-killable five or twenty years hence.Trying to figure on a good number to represent a value greater than 0, but not quite 1%.
and then assign that number to the confidence % I put in any corporate promises.
From the Charlie Marsh announcement:
Is this money talking, or is he honest? I know this has historically been a very AI skeptical forum, but it seems that the sentiment around coding assistants have swung quite a bit during 2026. And if you truly believe in this being the future, continuing to build tools directly for humans doesn’t really make that much sense when AIs are doing most of the coding.
That's ok, I'm sure it won't do any harm to the software ecosystem when the bubble bursts. Right?Seriously? Astral's tools aren't even AI-focused, and now they're tied to a company that's losing money hand over fist?
No but python is the dominant language in AI development, from creating the models to tuning them to agentic apps.Seriously? Astral's tools aren't even AI-focused, and now they're tied to a company that's losing money hand over fist?
Trying to figure on a good number to represent a value greater than 0, but not quite 1%.
and then assign that number to the confidence % I put in any corporate promises.
Boarding the Titanic...
Winning posts.Time to fork all those projects
I would say that 0 seems to be fine.Trying to figure on a good number to represent a value greater than 0, but not quite 1%.
and then assign that number to the confidence % I put in any corporate promises.
Boarding the Titanic...
That may be what OpenAI wants to do with Pyx, but that isn't the way Astral has been selling that service to customers. I listened to a podcast that interviewed Charlie Marsh where he talked about Pyx. Pyx was being marketed as a secure, private Python repo for companies and other organizations. If a company cares enough to pay for a private repo, I don't see many of them agreeing to then let OpenAI train their models on it and do who knows what else with their code. Now Pyx has some additional features that PyPI lacks, such as downloading a ML/AI package for a specific type of GPU.Right, so having thought about this some more, I wonder if the real prize for OpenAI isn't actually any of Astral's current products, but the Python package registry they've been working on, Pyx.
I can certainly imagine a future where as part of uploading to Pyx, package maintainers have to explicitly allow OpenAI to train on the source code of the package. Then uv deprecates support for Pypi, and because uv support is kind of a big deal, suddenly OpenAI has a huge repo that they can train on, completely legally.
That might be too tin-foil hat, but it certainly seems like a benefit to OpenAI.
Epsilon. You’re looking for epsilon.Trying to figure on a good number to represent a value greater than 0, but not quite 1%.
and then assign that number to the confidence % I put in any corporate promises.
Nah. When it comes to tech bro and vulture capital’s ability to enshittify, take the most tin-foil hat scenario you can imagine, and that might end up being the best case scenario. If we’re lucky.That might be too tin-foil hat
That may be what OpenAI wants to do with Pyx, but that isn't the way Astral has been selling that service to customers. I listened to an a podcast that interviewed Charlie Marsh where he talked about Pyx. Pyx was being marketed as a secure, private Python repo for companies and other organizations. If a company cares enough to pay for a private repo, I don't see many of them agreeing to then let OpenAI train their models on it and do who knows what else with their code. Now Pyx has some additional features that PyPI lacks, such as downloading a ML/AI package for a specific type of GPU.
pyx - the other side of the uv coin (announcing pyx)
Maybe it's small potatoes, but FOSS naming in general is a tire fire. Every package or project is seemingly designed to be as comprehensively unsearchable as possible.
It's not as if the string (the string of two characters, mind you, lots of namespace there guys) "UV" has any other common meanings.
Not saying I am thrilled by this acqui-hire (imo that's what this is) but, realistically, how was Astral going to keep the lights on otherwise?That's ok, I'm sure it won't do any harm to the software ecosystem when the bubble bursts. Right?
uv and ruff extensively in my workplace, I've championed especially uv across my organization more broadly, and I'm a huge fan. I'm hopeful that the work of the Astral folks will continue as-is. If not, their code is available and forks can happen if necessary.uv is so much faster than pip are down to optimizations that are entirely available to pip today and simply not done there. Plenty of meat on those bones.AI coding has improved a ton. I recently gave it a shot again after being immensely frustrated with it last year, and.. well, any programmer who wants to still be in the industry a decade from now needs to start taking this seriously. Gemini Pro 3.1 does really well. Even if I still have to manually debug code from time to time, it’s enabling me to produce apps for personal use at a pace and with a quality I’d never dreamed of. What once took me weeks to put together can be done in hours—and I’ve been hobby programming for thirty years (with about a decade professionally).From the Charlie Marsh announcement:
Is this money talking, or is he honest? I know this has historically been a very AI skeptical forum, but it seems that the sentiment around coding assistants have swung quite a bit during 2026. And if you truly believe in this being the future, continuing to build tools directly for humans doesn’t really make that much sense when AIs are doing most of the coding.
This is the wrong example to criticize FOSS naming. It's from a VC funded company.Maybe it's small potatoes, but FOSS naming in general is a tire fire. Every package or project is seemingly designed to be as comprehensively unsearchable as possible.
It's not as if the string (the string of two characters, mind you, lots of namespace there guys) "UV" has any other common meanings.
I can certainly imagine a future where as part of uploading to Pyx, package maintainers have to explicitly allow OpenAI to train on the source code of the package. Then uv deprecates support for Pypi, and because uv support is kind of a big deal, suddenly OpenAI has a huge repo that they can train on, completely legally.