BTW, I asked today a friend who is involved in license issue and she
explained me that: if the version of a license is not declared in a software
product, that means that the license applied is the last one.
The last one at the time of licensing or the last one at the time
someone comes back
2018 - LGPL 3.0 is released
2019 - Package X is licensed by LPGL (no version)
2020 - LPGL 4.0 is released
2021 - What's the license of the package X? LGPL 4.0
IANAL, but I don't believe this example; in addition, I
consider it fairly artificial. The LGPL recommends that
you include a verbatim
On Sat, Apr 18, 2009 at 07:19:31AM -0400, Tres Seaver wrote:
What are the other major reasons people use setuptools?
- setuptools.find_pacakges built-in SVN support makes a whole class of
packaging errors go away for me.
- virtualenv makes isolation between different applications sane;
On Sat, Apr 18, 2009 at 11:09:11AM +0200, Lennart Regebro wrote:
I don't actually know what features of setuptools people use.
1. 'python setup.py sdist register upload' (you could say this is a
distutils feature, but my packages tend to unconditionally import
setuptools in their setup.py)
On Sun, Apr 19, 2009 at 6:14 AM, Martin v. Löwis mar...@v.loewis.de wrote:
However, that wording is specific to the LGPL (and the GPL),
and does not apply to any other license.
More importantly, it only applies if you specifically include it.
The problem I see is with non-specification; it
