Comment by jrochkind1
5 months ago
Does anyone understand the intent behind the changed license on the package, why are the current maintainers trying to do it in the first place? What's actually going on?
5 months ago
Does anyone understand the intent behind the changed license on the package, why are the current maintainers trying to do it in the first place? What's actually going on?
Unicode detection is the kind of utility the language maintainers want in their package collection if not in the standard library, and programmers who have to do anything with "plain text" files might want to rely on.
Releasing a core library like this under a genuinely free licence (MIT) is a service to anyone working in the ecosystem.
Maybe. Enabling more GPL software to become proprietary isn't exactly a service.
I think they moved chardet from GPL to MIT? If the maintainer made future versions proprietery, they'd surely be forked and then kicked out of the python package repo?
1 reply →
Nobody that is not already writing (L)GPL licensed software wants to pull LGPL licensed libraries into his software. I'm not a lawyer. If you have it in separate object artefacts that you can dynamically link to, you should be fine. Everything else may be more difficult.
See what FFmpeg writes on this topic: https://ffmpeg.org/legal.html
https://news.ycombinator.com/item?id=47260749