Timon 🛠And another reason why Python packaging needs to gets fixed upstream. You can't have the languages package management be treated as a thing to be implemented by third parties.
Please CPython, finally learn from node and Rust on how to do this properly.
✧✦Catherine✦✧@timonsku there's no resources to do that... and the resources that do exist to fund PyPI and such are also paid for by openai
@whitequark Yea that is fair.
My issue is less with OpenAI specifically and more that ultimate control for cruicial infrastructure is in the hands of an unreliable actor. A neutral foundation is always an important layer of protection.
More a critique of governance.
I also have not really seen any desire by CPython to even start tackling this, irrespective of the available funds to realize the project. It was consistently pushed off to be "solved by community"
My issue is less with OpenAI specifically and more that ultimate control for cruicial infrastructure is in the hands of an unreliable actor. A neutral foundation is always an important layer of protection.
More a critique of governance.
I also have not really seen any desire by CPython to even start tackling this, irrespective of the available funds to realize the project. It was consistently pushed off to be "solved by community"
@whitequark Which, fair for the financial burden but the technical ground work needs to be more foundational to make package management a more natural first party aspect of Python, which I think we discussed before and realize is not straight forward but still think can see significant improvement over the current state.
npcomp@timonsku @whitequark on a sufficiently long timeline (and usually sufficiently long is not even _that_ long), all actors are unreliable.