> I don't understand all the worry about sys.subversion. It's not like > it's useful to anybody else than us, and I think it should have been > named sys._subversion instead. There's no point in making API-like > promises about which DVCS, bug tracker or documentation toolset we use > for our workflow.
I read “subversion” as “sub-piece of information about version”, not the name of a VCS, so I have no problem with its continuing existence under Mercurial (it’s in PEP 385). Regards _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
