Re: [python-committers] The peps repo is now on GitHub!

2016-06-16 Thread Robert Collins
Folk can't argue with robots: I think its useful to have an escape valve for dealing with spurious failures - the Python Core team is pretty responsible, and I think we should permit bypassing robots, at least until we have lots of run-time to learn about any flakiness present. -Rob On 16 June 20

Re: [python-committers] The peps repo is now on GitHub!

2016-06-16 Thread Donald Stufft
> On Jun 16, 2016, at 1:38 AM, Barry Warsaw wrote: > > On Jun 15, 2016, at 06:59 PM, Donald Stufft wrote: > >> Currently there’s nothing preventing people from pushing directly to >> the PEP repository, in https://github.com/python/peps/issues/5 there’s >> talk of setting up Travis to ensure th

Re: [python-committers] The peps repo is now on GitHub!

2016-06-15 Thread Barry Warsaw
On Jun 15, 2016, at 06:59 PM, Donald Stufft wrote: >Currently there’s nothing preventing people from pushing directly to >the PEP repository, in https://github.com/python/peps/issues/5 there’s >talk of setting up Travis to ensure the PEPs are always building and >if the flag is set to require a +1

Re: [python-committers] The peps repo is now on GitHub!

2016-06-15 Thread Barry Warsaw
On Jun 15, 2016, at 10:42 PM, Brett Cannon wrote: >I don't think anything has fallen over, so I'm calling this a successful >migration! The peps repo is now https://github.com/python/peps . Really great work Brett, thanks! -Barry ___ python-committers

Re: [python-committers] The peps repo is now on GitHub!

2016-06-15 Thread Nick Coghlan
On 15 June 2016 at 15:54, Brett Cannon wrote: > On Wed, 15 Jun 2016 at 15:49 M.-A. Lemburg wrote: >> Hmm, isn't it better to make this read-only to avoid breaking links >> to it ? > > If you want. My only worry is people forgoing GitHub and sending us outdated > patches. But if people want it lef

Re: [python-committers] The peps repo is now on GitHub!

2016-06-15 Thread Donald Stufft
> On Jun 15, 2016, at 6:55 PM, M.-A. Lemburg wrote: > > On 16.06.2016 00:48, M.-A. Lemburg wrote: >> On 16.06.2016 00:42, Brett Cannon wrote: >>> I don't think anything has fallen over, so I'm calling this a successful >>> migration! The peps repo is now https://github.com/python/peps . >> >> T

Re: [python-committers] The peps repo is now on GitHub!

2016-06-15 Thread M.-A. Lemburg
On 16.06.2016 00:48, M.-A. Lemburg wrote: > On 16.06.2016 00:42, Brett Cannon wrote: >> I don't think anything has fallen over, so I'm calling this a successful >> migration! The peps repo is now https://github.com/python/peps . > > Thanks for putting so much hard work into this ! BTW: Is it ok t

Re: [python-committers] The peps repo is now on GitHub!

2016-06-15 Thread Brett Cannon
On Wed, 15 Jun 2016 at 15:49 M.-A. Lemburg wrote: > On 16.06.2016 00:42, Brett Cannon wrote: > > I don't think anything has fallen over, so I'm calling this a successful > > migration! The peps repo is now https://github.com/python/peps . > > Thanks for putting so much hard work into this ! > We

Re: [python-committers] The peps repo is now on GitHub!

2016-06-15 Thread M.-A. Lemburg
On 16.06.2016 00:42, Brett Cannon wrote: > I don't think anything has fallen over, so I'm calling this a successful > migration! The peps repo is now https://github.com/python/peps . Thanks for putting so much hard work into this ! > I have given the Python core team on GitHub write access to the

[python-committers] The peps repo is now on GitHub!

2016-06-15 Thread Brett Cannon
I don't think anything has fallen over, so I'm calling this a successful migration! The peps repo is now https://github.com/python/peps . I have given the Python core team on GitHub write access to the repository so people can add/update their own PEPs. There is also an issue tracker there, seeded