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
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
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
> 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
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
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
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
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
We will begin the migration process in about an hour. Once it's over and
everything is set I'll email again and give the all clear to start using
https://github.com/python/peps instead of hg.python.org/peps.
___
python-committers mailing list
python-commi
