On Sun, Feb 17, 2013 at 2:10 AM, Nick Coghlan ncogh...@gmail.com wrote:
Maintainer (optional)
-
A string containing the maintainer's name at a minimum; additional
contact information may be provided.
Note that this field is intended for use when a project is being
Makes sense. Even 1.2 has maintainer. It probably wouldn't be too intrusive
to spit out a few more fields in distutils. I don't know about pypi which
usually gets metadata as a dictionary.
On Feb 23, 2013 10:51 PM, Chris Jerdonek chris.jerdo...@gmail.com wrote:
On Sun, Feb 17, 2013 at 2:10 AM,
On Sat, Feb 23, 2013 at 8:13 PM, Daniel Holth dho...@gmail.com wrote:
Makes sense. Even 1.2 has maintainer. It probably wouldn't be too intrusive
to spit out a few more fields in distutils. I don't know about pypi which
usually gets metadata as a dictionary.
This issue in PyPI's bug tracker
On Mon, Feb 18, 2013 at 5:38 AM, Philippe Ombredanne
pombreda...@nexb.com wrote:
On Sun, Feb 17, 2013 at 2:10 AM, Nick Coghlan ncogh...@gmail.com wrote:
The latest draft of PEP 426 is up at http://www.python.org/dev/peps/pep-0426/
This is looking great!
License (optional)
--
On Sun, Feb 17, 2013 at 2:10 AM, Nick Coghlan ncogh...@gmail.com wrote:
The latest draft of PEP 426 is up at http://www.python.org/dev/peps/pep-0426/
This is looking great!
License (optional)
--
[...]
The full text of the license would normally be included in a separate
file.
The Wheel implementation tries to put the license in LICENSE.txt inside
.dist-info. I didn't feel the need to mention it in metadata.
Metadata parsing is extremely unimportant in prior versions of the spec.
Correct me if a significant tool actually needs the file at all in v1.1,
except for
