|
|
Log in / Subscribe / Register

Distributors entering Flatpakland

Distributors entering Flatpakland

Posted Jul 10, 2022 17:29 UTC (Sun) by gray_-_wolf (subscriber, #131074)
In reply to: Distributors entering Flatpakland by atnot
Parent article: Distributors entering Flatpakland

> bundle a custom patched version in a third

Could this lead to a fragmentation of an ecosystem for whatever interpreted language? As in, "I don't like this about python, so let me just patch that out". Since you will ship your own python anyway, you might not care. Am I too paranoid?


to post comments

Distributors entering Flatpakland

Posted Jul 10, 2022 19:07 UTC (Sun) by mathstuf (subscriber, #69389) [Link]

For Python specifically? Unlikely. All code lives in a single namespace with no way to make sub-namespaces (AFAIK). So if you want to patch `numpy`, you have to give it a new name and update all internal code to look itself up by that new name. Or you're patching *everyone's* `numpy`. The former is too much work for most people to bother with. The latter is bound to cause trouble with various mixes of packages and versions sooner or later.

If you're talking about the interpreter and its stdlib, who knows. Embedding Python into your own package is already a nightmare to do half decently. Attempts at "bring your own Python" packages have been a flop so far because you lose double-click on the binary. So we just ship our own and say "too bad" about anything else (`pip` is not shipped in a working condition because we disable OpenSSL; if we shipped that, we'd get hammered on every audit for being "out of date").


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds