Closed wavenator closed 2 years ago
tld
seems to be under a triple license arrangement: "MPL-1.1 OR GPL-2.0-only OR LGPL-2.1-or-later". Wouldn't that meet your needs?
Unfortunately no :(
Yet I think switching to a more popular library like tldextract
seems reasonable from other perspectives such as community adoption.
WDYT?
I'm open to the idea, but I'd like to hear a concrete example for how LPGL tld
is still unsuitable, because I'd rather not swap the dependency without certainty that it solves a problem.
The relative popularity of the 2 choices likely isn't an issue since they're both actively maintained. On the other hand, tld
still supports Python 2.7, which is is nice because I still need to cater to some niche environments that use it.
It makes it much harder to make a modification to the library. Also, using licenses of this type keep potential users away.
Thanks a lot for making this change!
Hi folks.
The library requires
tld
for the sole purpose of parsing the tld out of the host in one place in the code. It makes usingpypac
a bit harder for commercial usage. There is a much more popular library calledtldextract
which is distributed under BSD-3clause license - which is much more permissive. I'd be happy to open a PR replacingtld
withtldextract
.https://github.com/john-kurkowski/tldextract