Re: [Distutils] PEP 566 - metadata 1.3 changes

I've updated the PEP to use "2.1" as the version: https://www.python.org/dev/peps/pep-0566/ D. ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig

Re: [Distutils] PEP 566 - metadata 1.3 changes

+1 from me. While I dislike the fact that "2.0" was put to use prematurely, using "2.1" is still less confusing than going from 2.0 to 1.3. Nick Coghlan kirjoitti 20.01.2018 klo 05:07: On 19 January 2018 at 00:14, Joni Orponen wrote: On Thu, Jan 18, 2018 at 5:58 AM,

Re: [Distutils] PEP 566 - metadata 1.3 changes

On 19 January 2018 at 00:14, Joni Orponen wrote: > On Thu, Jan 18, 2018 at 5:58 AM, Nick Coghlan wrote: >> Given that, I think it would be reasonable to finally Withdraw PEP 426 >> (rather than continuing to defer it), and have PEP 566 define metadata

Re: [Distutils] PEP 566 - metadata 1.3 changes

It does, it's using the `packaging` module under the hood: >>> from pkg_resources import Requirement >>> Requirement.parse("requests >= 2.8.1") == Requirement.parse("requests (>= >>> 2.8.1)") True D. On Thu, Jan 18, 2018 at 10:56 AM, Daniel Holth wrote: >>1.2 and not 2.0 is

Re: [Distutils] PEP 566 - metadata 1.3 changes

>1.2 and not 2.0 is correct. I took a look at pkg_resources. It doesn't read Metadata-Version at all. It only cares about Version, and in wheels Requires-Dist and Provides-Extra. Everything else is ignored. So PEP 566 won't break anything there as long as someone checks that pkg_resources can

Re: [Distutils] PEP 566 - metadata 1.3 changes

> Given that, I think it would be reasonable to finally Withdraw PEP 426 > (rather than continuing to defer it), and have PEP 566 define metadata > version 2.1, so that it's unambiguously the latest metadata version. I'm amenable to any version number that is > 1.2 and not 2.0. D.

Re: [Distutils] PEP 566 - metadata 1.3 changes

On Thu, Jan 18, 2018 at 5:58 AM, Nick Coghlan wrote: > On 18 January 2018 at 10:22, Dustin Ingram wrote: > >> Metadata 1.3 vs Metadata 2.0 > > > > I agree with Nick here that since this version is backwards-compatible, > that it > > should remain Metadata 1.3. >

Re: [Distutils] PEP 566 - metadata 1.3 changes

On 18 January 2018 at 10:22, Dustin Ingram wrote: >> Metadata 1.3 vs Metadata 2.0 > > I agree with Nick here that since this version is backwards-compatible, that > it > should remain Metadata 1.3. > > In addition, I think we should avoid overloading the already-in-use "2.0" >

Re: [Distutils] PEP 566 - metadata 1.3 changes

Hi all, Thanks very much for all your suggestions and feedback. I want to take a moment to summarize & respond to some outstanding issues from this thread & previous threads. [0][1][2] First, I'd like to reiterate that the goal of this PEP is to: 1. Define the Core Metadata document as the

Re: [Distutils] PEP 566 - metadata 1.3 changes

On Tue, Jan 16, 2018 at 8:55 PM, Nick Coghlan wrote: > The reason for *not* making PEP 566 a major version bump is in case > anyone actually implemented this draft requirement from PEP 426: > "Automated tools consuming metadata SHOULD warn if metadata_version is > greater than

Re: [Distutils] PEP 566 - metadata 1.3 changes

On 17 January 2018 at 02:58, Nathaniel Smith wrote: > Should wheel change to emit 1.3, or should the PEP change to become 2.0? I > know there were great hopes for "metadata 2.0", but given that there are > bazillions of packages out there with a metadata version of 2.0, we're

Re: [Distutils] PEP 566 - metadata 1.3 changes

5 On Tue, Jan 16, 2018 at 12:08 PM Alex Grönholm wrote: > Whichever we choose, the metadata version should match the PEP version, > which it currently does not. > > Nathaniel Smith kirjoitti 16.01.2018 klo 18:58: > > On Jan 12, 2018 8:00 AM, "Alex Grönholm"

Re: [Distutils] PEP 566 - metadata 1.3 changes

Whichever we choose, the metadata version should match the PEP version, which it currently does not. Nathaniel Smith kirjoitti 16.01.2018 klo 18:58: On Jan 12, 2018 8:00 AM, "Alex Grönholm" > wrote: On the same note, wheel

Re: [Distutils] PEP 566 - metadata 1.3 changes

On Jan 12, 2018 8:00 AM, "Alex Grönholm" wrote: On the same note, wheel currently writes "2.0" as its metadata version. Shouldn't this be changed into 1.3 (along with ditching metadata.json)? Should wheel change to emit 1.3, or should the PEP change to become 2.0? I

Re: [Distutils] PEP 566 - metadata 1.3 changes

This is the old text. Describing the distribution === The distribution metadata should include a longer description of the distribution that may run to several paragraphs. Software that deals with metadata should not assume any maximum size for the description. The

Re: [Distutils] PEP 566 - metadata 1.3 changes

Allow me to prod this topic again. ;-) I'm happy with PEP 566 as it stands. Do we want to specify 'email body is long description' in this PEP? It appears to have at least some real world support, but I'm not familiar enough with the email metadata format to write a proper description of it.

Re: [Distutils] PEP 566 - metadata 1.3 changes

Yes, after the PEP is prep'd. On Fri, Jan 12, 2018 at 11:00 AM Alex Grönholm wrote: > On the same note, wheel currently writes "2.0" as its metadata version. > Shouldn't this be changed into 1.3 (along with ditching metadata.json)? > > > Thomas Kluyver kirjoitti

Re: [Distutils] PEP 566 - metadata 1.3 changes

On the same note, wheel currently writes "2.0" as its metadata version. Shouldn't this be changed into 1.3 (along with ditching metadata.json)? Thomas Kluyver kirjoitti 12.01.2018 klo 17:26: On Wed, Jan 10, 2018, at 11:42 PM, Nick Coghlan wrote: On 11 January 2018 at 00:54, Daniel Holth

Re: [Distutils] PEP 566 - metadata 1.3 changes

On Wed, Jan 10, 2018, at 11:42 PM, Nick Coghlan wrote: > On 11 January 2018 at 00:54, Daniel Holth wrote: > > AFAICT the only missing feature from old-Metadata-2.0 is "description as > > message body", which places readable description text after the key/value > > pairs. > > Do

Re: [Distutils] PEP 566 - metadata 1.3 changes

+1 from me for the adjustment Thomas suggested, since that's in the intended vein of "properly document the status quo". On 11 January 2018 at 00:54, Daniel Holth wrote: > AFAICT the only missing feature from old-Metadata-2.0 is "description as > message body", which places

Re: [Distutils] PEP 566 - metadata 1.3 changes

AFAICT the only missing feature from old-Metadata-2.0 is "description as message body", which places readable description text after the key/value pairs. On Wed, Jan 10, 2018 at 8:45 AM Thomas Kluyver wrote: > I hope everyone has had a good break. :-) > > I'd like to see