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.
You must log in or register to comment.
Sigh. I knew uv and ruff were too good to be true. Just hope the community can fork before it all goes to crap.
FFS, first Bun, now Astral… It’s a shame, uv is such a useful tool in the Python ecosystem.
The ensloppening of some of my favorite tools begins?
The developers were already genAI users.
But now I fear that the tutorial will include an “openai init”, and other non-deterministic subscription-based commands for ruff and uv and that will be what is pushed.
I find that Python requires a fair bit of discipline to keep it readable, and I’ve seen some very unreadable code written by people. Vibe coding with Python’s dynamic nature seems like a match made in hell.
This is true although that’s what enforcing strict type checking and good linting is supposed to help with. I think it’s partially an issue that you can kinda just type what you think and not everyone thinks efficiently/ programmer-y
Edited for clarity
Agreed! I think both linting and type checking are extremely important to Python, but it’s also an extra step that far too many people just don’t take. And honestly, I used to get tripped up sometimes with setting up Python tooling before I started using uv.
Unfortunately I also have to work with the occasional Python script that someone just slapped together, and that’s something far too easy to do in Python. It does kind of remind me of vibe coding. Initial velocity seems high, but if you’re not thinking about it, long term maintenance tanks.
That’s not to say Python is bad, and there is certainly a lot of good Python code out there too. But it’s a language that does make it easy to make a mess, which will probably be compounded by LLMs.
Count down to forks in 3… 2… 1…
But which form will survive ?
I want tools from the python foundation ! (I kinda hoped ruff and UV were taken over by the pypa)
Removed by mod
Read the room dude.
