this post was submitted on 19 Mar 2026
85 points (97.8% liked)

Python

7874 readers
2 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

📅 Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

🐍 Python project:
💓 Python Community:
✨ Python Ecosystem:
🌌 Fediverse
Communities
Projects
Feeds

founded 2 years ago
MODERATORS
 

Today we’re announcing that OpenAI will acquire Astral⁠, bringing powerful open source developer tools into our Codex ecosystem.

Astral has built some of the most widely used open source Python tools, helping developers move faster with modern tooling like uv, Ruff, and ty. These tools power millions of developer workflows and have become part of the foundation of modern Python development. As part of our developer-first philosophy, after closing OpenAI plans to support Astral’s open source products. By bringing Astral’s tooling and engineering expertise to OpenAI, we will accelerate our work on Codex and expand what AI can do across the software development lifecycle.

you are viewing a single comment's thread
view the rest of the comments
[–] Brummbaer@pawb.social 4 points 1 month ago (2 children)

Good luck - uv is under a MIT license, so every fork is just a free buffet for openai to incorporate into their enshittified version of uv. There is a reason the GPL exists and many people will learn this the hard way ...

[–] Aatube@lemmy.dbzer0.com 1 points 6 days ago (1 children)

uv is under an MIT license, so every fork is free to relicense themselves as GPL and prevent openai's gobblies.

[–] Brummbaer@pawb.social 1 points 5 days ago (1 children)

Do you have more on that?

I'm not sure you can relicense the MIT code under GPL if you are not the author or it doesn't say so in the MIT license, that relicensing is permitted.

[–] Aatube@piefed.social 1 points 5 days ago (1 children)

The MIT is what's called a permissive license.

Copyright

Permission is hereby granted , free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense , and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

That's the entirety of the text. You can do pretty much anything as long as you make sure the first line is still visible somewhere (and if you're not incorporating/relicensing it into GPL, you have to include the MIT license text as well; I'm less sure about how this parenthetical works but I do know an MIT project relicensed to GPL needs not include the MIT text), which in GPL it is.

https://choosealicense.com/licenses/mit/

https://www.gnu.org/licenses/license-list.html#%3A%7E%3Atext=Expat)-,This%20is%20a%20lax%2C%20permissive%20non%2Dcopyleft%20free%20software%20license%2C%20compatible%20with%20the%20GNU%20GPL.,-Some

[–] Brummbaer@pawb.social 1 points 4 days ago (1 children)

Thanks for the info.

So you can relicense MIT to GPL without the MiT parts staying MIT?

[–] Aatube@piefed.social 1 points 4 days ago* (last edited 4 days ago) (1 children)

yes, you're creating a derivative work that is entirely GPL. note that this doesn't stop anyone from consulting the original since FOSS licenses do not have revocation. if they use none of the GPL derivative work they can still only abide by MIT. however, your changes would only exist in the GPL work, and they must be used with GPL.

[–] Brummbaer@pawb.social 1 points 4 days ago

Thanks for the clarification. I always thought that the GPL parts are also MIT then.

[–] a_good_hunter@lemmy.world 3 points 1 month ago (2 children)

Your truust in the Law is admirable. OpenAI does not care at all about laws. They do what they want and have an army of lawyers to fight anyone who says differently. Just look at copyright laws.

This is why I am saying do it now. Better safe than sorry.

But, since all l am getting is abuse.... I'm out! Y'all have the say you deserve.

[–] Brummbaer@pawb.social 3 points 1 month ago

The world does not consist entirely of the US.

While I agree that openai can buy enough "law" in the US to do what it wants, the license is important in other jurisdictions and can be enforced.

[–] HubertManne@piefed.social 1 points 1 month ago (1 children)

alll I see is abuse? I see only one comment under yours (and its pretty reasonalbe from brummbaer) but maybe all the rest are folks I have blocked.

[–] a_good_hunter@lemmy.world 1 points 1 month ago