[Python-Dev] PEP: Collecting information about git
Oleg Broytman
phd at phdru.name
Wed Sep 16 00:09:04 CEST 2015
On Tue, Sep 15, 2015 at 10:41:54PM +0100, Larry Hastings <larry at hastings.org> wrote:
>
> I don't follow. Because you're an advocate of Python switching to
> git and GitHub, we should have a git tutorial committed as a Python
> Enhancement Proposal?
>
> I'm not attempting to stir up a conversation about git vs hg. I
> only question the idea that a git tutorial should be a PEP, when it
> has literally nothing to do with enhancing Python. There are
There are PEPs that enhance development process but not Python
itself. I consider the PEP one of those.
> countless other venues through which Oleg could publish this
> information--a blog, a wiki, or even a series of postings to this
> newsgroup. I would encourage him to withdraw the PEP and publish
> through one of those.
>
>
> //arry/
>
> On 09/15/2015 07: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?
> >
> > Georg
> >--
> >--Guido van Rossum (python.org/~guido <http://python.org/%7Eguido>)
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