Re: [Distutils] [Catalog-sig] Metadata-Version in PKG-INFO
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 later and asks? As my friend told me, this is an example: 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 Regards, Carlos Tejo ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] [Catalog-sig] Metadata-Version in PKG-INFO
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 copy of it in your source distribution; if you do so, it seems fairly clear that the license that you specified is the very version that you include with your code, even if you don't mention a version number explicitly. OTOH, if you then also include the following text in the source files (which the LGPL suggests that you do), then clearly, you explicitly make it the user's choice to pick a version: This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. However, that wording is specific to the LGPL (and the GPL), and does not apply to any other license. Regards, Martin ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Questionnaire: Why do you use setuptools?
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; it installs setuptools, and then makes 'easy_install' a pleasure to use (I still can't believe people use easy_install in their system Python!) Why not? They're told to. Go to a random Python package's web page and chances are you'll see to install it, simply run easy_install MyAwesomePackage. - entry points serve as crude equivalents of named utilities in the Zope component architecture; they allow an application to define a class of plug points, which are then filled by other libraries. These plug points can then be configured together declaratively (e.g. in an INI file) using their names. Marius Gedminas -- Microsoft -- because God hates us. signature.asc Description: Digital signature ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] Questionnaire: Why do you use setuptools?
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) 2. virtualenv + easy_installing packages inside + getting all the dependencies specified with install_requires in step 1. 2b. same but with zc.buildout 3. entry points (usually for specifying console_scripts) Marius Gedminas -- If you sat a monkey down in front of a keyboard, the first thing typed would be a unix command. -- Bill Lye signature.asc Description: Digital signature ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
Re: [Distutils] [Catalog-sig] Metadata-Version in PKG-INFO
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 should be more difficult to specify imprecisely (by including text as described) than to specify precisely. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
