I have personally interacted with migrating features and I have also experienced where there is an internal fork of CPython from more than one group. It isn't really necessarily that they are a few features ahead what I have seen is that they a set of targeted features where they do their best judgement on what they can now leverage. That doesn't necessarily mean its better for everyone.
My experience is that I have personally committed code from Cinder (CPython fork internally from Meta) back into CPython and it was determined that features didn't align with CPython and this isn't some kind of dig between each project at all. Also, at a large mega corporation nearly all groups that use critical software with high complexity they all will have internal forks. I'm not sure what exactly what UV will have added on internally but instead of versions I think that you will have patch collections that might be beneficial to OpenAI but not necessarily for everyone. I hope that OpenAI will interact with the rest of the community and those internal patches can be ported into the overall system if it provides benefit.
My experience is that I have personally committed code from Cinder (CPython fork internally from Meta) back into CPython and it was determined that features didn't align with CPython and this isn't some kind of dig between each project at all. Also, at a large mega corporation nearly all groups that use critical software with high complexity they all will have internal forks. I'm not sure what exactly what UV will have added on internally but instead of versions I think that you will have patch collections that might be beneficial to OpenAI but not necessarily for everyone. I hope that OpenAI will interact with the rest of the community and those internal patches can be ported into the overall system if it provides benefit.