Finalizing PEP 440
It's been ~3 months or so since PEP 440 support was released in pip and setuptools. I think at this point we've resolved any major issues with the PEP 440 spec that can be resolved without a whole new PEP. In addition it's now been out long enough that people have adjusted processes/tooling to account for it and changing things at this stage is likely going to be more disruptive than just leaving it as it is. Given that, I suggest that we mark the PEP as no longer provisional. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
On 19 March 2015 at 08:11, Donald Stufft
It's been ~3 months or so since PEP 440 support was released in pip and setuptools. I think at this point we've resolved any major issues with the PEP 440 spec that can be resolved without a whole new PEP. In addition it's now been out long enough that people have adjusted processes/tooling to account for it and changing things at this stage is likely going to be more disruptive than just leaving it as it is.
Given that, I suggest that we mark the PEP as no longer provisional.
Agreed, and I've updated the PEP accordingly: https://hg.python.org/peps/rev/8d7b218a99a8 Cheers, Nick. P.S. /me also bumps officially defining the "provisional PEP acceptance" approach in PEP 1 even further down the todo list :) -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
participants (2)
-
Donald Stufft
-
Nick Coghlan