Re: [Python-Dev] Workflow PEP proposals are now closed

2015-02-03 Thread Nick Coghlan
On 3 Feb 2015 01:26, "Brett Cannon" wrote: >>> >> >> >> Is there going to be discussion between the two approaches or should the PEPs themselves address each other? > > > Since PEPs are meant to act as a record of what was discussed on a topic then it probably wouldn't hurt to incorporate why your

Re: [Python-Dev] Workflow PEP proposals are now closed

2015-02-02 Thread Brett Cannon
On Mon Feb 02 2015 at 2:40:21 PM Antoine Pitrou wrote: > > Hi, > > What does "closed" mean in this context? > No new PEPs on this topic will be taken under consideration, so submissions are now "closed" to new participants. -Brett > > Regards > > Antoine. > > > > On Mon, 02 Feb 2015 14:35:47

Re: [Python-Dev] Workflow PEP proposals are now closed

2015-02-02 Thread Antoine Pitrou
Hi, What does "closed" mean in this context? Regards Antoine. On Mon, 02 Feb 2015 14:35:47 + Brett Cannon wrote: > The PEPs under consideration are PEPs 474 > and 462 > from Nick Coghlan to use > Kal

Re: [Python-Dev] Workflow PEP proposals are now closed

2015-02-02 Thread Brett Cannon
On Mon Feb 02 2015 at 10:00:30 AM Donald Stufft wrote: > > On Feb 2, 2015, at 9:35 AM, Brett Cannon wrote: > > The PEPs under consideration are PEPs 474 > and 462 > from Nick Coghlan to use > Kallithea and do

Re: [Python-Dev] Workflow PEP proposals are now closed

2015-02-02 Thread Donald Stufft
> On Feb 2, 2015, at 9:35 AM, Brett Cannon wrote: > > The PEPs under consideration are PEPs 474 > and 462 > from Nick Coghlan to use > Kallithea and do self-hosting, and PEP 481 >

[Python-Dev] Workflow PEP proposals are now closed

2015-02-02 Thread Brett Cannon
The PEPs under consideration are PEPs 474 and 462 from Nick Coghlan to use Kallithea and do self-hosting, and PEP 481 from Donald Stufft that proposes using GitHub. A