[Python-Dev] AUTO: Jon K Peck is out of the office
I am out of the office until 09/17/2012. I will be out of the office from Sept 14 through Sept 16. I will not have email access during this time. Note: This is an automated response to your message Python-Dev Digest, Vol 110, Issue 24 sent on 09/14/2012 4:00:03. This is the only notification you will receive while this person is away.___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Edits to Metadata 1.2 to add extras (optional dependencies)
Add to metadata 1.3: Description-File: README(\..+)? Meaning the description should be read from a file in the same directory as PKG-INFO or METADATA (including in the .dist-info directories) and we strongly recommend it be named as README.* and be utf-8 encoded text. Description: is the only multi-line field in the metadata. It is almost never needed at runtime. It would be great for performance and simplify the parser to just put it in another file. Mutually exclusive with Description. May beg for a Summary: tag with a one-line description. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Edits to Metadata 1.2 to add extras (optional dependencies)
On Fri, Sep 14, 2012 at 1:43 PM, Erik Bray erik.m.b...@gmail.com wrote: On Fri, Sep 14, 2012 at 12:30 PM, Daniel Holth dho...@gmail.com wrote: Add to metadata 1.3: Description-File: README(\..+)? Meaning the description should be read from a file in the same directory as PKG-INFO or METADATA (including in the .dist-info directories) and we strongly recommend it be named as README.* and be utf-8 encoded text. Description: is the only multi-line field in the metadata. It is almost never needed at runtime. It would be great for performance and simplify the parser to just put it in another file. Mutually exclusive with Description. May beg for a Summary: tag with a one-line description. Can we make Description-File multiple-use? The meaning of this would be that the Description is formed from concatenating each Description-File in order. That raises the question: Is ordering guaranteed for multiple-use fields? I ask, because distutils2 supports exactly such a feature, and I've found it useful. For example, if I have a README.rst and a CHANGELOG.rst I can specify: description-file = README.rst CHANGELOG.rst Then the full description, contains my readme and my changelog, which look nice together on PyPI, but I prefer to keep as separate files in the source. My only other concern is that if the value of this field can theoretically be arbitrary, it could conflict with other .dist-info files. Does the .dist-info format allow subdirectories? Placing description-files in a subdirectory of .dist-info could be a reasonable workaround. Erik The .dist-info design asks for every metadata file (the one in all caps, not any of the other metadata in .dist-info) to be parsed for many packaging operations that do not require the description, such as resolving the dependency graph of a package. Description-File would give an installer the option to pull Description: out into Description-File:. I would expect the concatenation to happen before this point. I would like to forbid subdirectories in .dist-info but I think they are allowed. The order of multi-use fields is probably preserved. I don't think it is required to be by any spec. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Edits to Metadata 1.2 to add extras (optional dependencies)
On Friday, September 14, 2012 at 12:30 PM, Daniel Holth wrote: Description: is the only multi-line field in the metadata. It is almost never needed at runtime. It would be great for performance and simplify the parser to just put it in another file. License also can be multiline I believe, ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Edits to Metadata 1.2 to add extras (optional dependencies)
On Fri, Sep 14, 2012 at 2:03 PM, Donald Stufft donald.stu...@gmail.com wrote: On Friday, September 14, 2012 at 12:30 PM, Daniel Holth wrote: Description: is the only multi-line field in the metadata. It is almost never needed at runtime. It would be great for performance and simplify the parser to just put it in another file. License also can be multiline I believe, OK. In practice, Description: is the only field that is likely to be hundreds of lines long which seems wasteful. The parser complexity is a non-issue. (I know the PEP says Description: should not be the instruction manual, but it is wrong because that is the way to get useful data up on a package's pypi page.) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Edits to Metadata 1.2 to add extras (optional dependencies)
On 14 September 2012 17:30, Daniel Holth dho...@gmail.com wrote: we strongly recommend it be named as README.* and be utf-8 encoded text. I'd very strongly recommend that the encoding should be mandated. I'm happy with UTF-8 (although I expect a lot of accidental latin-1 files, particularly from Windows users) but I think it would be a mistake to have the specification leaving the encoding of *any* string data unclear. Without the encoding being specified, either in the metadata itself (Description-File-Encoding: utf8? Please, no) or by the specification mandating it, how is a program expected to read the description? Other than this point, I have no opinion on the proposal. Paul. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Edits to Metadata 1.2 to add extras (optional dependencies)
On Fri, Sep 14, 2012 at 1:57 PM, Daniel Holth dho...@gmail.com wrote: On Fri, Sep 14, 2012 at 1:43 PM, Erik Bray erik.m.b...@gmail.com wrote: On Fri, Sep 14, 2012 at 12:30 PM, Daniel Holth dho...@gmail.com wrote: Add to metadata 1.3: Description-File: README(\..+)? Meaning the description should be read from a file in the same directory as PKG-INFO or METADATA (including in the .dist-info directories) and we strongly recommend it be named as README.* and be utf-8 encoded text. Description: is the only multi-line field in the metadata. It is almost never needed at runtime. It would be great for performance and simplify the parser to just put it in another file. Mutually exclusive with Description. May beg for a Summary: tag with a one-line description. Can we make Description-File multiple-use? The meaning of this would be that the Description is formed from concatenating each Description-File in order. That raises the question: Is ordering guaranteed for multiple-use fields? I ask, because distutils2 supports exactly such a feature, and I've found it useful. For example, if I have a README.rst and a CHANGELOG.rst I can specify: description-file = README.rst CHANGELOG.rst Then the full description, contains my readme and my changelog, which look nice together on PyPI, but I prefer to keep as separate files in the source. My only other concern is that if the value of this field can theoretically be arbitrary, it could conflict with other .dist-info files. Does the .dist-info format allow subdirectories? Placing description-files in a subdirectory of .dist-info could be a reasonable workaround. Erik The .dist-info design asks for every metadata file (the one in all caps, not any of the other metadata in .dist-info) to be parsed for many packaging operations that do not require the description, such as resolving the dependency graph of a package. Description-File would give an installer the option to pull Description: out into Description-File:. I would expect the concatenation to happen before this point. I understand now. In this case why even allow flexibility in the description file name? Just make it description.txt, and the Description-File field just some boolean indicator of whether or not a description file exists? Erik ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] What's New in Python 3.3: missing unittest.mock!
Hi, I just noticed that the new unittest.mock module is missing from the What's New in Python 3.3. Can someone add it? (I cannot right now). Thanks. Victor ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
