[Python-Dev] PEP: Collecting information about git
Oleg Broytman
phd at phdru.name
Tue Sep 15 20:44:39 CEST 2015
On Tue, Sep 15, 2015 at 08:32:33PM +0200, Georg Brandl <g.brandl at gmx.net> wrote:
> Fair enough. Still strange to read this PEP with the explicit caveat of
> "The author of the PEP doesn't currently plan to write a Process PEP on
> migration Python development from Mercurial to git."
I am not a member of the core team, I certainly cannot write such a
Process PEP. But I very much hope to see one and help if I can.
> Georg
>
> On 09/15/2015 08:22 PM, Guido van Rossum wrote:
> > For one, because *I* have been a (moderate) advocate for switching to git and
> > GitHub.
> >
> > On Tue, Sep 15, 2015 at 11:19 AM, Georg Brandl <g.brandl at gmx.net
> > <mailto:g.brandl at gmx.net>> wrote:
> >
> > On 09/15/2015 08:02 PM, Oleg Broytman wrote:
> > > On Tue, Sep 15, 2015 at 09:46:55AM -0700, Benjamin Peterson <benjamin at python.org <mailto:benjamin at python.org>> wrote:
> > >> This looks like good information, but why is it a PEP? If anything, the
> > >> devguide was probably be more appropriate. But even that's strange
> > >> considering we don't use git at the moment.
> > >
> > > Exactly because the core team doesn't use git the information doesn't
> > > belong to the current revision of Developer's Guide.
> >
> > And if it doesn't propose to make the core team use git, why is it a PEP?
Oleg.
--
Oleg Broytman http://phdru.name/ phd at phdru.name
Programmers don't die, they just GOSUB without RETURN.
More information about the Python-Dev
mailing list