[Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github
Antoine Pitrou
solipsis at pitrou.net
Sun Nov 30 22:00:35 CET 2014
More information about the Python-Dev mailing list
Sun Nov 30 22:00:35 CET 2014
- Previous message: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github
- Next message: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, 30 Nov 2014 19:19:50 +0000 Brett Cannon <brett at python.org> wrote: > > As the PEP points out, the devguide, devinabox, and the PEPs have such a > shallow development process that hosting them on Bitbucket wouldn't be a > big thing. But if we don't view this as a long-term step towards moving > cpython development somehow we are bifurcating our code contributors > between git and hg which will be annoying. Now it could be argued that it > doesn't matter for the peps and devguide since they are purely text and can > be done easily through a web UI and a simple CI in Travis can be set up to > make sure that the docs compile cleanly. Web-based text editors are a poor UI so, while it *can* be done over the Web, it's not really a good thing to promote (unless we're talking mini-edits such as fixing typos). Regards Antoine.
- Previous message: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github
- Next message: [Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list