On Wed, 20 Jan 2016 at 12:40 francismb <franci...@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' :-) >
This is brought up every time we change the VCS. I'm not pushing one way or the other so I leave it up to others to argue whether we should change the approach taken by starting a new thread (but unless a consensus is reached I'm sticking with what we have done in the past). If I remember correctly, the original argument for not going generic is there is no guarantee future VCSs will have similar semantics that will fit into whatever tuple or dict structure we chose.
_______________________________________________ core-workflow mailing list core-workflow@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
