On 1 October 2015 at 10:19, Alexander Belopolsky
wrote:
> It has been my understanding that some PEPs may be discussed on specialized
> mailings lists, but a notice would be given on python-dev prior to any
> acceptance.
No, that only applies for changes that actually impact the reference
interpr
On September 30, 2015 at 9:14:42 PM, Alexander Belopolsky
(alexander.belopol...@gmail.com) wrote:
> On Wed, Sep 30, 2015 at 8:32 PM, Donald Stufft wrote:
> >
> > I don’t see any requirement to post PEPs to python-dev if they have a
> Discussions-To header in PEP 1.
>
>
> When I faced a similar
On Sep 30, 2015, at 09:14 PM, Alexander Belopolsky wrote:
>When I faced a similar situation with PEP 495, Guido's advise was "I think
>that a courtesy message to python-dev is appropriate, with a link to the
>PEP and an invitation to discuss its merits on datetime-sig." [1]
Certainly Discussions-
On Wed, Sep 30, 2015 at 8:32 PM, Donald Stufft wrote:
>
> I don’t see any requirement to post PEPs to python-dev if they have a
Discussions-To header in PEP 1.
When I faced a similar situation with PEP 495, Guido's advise was "I think
that a courtesy message to python-dev is appropriate, with a
On September 30, 2015 at 8:20:53 PM, Alexander Belopolsky
(alexander.belopol...@gmail.com) wrote:
> It has been my understanding that some PEPs may be discussed on specialized
> mailings lists, but a notice would be given on python-dev prior to any
> acceptance.
>
I don’t see any requirement to
It has been my understanding that some PEPs may be discussed on specialized
mailings lists, but a notice would be given on python-dev prior to any
acceptance.
I have recently received a notification that since PEP 470 has been
accepted, I can no longer use external hosting for one of the packages
