RetroSearch Browse

Thu Oct 1 08:29:24 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-October/141843.html

On 1 October 2015 at 10:19, Alexander Belopolsky
<alexander.belopolsky at 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.

No, that only applies for changes that actually impact the reference
interpreter or the standard library - those still need to be discussed
and approved on python-dev.

For changes that are wholly decoupled from the reference interpreter
(like PyPI behavioural changes), the delegation of authority to the
relevant SIG is more complete:

=================
PEP review and resolution may also occur on a list other than
python-dev (for example, distutils-sig for packaging related PEPs that
don't immediately affect the standard library). In this case, the
"Discussions-To" heading in the PEP will identify the appropriate
alternative list where discussion, review and pronouncement on the PEP
will occur.
=================

(From https://www.python.org/dev/peps/pep-0001/#pep-review-resolution )

Regards,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-October/141843.html below:

[Python-Dev] PEP acceptance and SIGs