On Thu, Jan 18, 2018 at 5:58 AM, Nick Coghlan
Metadata 1.3 vs Metadata 2.0
I agree with Nick here that since this version is backwards-compatible,
On 18 January 2018 at 10:22, Dustin Ingram
wrote: that it should remain Metadata 1.3.
In addition, I think we should avoid overloading the already-in-use "2.0" version as possibly being either a "PEP 566 flavor 2.0" or a "PEP 426 flavor 2.0".
Nathaniel raised a good point, which is that client tools have already been accepting "bdist_wheel-flavoured metadata 2.0" for years, so we can be confident no client tools are actually rejecting metadata versions that start with "2.x".
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.
Jump straight to 3.0 to clear out any confusion and/or ambiguity on the next backwards-incompatible one? -- Joni Orponen