Bundling codex with uv isnt going to meaningfully affect the number of people using it. It doesnt increase the switching costs or anything.
I'm sort of wondering if they're going to try to make a coding LLM that operates on an AST rather than text, and need software/expertise to manage the text->AST->text pipeline in a way that preserves the structure of your files/text.
Writing something that understands all the methods that come in a Django model goes way beyond parsing the code, and is a genuine struggle in language where you can’t execute the code without worrying about side effects like Python.
Ty should give them a base for that where the model is able to see things that aren’t literally in the code and aren’t in the training data (eg an internal version of something like SQLAlchemy).
E.g. mypy has a plugin to read the methods and return types of SQLAlchemy records, I believe without actually executing them.
Obviously not globally true, but in limited domains/scenarios you can see what would exist without actually executing the code.
Not-most popular LLM software development product on the planet acquires most popular/rapidly rising python packaging org for mindshare.
I guess this move might end up in a situation where the uv team comes up with some new agent-first tooling, which works best or only with OAI services.