On Thu, Mar 11, 2021 at 12:16 AM Evpok Padding <evpok.padd...@gmail.com> wrote: > > Dear all, > > Apparently renaming a git branch to follow the general convention is now an > unbearable outrage.
It is NOT a general convention. It is a push by Microsoft (owners of GitHub). Outside of GitHub, the git command still uses "master" as the default name. This is a *political* move made for *political* reasons, and has consequences downstream. Why is it so important to cause actual real problems for no reason other than to feel good about one insignificant piece of language - and, as Steve pointed out, not even the most significant one? Let's take ChainMap as an example. Would you propose renaming it in Python 3.11? Would there be pushback against such a proposal? Things in the Python standard library, when renamed, can have aliases to ensure backward compatibility. Can you do that with a branch rename? What plans are there to ensure that scripts and tooling can work on both sides of such a rename? Why has there been no discussion of the technical implications of this change prior to now? ChrisA _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/4VZ7GM6EXNG5PKV3RBBQ7T2R43CJPE6L/ Code of Conduct: http://python.org/psf/codeofconduct/
