Ahhh - this is true, good point. I thought I did read somewhere that LICENSE
was included by default. distutils?
Maybe I should open an issue with setuptools and see what people there think as
I've hit this issue a lot, especially as wheel always wants a LICENSE file.
Cooper
> On Jul 13, 2018,
On Thu, 12 Jul 2018 at 08:25 Cooper Ry Lees wrote:
> Hi all,
>
> Side note / side track / I've noticed this recently. Was adding LICENSE
> file ever a default for distutils/setuptools to add too sdsists? Has that
> changed recently?
>
> I build wheels from sdists from PyPI (to link with my own in
> On Jul 12, 2018, at 3:45 AM, Robin Becker wrote:
>
> Am I right in assuming that uploading a different file with the same name
> will cause an error?
Correct.--
Distutils-SIG mailing list -- distutils-sig@python.org
To unsubscribe send an email to distutils-sig-le...@python.org
https://mail.
On 12/07/2018 16:22, Cooper Ry Lees wrote:
Hi all,
Side note / side track / I've noticed this recently. Was adding LICENSE file
ever a default for distutils/setuptools to add too sdsists? Has that changed
recently?
I build wheels from sdists from PyPI (to link with my own internal versions of
Hi all,
Side note / side track / I've noticed this recently. Was adding LICENSE file
ever a default for distutils/setuptools to add too sdsists? Has that changed
recently?
I build wheels from sdists from PyPI (to link with my own internal versions of
C libraries etc. - I don't like to trust bi
On 12/07/2018 14:13, John Thorvald Wodder II wrote:
.
I believe the current standard way to distribute a LICENSE file with a package is to add
"include LICENSE" (or whatever the filename is) to MANIFEST.in (which adds the file to
the sdist) and add "license_file = LICENSE" (or other fi
On 2018 Jul 12, at 07:20, Robin Becker wrote:
>
>
>> (full list: https://opensource.org/licenses/alphabetical)
>> The Reportlab licence is listed as "BSD License (BSD license (see
>> license.txt for details)", but, AFAICS, none of the downloadable files
>> actually include a license.tx
(full list: https://opensource.org/licenses/alphabetical)
The Reportlab licence is listed as "BSD License (BSD license (see license.txt for details)", but, AFAICS, none of the downloadable
files actually include a license.txt file.
(This means redistributing these files is against eith
On 12/07/2018 09:39, Petr Viktorin wrote:
On 07/12/18 09:41, Robin Becker wrote:
On 11/07/2018 17:28, Paul G wrote:
I think the classifier you want is `License :: Other/Proprietary License`, but you can choose the most appropriate one from the
list.
Actually I'm not sure this is correct. The
On Thu, 12 Jul 2018, 13:06 Thomas Kluyver, wrote:
> On Thu, Jul 12, 2018, at 8:19 AM, Robin Becker wrote:
> > The previous
> > answer says there is a list so I can use that.
>
> I don't think anyone linked to it yet, so:
> https://pypi.org/pypi?%3Aaction=list_classifiers
https://pypi.org/classi
On Thu, Jul 12, 2018 at 12:32 AM, Robin Becker wrote:
> On 11/07/2018 19:44, Thomas Kluyver wrote:
>
>> On Wed, Jul 11, 2018, at 7:32 PM, Chris Jerdonek wrote:
>>
>>> And yet you can see "License: ReportLab BSD Derived" in the left-hand
>>> column under "Meta," so how did it get there? Did PyPI p
On 07/12/18 09:41, Robin Becker wrote:
On 11/07/2018 17:28, Paul G wrote:
I think the classifier you want is `License :: Other/Proprietary
License`, but you can choose the most appropriate one from the list.
Actually I'm not sure this is correct. The license is actually the BSD
one, but deriv
On 11/07/2018 19:39, Donald Stufft wrote:
On Jul 11, 2018, at 12:37 PM, Nathaniel Smith wrote:
Possibly PyPI is noticing that the file you're trying to upload is identical to the one
that's already there and counting that as a "successful upload"?
Yes, if you try to upload the same file t
On 11/07/2018 17:28, Paul G wrote:
I think the classifier you want is `License :: Other/Proprietary License`, but
you can choose the most appropriate one from the list.
Actually I'm not sure this is correct. The license is actually the BSD one, but derived in the standard way. So it's not
pro
On Thu, Jul 12, 2018, at 8:19 AM, Robin Becker wrote:
> The previous
> answer says there is a list so I can use that.
I don't think anyone linked to it yet, so:
https://pypi.org/pypi?%3Aaction=list_classifiers
--
Distutils-SIG mailing list -- distutils-sig@python.org
To unsubscribe send an email
On 11/07/2018 19:44, Thomas Kluyver wrote:
On Wed, Jul 11, 2018, at 7:32 PM, Chris Jerdonek wrote:
And yet you can see "License: ReportLab BSD Derived" in the left-hand
column under "Meta," so how did it get there? Did PyPI previously fall
back to including the "License" classifier value as is (
On 11/07/2018 17:29, Ian Stapleton Cordasco wrote:
1) I think it is completely wrong for twine/pypi to fail to upload because
of the license field. The license is derived from BSD
and the same string is present in the previously uploaded versions of this
package. What are valid licenses? Presumab
On 11/07/2018 17:28, Paul G wrote:
I think the issue here is not your use of the "license" field (though using the
classifier-like syntax there is dubious), but the fact that you are specifying an invalid
classifier. The valid classifiers are enumerated, you can find them here:
https://pypi.or
On Wed, Jul 11, 2018, at 7:32 PM, Chris Jerdonek wrote:
> And yet you can see "License: ReportLab BSD Derived" in the left-hand
> column under "Meta," so how did it get there? Did PyPI previously fall
> back to including the "License" classifier value as is (even if
> invalid) if no "license" field
> On Jul 11, 2018, at 12:37 PM, Nathaniel Smith wrote:
>
> Possibly PyPI is noticing that the file you're trying to upload is identical
> to the one that's already there and counting that as a "successful upload"?
Yes, if you try to upload the same file twice (same as in, the hashes match and
On Wed, Jul 11, 2018 at 10:41 AM, Thomas Kluyver
wrote:
> On Wed, Jul 11, 2018, at 5:37 PM, Nathaniel Smith wrote:
>
> I don't know why you're having this experience of a classifier you think
> used to be supported no longer being supported. You say the license field
> is the same as on previous
On Wed, Jul 11, 2018, at 5:37 PM, Nathaniel Smith wrote:
> I don't know why you're having this experience of a classifier you
> think used to be supported no longer being supported. You say the
> license field is the same as on previous uploads. But the license
> field isn't the issue here. Is the
PyPI is not the license police. You can specify any license you like in the
dedicated, free-form text, "license" field.
That's the "license" field. But, PyPI does require that values in the
"classifiers" field have to be taken from a known set. Among other things,
this prevents typos, and prevents
Hi there Robin,
I'm going to try to reply in-line.
Sent from my phone with my typo-happy thumbs.
On Wed, Jul 11, 2018, 11:17 Robin Becker wrote:
> After release of Python-3.7 I wanted to upload to pypi a newly built
> version of a C-extension which already has been migrated to
> the new site.
I think the issue here is not your use of the "license" field (though using the
classifier-like syntax there is dubious), but the fact that you are specifying
an invalid classifier. The valid classifiers are enumerated, you can find them
here: https://pypi.org/classifiers/
I think the classifie
25 matches
Mail list logo