[core-workflow] Updated draft of PEP 512

[Ezio Melotti]

FWIW sys.subversion has been deprecated in 3.2.1 and removed in 3.3 [0].
In 3.2.1+ and 2.7 it returns ('CPython', '', '').
In theory sys._mercurial is private, so technically we don't have to
go through the same deprecation process, but I see no harm in
deprecating it in 3.6 and then removing it in 3.7+ (assuming we are
going to remove it).

Best Regards,
Ezio Melotti

[0]: https://docs.python.org/3.2/library/sys.html#sys.subversion


On Thu, Jan 21, 2016 at 12:34 AM, Guido van Rossum <guido at python.org> wrote:
> For backwards compatibility sys._mercurial must probably stay. Maybe it
> could be None, so we could write
>
> if sys._mercurial:
>    ...
> elif sys._git:
>    ...
> else:
>    # unknown VCS ...
>
> On Wed, Jan 20, 2016 at 12:39 PM, francismb <francismb at email.de> wrote:
>>
>> Hi Brett,
>> >
>> > Change sys._mercurial
>> > '''''''''''''''''''''
>> > Once Python is no longer kept in Mercurial, the ``sys._mercurial``
>> > attribute will need to be removed. An equivalent ``sys._git``
>> > attribute will be needed to take its place.
>> >
>>
>> Would it make sense to change it to something more general like:
>>
>> sys._version_control_system or
>> sys._vcs  with maybe a new field for the type of vcs: 'mercurial',
>> 'git' or 'the next one' :-)
>>
>>
>> Regards,
>> francis
>> _______________________________________________
>> core-workflow mailing list
>> core-workflow at python.org
>> https://mail.python.org/mailman/listinfo/core-workflow
>> This list is governed by the PSF Code of Conduct:
>> https://www.python.org/psf/codeofconduct
>
>
>
>
> --
> --Guido van Rossum (python.org/~guido)
>
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct