[issue11219] Produce a warning when the license is specified in both the License and Classifier metadata fields

2011-02-16 Thread Alexis Metaireau
Alexis Metaireau ale...@notmyidea.org added the comment: Hi, I was more thinking about something like: if the license is specified in the License metadata, then check that it's not a well known license (which can and must be provided by the classifiers instead). At the end, the code you've

[issue11219] Produce a warning when the license is specified in both the License and Classifier metadata fields

2011-02-16 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: PEP 345 actually defines two fields that should be used only when a suitable Trove classifier does not exist: Platform (multiple use) A Platform specification describing an operating system supported by the distribution which is not listed in

[issue11219] Produce a warning when the license is specified in both the License and Classifier metadata fields

2011-02-16 Thread Kelsey
Kelsey kelsey.highto...@gmail.com added the comment: Based on the feedback, I will rework the patch to include the following: * Produce a warning only if the user supplied Platform or License metadata is listed in Trove classifiers (Exact match?). --

[issue11219] Produce a warning when the license is specified in both the License and Classifier metadata fields

2011-02-16 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: That’s not quite what the PEP says. Please read it again and try to follow the text in your code. Thanks for your work :) -- ___ Python tracker rep...@bugs.python.org

[issue11219] Produce a warning when the license is specified in both the License and Classifier metadata fields

2011-02-16 Thread Alexis Metaireau
Alexis Metaireau ale...@notmyidea.org added the comment: That's almost what the PEP says, or at least what I understand of it. The platform and license fields should be used only if no matching classifier exists for them. -- ___ Python tracker

[issue11219] Produce a warning when the license is specified in both the License and Classifier metadata fields

2011-02-16 Thread Kelsey
Kelsey kelsey.highto...@gmail.com added the comment: Eric, I am not sure we can check for more than an exact match on Platform and License metadata fields. D2 maintains a list of all Trove Classifiers which can be searched for an exact match; if a match is found warn the user that a

[issue11219] Produce a warning when the license is specified in both the License and Classifier metadata fields

2011-02-16 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: That's almost what the PEP says, or at least what I understand of it. I’ve probably misused “not quite”; I meant “not exactly”. Allow me to try to translate the PEP text to pseudo-code: Platform (multiple use) A Platform specification

[issue11219] Produce a warning when the license is specified in both the License and Classifier metadata fields

2011-02-16 Thread Kelsey
Kelsey kelsey.highto...@gmail.com added the comment: Eric, thanks for the example. This clarifies things. +1 on the new data structure for the classifiers -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11219

[issue11219] Produce a warning when the license is specified in both the License and Classifier metadata fields

2011-02-15 Thread Kelsey
New submission from Kelsey kelsey.highto...@gmail.com: Distutils2 should produce a warning when the license is specified in both the License and Classifier metadata fields -- assignee: tarek components: Distutils2 messages: 128624 nosy: alexis, eric.araujo, kelseyhightower, tarek

[issue11219] Produce a warning when the license is specified in both the License and Classifier metadata fields

2011-02-15 Thread Kelsey
Kelsey kelsey.highto...@gmail.com added the comment: Changes and additional tests can be reviewed on my patch queue. https://bitbucket.org/khightower/distutils2-patch-queue/changeset/d7dff88ab524 -- ___ Python tracker rep...@bugs.python.org