On Fri, 3 Jul 2020 at 13:10, Ivan Pozdeev <v...@mail.mipt.ru> wrote: > So what? > Unnecessary
> They'll have to synchronise their history to ours to be able to make a PR. > And if they don't, it doesn't matter for us what they do with the data > anyway since they are responsible for maintaining it and keeping it > relevant if they need to, not us > That is not a very collaborative mindset. Can somebody give an example of when we force-pushed before? Surely there should be a PEP outlining when we force push and how we communicate this to our "consumers" before/when we do so? > Plus, since it's the PEPs repo, it's tightly bould to the Python project > -- the usefulness of a fork disconnected from it is pretty low. > It partially serves as documentation for the Python project, so mirroring it and its documentation (in git form or in its presented form) can definitely have a use, for example, if you are an environment that has no internet access (common in secret government work, and I am sure their IT team will be even less pleased that they have to do something by hand and overwrite history!). >
_______________________________________________ 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/55F6YYVAHRRIGUCXZQWZNUKK3LSDDNYZ/ Code of Conduct: http://python.org/psf/codeofconduct/
