[python-committers] [RELEASE] Python 3.8.1rc1 is now available for testing

2019-12-10 Thread Łukasz Langa 
Python 3.8.1rc1 is the release candidate of the first maintenance release of 
Python 3.8.

The Python 3.8 series is the newest feature release of the Python language, and 
it contains many new features and optimizations. You can find Python 3.8.1rc1 
here:

https://www.python.org/downloads/release/python-381rc1/ 

Assuming no critical problems are found prior to 2019-12-16, the scheduled 
release date for 3.8.1 as well as Ned Deily's birthday, no code changes are 
planned between this release candidate and the final release.

That being said, please keep in mind that this is a pre-release of 3.8.1 and as 
such its main purpose is testing.

See the “What’s New in Python 3.8 
” document for more information 
about features included in the 3.8 series. Detailed information about all 
changes made in 3.8.0 can be found in its change log.

Maintenance releases for the 3.8 series will continue at regular bi-monthly 
intervals, with 3.8.2 planned for February 2020.

We hope you enjoy Python 3.8!

Thanks to all of the many volunteers who help make Python Development and these 
releases possible! Please consider supporting our efforts by volunteering 
yourself or through organization contributions to the Python Software 
Foundation.

https://www.python.org/psf/ 


signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/IGJ6ZOAOT2WFY5ZIPRQNTHOSUMPUAO2H/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: [Python-Dev] [RELEASE] Python 3.8.1rc1 is now available for testing

2019-12-10 Thread Christian Tismer 
Hi Łukasz,

tonite I found a critical bug that affects all heaptype extension
classes with a custom (not PyType_Type) type.

the bug is in typeobject.c function type_mro_modified line 309:

if (custom) {
_Py_IDENTIFIER(mro);
mro_meth = lookup_maybe_method(
(PyObject *)type, &PyId_mro, &unbound);
if (mro_meth == NULL)
goto clear;
Py_INCREF(mro_meth);
type_mro_meth = lookup_maybe_method(
(PyObject *)&PyType_Type, &PyId_mro, &unbound);
if (type_mro_meth == NULL)
goto clear;
Py_INCREF(type_mro_meth);
if (mro_meth != type_mro_meth)
goto clear;
Py_XDECREF(mro_meth);
Py_XDECREF(type_mro_meth);
}

This block is wrong because it decrefs a value that comes from
lookup_maybe_method which does not incref.

The code is easily fixed by two Py_INCREF s.

Please let me know how you want to proceed.
This is a critical error, producing negative refcounts.

Cheers -- Chris


On 10.12.19 10:22, Łukasz Langa wrote:
> Python 3.8.1rc1 is the release candidate of the first maintenance
> release of Python 3.8.
> 
> The Python 3.8 series is the newest feature release of the Python
> language, and it contains many new features and optimizations. You can
> find Python 3.8.1rc1 here:
> 
> https://www.python.org/downloads/release/python-381rc1/
> 
> Assuming no critical problems are found prior to *2019-12-16*, the
> scheduled release date for *3.8.1* as well as *Ned Deily's birthday*, no
> code changes are planned between this release candidate and the final
> release.
> 
> That being said, please keep in mind that this is a pre-release of 3.8.1
> and as such its main purpose is testing.
> 
> See the “What’s New in Python 3.8
> ” document for more
> information about features included in the 3.8 series. Detailed
> information about all changes made in 3.8.0 can be found in its change log.
> 
> Maintenance releases for the 3.8 series will continue at regular
> bi-monthly intervals, with *3.8.2* planned for February 2020.
> 
> 
>   We hope you enjoy Python 3.8!
> 
> Thanks to all of the many volunteers who help make Python Development
> and these releases possible! Please consider supporting our efforts by
> volunteering yourself or through organization contributions to the
> Python Software Foundation.
> 
> https://www.python.org/psf/
> 
> 
> ___
> Python-Dev mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at 
> https://mail.python.org/archives/list/[email protected]/message/IGJ6ZOAOT2WFY5ZIPRQNTHOSUMPUAO2H/
> Code of Conduct: http://python.org/psf/codeofconduct/
> 


-- 
Christian Tismer :^)   [email protected]
Software Consulting  : http://www.stackless.com/
Karl-Liebknecht-Str. 121 : https://github.com/PySide
14482 Potsdam: GPG key -> 0xFB7BEE0E
phone +49 173 24 18 776  fax +49 (30) 700143-0023



signature.asc
Description: OpenPGP digital signature
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/6VIEOGQJ433TVQZRYFXQ7SWQM3XRBBKD/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: [Python-Dev] [RELEASE] Python 3.8.1rc1 is now available for testing

2019-12-10 Thread Christian Tismer 
Sorry, I sent the fixed version.
These two incref's are missing!

On 10.12.19 14:16, Christian Tismer wrote:
> Hi Łukasz,
> 
> tonite I found a critical bug that affects all heaptype extension
> classes with a custom (not PyType_Type) type.
> 
> the bug is in typeobject.c function type_mro_modified line 309:
> 
> if (custom) {
> _Py_IDENTIFIER(mro);
> mro_meth = lookup_maybe_method(
> (PyObject *)type, &PyId_mro, &unbound);
> if (mro_meth == NULL)
> goto clear;

This one
> Py_INCREF(mro_meth);
> type_mro_meth = lookup_maybe_method(
> (PyObject *)&PyType_Type, &PyId_mro, &unbound);
> if (type_mro_meth == NULL)
> goto clear;

And this one
> Py_INCREF(type_mro_meth);
> if (mro_meth != type_mro_meth)
> goto clear;
> Py_XDECREF(mro_meth);
> Py_XDECREF(type_mro_meth);
> }
> 
> This block is wrong because it decrefs a value that comes from
> lookup_maybe_method which does not incref.
> 
> The code is easily fixed by two Py_INCREF s.
> 
> Please let me know how you want to proceed.
> This is a critical error, producing negative refcounts.
> 
> Cheers -- Chris

-- 
Christian Tismer :^)   [email protected]
Software Consulting  : http://www.stackless.com/
Karl-Liebknecht-Str. 121 : https://github.com/PySide
14482 Potsdam: GPG key -> 0xFB7BEE0E
phone +49 173 24 18 776  fax +49 (30) 700143-0023



signature.asc
Description: OpenPGP digital signature
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/K2SX7F7P5CXJ7PMK2AAIU7JTAG2AH2A5/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: [Python-Dev] [RELEASE] Python 3.8.1rc1 is now available for testing

2019-12-10 Thread Łukasz Langa 

> On 10 Dec 2019, at 14:16, Christian Tismer  wrote:
> 
> Please let me know how you want to proceed.
> This is a critical error, producing negative refcounts.

Is there a BPO issue for this? If not, there should be, let's discuss there. Is 
this a 3.8 regression?

3.8.1 proper is next Monday, if this fix is handled quickly it will land in 
3.8.1.

- Ł


signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/X4V3MV5BKWCG6T7Q6R2CTJUXE5HPQPJD/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: [Python-Dev] Re: [RELEASE] Python 3.8.1rc1 is now available for testing

2019-12-10 Thread Christian Tismer 
On 10.12.19 14:28, Łukasz Langa wrote:
> 
>> On 10 Dec 2019, at 14:16, Christian Tismer > > wrote:
>>
>> Please let me know how you want to proceed.
>> This is a critical error, producing negative refcounts.
> 
> Is there a BPO issue for this? If not, there should be, let's discuss
> there. Is this a 3.8 regression?
> 
> 3.8.1 proper is next Monday, if this fix is handled quickly it will land
> in 3.8.1.


Yes, this problem exists since the first 3.8.0 version.
I did not create a PR, yet because it took me so long
to understand that this time it was really not a PySide problem ;-)

I will try to produce one ASAP.

-- 
Christian Tismer :^)   [email protected]
Software Consulting  : http://www.stackless.com/
Karl-Liebknecht-Str. 121 : https://github.com/PySide
14482 Potsdam: GPG key -> 0xFB7BEE0E
phone +49 173 24 18 776  fax +49 (30) 700143-0023



signature.asc
Description: OpenPGP digital signature
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/BWHTDGNDKZFE4G6GK7ASSY4WTANBGMZ5/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: [Python-Dev] [RELEASE] Python 3.8.1rc1 is now available for testing

2019-12-10 Thread Victor Stinner 
Can you please open an issue at https://bugs.python.org/ and then post
the link in this thread?

Thanks in advance,
Victor

Le mar. 10 déc. 2019 à 14:18, Christian Tismer  a écrit :
>
> Hi Łukasz,
>
> tonite I found a critical bug that affects all heaptype extension
> classes with a custom (not PyType_Type) type.
>
> the bug is in typeobject.c function type_mro_modified line 309:
>
> if (custom) {
> _Py_IDENTIFIER(mro);
> mro_meth = lookup_maybe_method(
> (PyObject *)type, &PyId_mro, &unbound);
> if (mro_meth == NULL)
> goto clear;
> Py_INCREF(mro_meth);
> type_mro_meth = lookup_maybe_method(
> (PyObject *)&PyType_Type, &PyId_mro, &unbound);
> if (type_mro_meth == NULL)
> goto clear;
> Py_INCREF(type_mro_meth);
> if (mro_meth != type_mro_meth)
> goto clear;
> Py_XDECREF(mro_meth);
> Py_XDECREF(type_mro_meth);
> }
>
> This block is wrong because it decrefs a value that comes from
> lookup_maybe_method which does not incref.
>
> The code is easily fixed by two Py_INCREF s.
>
> Please let me know how you want to proceed.
> This is a critical error, producing negative refcounts.
>
> Cheers -- Chris
>
>
> On 10.12.19 10:22, Łukasz Langa wrote:
> > Python 3.8.1rc1 is the release candidate of the first maintenance
> > release of Python 3.8.
> >
> > The Python 3.8 series is the newest feature release of the Python
> > language, and it contains many new features and optimizations. You can
> > find Python 3.8.1rc1 here:
> >
> > https://www.python.org/downloads/release/python-381rc1/
> >
> > Assuming no critical problems are found prior to *2019-12-16*, the
> > scheduled release date for *3.8.1* as well as *Ned Deily's birthday*, no
> > code changes are planned between this release candidate and the final
> > release.
> >
> > That being said, please keep in mind that this is a pre-release of 3.8.1
> > and as such its main purpose is testing.
> >
> > See the “What’s New in Python 3.8
> > ” document for more
> > information about features included in the 3.8 series. Detailed
> > information about all changes made in 3.8.0 can be found in its change log.
> >
> > Maintenance releases for the 3.8 series will continue at regular
> > bi-monthly intervals, with *3.8.2* planned for February 2020.
> >
> >
> >   We hope you enjoy Python 3.8!
> >
> > Thanks to all of the many volunteers who help make Python Development
> > and these releases possible! Please consider supporting our efforts by
> > volunteering yourself or through organization contributions to the
> > Python Software Foundation.
> >
> > https://www.python.org/psf/
> >
> >
> > ___
> > Python-Dev mailing list -- [email protected]
> > To unsubscribe send an email to [email protected]
> > https://mail.python.org/mailman3/lists/python-dev.python.org/
> > Message archived at 
> > https://mail.python.org/archives/list/[email protected]/message/IGJ6ZOAOT2WFY5ZIPRQNTHOSUMPUAO2H/
> > Code of Conduct: http://python.org/psf/codeofconduct/
> >
>
>
> --
> Christian Tismer :^)   [email protected]
> Software Consulting  : http://www.stackless.com/
> Karl-Liebknecht-Str. 121 : https://github.com/PySide
> 14482 Potsdam: GPG key -> 0xFB7BEE0E
> phone +49 173 24 18 776  fax +49 (30) 700143-0023
>
> ___
> python-committers mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at 
> https://mail.python.org/archives/list/[email protected]/message/6VIEOGQJ433TVQZRYFXQ7SWQM3XRBBKD/
> Code of Conduct: https://www.python.org/psf/codeofconduct/



-- 
Night gathers, and now my watch begins. It shall not end until my death.
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/G5FRX7T5HC4QEIJSSNBUJWKSSBV2CV3R/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: [Python-Dev] [RELEASE] Python 3.8.1rc1 is now available for testing

2019-12-10 Thread Christian Tismer 
Howdy,

I have produced this:
https://bugs.python.org/issue39016

No idea if it's correct, doing that too rarely.

Cheers -- Chris


On 10.12.19 14:34, Victor Stinner wrote:
> Can you please open an issue at https://bugs.python.org/ and then post
> the link in this thread?
> 
> Thanks in advance,
> Victor
> 
> Le mar. 10 déc. 2019 à 14:18, Christian Tismer  a écrit 
> :
>>
>> Hi Łukasz,
>>
>> tonite I found a critical bug that affects all heaptype extension
>> classes with a custom (not PyType_Type) type.
>>
>> the bug is in typeobject.c function type_mro_modified line 309:
>>
>> if (custom) {
>> _Py_IDENTIFIER(mro);
>> mro_meth = lookup_maybe_method(
>> (PyObject *)type, &PyId_mro, &unbound);
>> if (mro_meth == NULL)
>> goto clear;
>> Py_INCREF(mro_meth);
>> type_mro_meth = lookup_maybe_method(
>> (PyObject *)&PyType_Type, &PyId_mro, &unbound);
>> if (type_mro_meth == NULL)
>> goto clear;
>> Py_INCREF(type_mro_meth);
>> if (mro_meth != type_mro_meth)
>> goto clear;
>> Py_XDECREF(mro_meth);
>> Py_XDECREF(type_mro_meth);
>> }
>>
>> This block is wrong because it decrefs a value that comes from
>> lookup_maybe_method which does not incref.
>>
>> The code is easily fixed by two Py_INCREF s.
>>
>> Please let me know how you want to proceed.
>> This is a critical error, producing negative refcounts.
>>
>> Cheers -- Chris
>>
>>
>> On 10.12.19 10:22, Łukasz Langa wrote:
>>> Python 3.8.1rc1 is the release candidate of the first maintenance
>>> release of Python 3.8.
>>>
>>> The Python 3.8 series is the newest feature release of the Python
>>> language, and it contains many new features and optimizations. You can
>>> find Python 3.8.1rc1 here:
>>>
>>> https://www.python.org/downloads/release/python-381rc1/
>>>
>>> Assuming no critical problems are found prior to *2019-12-16*, the
>>> scheduled release date for *3.8.1* as well as *Ned Deily's birthday*, no
>>> code changes are planned between this release candidate and the final
>>> release.
>>>
>>> That being said, please keep in mind that this is a pre-release of 3.8.1
>>> and as such its main purpose is testing.
>>>
>>> See the “What’s New in Python 3.8
>>> ” document for more
>>> information about features included in the 3.8 series. Detailed
>>> information about all changes made in 3.8.0 can be found in its change log.
>>>
>>> Maintenance releases for the 3.8 series will continue at regular
>>> bi-monthly intervals, with *3.8.2* planned for February 2020.
>>>
>>>
>>>   We hope you enjoy Python 3.8!
>>>
>>> Thanks to all of the many volunteers who help make Python Development
>>> and these releases possible! Please consider supporting our efforts by
>>> volunteering yourself or through organization contributions to the
>>> Python Software Foundation.
>>>
>>> https://www.python.org/psf/
>>>
>>>
>>> ___
>>> Python-Dev mailing list -- [email protected]
>>> To unsubscribe send an email to [email protected]
>>> https://mail.python.org/mailman3/lists/python-dev.python.org/
>>> Message archived at 
>>> https://mail.python.org/archives/list/[email protected]/message/IGJ6ZOAOT2WFY5ZIPRQNTHOSUMPUAO2H/
>>> Code of Conduct: http://python.org/psf/codeofconduct/
>>>
>>
>>
>> --
>> Christian Tismer :^)   [email protected]
>> Software Consulting  : http://www.stackless.com/
>> Karl-Liebknecht-Str. 121 : https://github.com/PySide
>> 14482 Potsdam: GPG key -> 0xFB7BEE0E
>> phone +49 173 24 18 776  fax +49 (30) 700143-0023
>>
>> ___
>> python-committers mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
>> https://mail.python.org/mailman3/lists/python-committers.python.org/
>> Message archived at 
>> https://mail.python.org/archives/list/[email protected]/message/6VIEOGQJ433TVQZRYFXQ7SWQM3XRBBKD/
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
> 
> 
> 


-- 
Christian Tismer :^)   [email protected]
Software Consulting  : http://www.stackless.com/
Karl-Liebknecht-Str. 121 : https://github.com/PySide
14482 Potsdam: GPG key -> 0xFB7BEE0E
phone +49 173 24 18 776  fax +49 (30) 700143-0023
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/6A7UURL224NQQFHRJXRQYKVTRWNHLLGR/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Reminder to vote for the 2020 Steering Council

2019-12-10 Thread Ewa Jodlowska 
Hi!

*This is a reminder that voting will end December 16, 2019 12:00 UTC.*

If you have not yet voted, please do so soon. Momentarily, Ernest will
resend all the ballots to those that have not voted yet. If you cannot find
your ballot, try searching spam for [email protected].

If you run into any issues, please email myself ([email protected]) and Ernest
([email protected]).


Thank you,

Ewa
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/V6RLPDRYNOE6PCXIA4DFSGIZ6ND5GTJU/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Possible bug in voting system ? (was: Re: Reminder to vote for the 2020 Steering Council)

2019-12-10 Thread M.-A. Lemburg 
I had been waiting for the ballot email, but have not received any.

I then checked the voters list and came across this section in the
readme:

"""
According to PEP 13, active membership is defined as "any non-trivial
contribution in two years". As such, the coredev active command will
create a pickle file containing the list of coredev.common.CoreDev
instances of people who have authored or committed to the CPython repo
in the past two years.
"""

as well as

"""
The coredev voters command will take an active membership pickle and
generate a CSV file to act as a voter roll.
"""

Looking at https://github.com/python/voters/blob/master/coredev/active.py
it seems the implementation is not working with a status flag for
each voter, but literally converts core members to inactive
based on just the commit history.

That's not in line with PEP 13 (even though this is quoted in the
readme), which says:

"""
Those who haven't made any non-trivial contribution in two years may be
asked to move themselves to this category, and moved there if they don't
respond.
"""

The conversion to an inactive dev is something that core devs need
to be asked to agree to, and thus needs to be managed as a status
flag, not depend on commits to the repo.

Regardless of the logic, I also find it highly questionable that
core devs who are no longer committing to the repo, but have put in
quite a bit of time into the project get their voting rights removed.

Even when not actively maintaining code, they still do have a
significant stake in the code base, own the copyright to their
contributions and thus should have a say on the future of Python.

As it turns out I was removed from the list of voters by the above
script, without being asked, and would like to be added back again.

Thanks,
-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts (#1, Dec 10 2019)
>>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
>>> Python Database Interfaces ...   http://products.egenix.com/
>>> Plone/Zope Database Interfaces ...   http://zope.egenix.com/


::: We implement business ideas - efficiently in both time and costs :::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
   Registered at Amtsgericht Duesseldorf: HRB 46611
   http://www.egenix.com/company/contact/
  http://www.malemburg.com/



On 10.12.2019 20:52, Ewa Jodlowska wrote:
> Hi!
> 
> *This is a reminder that voting will end December 16, 2019 12:00 UTC.*
> 
> If you have not yet voted, please do so soon. Momentarily, Ernest will
> resend all the ballots to those that have not voted yet. If you cannot
> find your ballot, try searching spam for [email protected]
> .
> 
> If you run into any issues, please email myself ([email protected]
> ) and Ernest ([email protected]
> ).
> 
> 
> Thank you,
> 
> Ewa
> 
> 
> 
> ___
> python-committers mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at 
> https://mail.python.org/archives/list/[email protected]/message/V6RLPDRYNOE6PCXIA4DFSGIZ6ND5GTJU/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
> 
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/INEF7B3X2MLZX2YSA66ZAOCIVSVQTHGI/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Possible bug in voting system ? (was: Re: Reminder to vote for the 2020 Steering Council)

2019-12-10 Thread Senthil Kumaran 
> As it turns out I was removed from the list of voters by the above
> script, without being asked, and would like to be added back again.


I support this, and I hope this can be rectified for this election
period itself.

Thank you,
Senthil


On Tue, Dec 10, 2019 at 12:52 PM M.-A. Lemburg  wrote:

> I had been waiting for the ballot email, but have not received any.
>
> I then checked the voters list and came across this section in the
> readme:
>
> """
> According to PEP 13, active membership is defined as "any non-trivial
> contribution in two years". As such, the coredev active command will
> create a pickle file containing the list of coredev.common.CoreDev
> instances of people who have authored or committed to the CPython repo
> in the past two years.
> """
>
> as well as
>
> """
> The coredev voters command will take an active membership pickle and
> generate a CSV file to act as a voter roll.
> """
>
> Looking at https://github.com/python/voters/blob/master/coredev/active.py
> it seems the implementation is not working with a status flag for
> each voter, but literally converts core members to inactive
> based on just the commit history.
>
> That's not in line with PEP 13 (even though this is quoted in the
> readme), which says:
>
> """
> Those who haven't made any non-trivial contribution in two years may be
> asked to move themselves to this category, and moved there if they don't
> respond.
> """
>
> The conversion to an inactive dev is something that core devs need
> to be asked to agree to, and thus needs to be managed as a status
> flag, not depend on commits to the repo.
>
> Regardless of the logic, I also find it highly questionable that
> core devs who are no longer committing to the repo, but have put in
> quite a bit of time into the project get their voting rights removed.
>
> Even when not actively maintaining code, they still do have a
> significant stake in the code base, own the copyright to their
> contributions and thus should have a say on the future of Python.
>
> As it turns out I was removed from the list of voters by the above
> script, without being asked, and would like to be added back again.
>
> Thanks,
> --
> Marc-Andre Lemburg
> eGenix.com
>
> Professional Python Services directly from the Experts (#1, Dec 10 2019)
> >>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
> >>> Python Database Interfaces ...   http://products.egenix.com/
> >>> Plone/Zope Database Interfaces ...   http://zope.egenix.com/
> 
>
> ::: We implement business ideas - efficiently in both time and costs :::
>
>eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
> D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
>Registered at Amtsgericht Duesseldorf: HRB 46611
>http://www.egenix.com/company/contact/
>   http://www.malemburg.com/
>
>
>
> On 10.12.2019 20:52, Ewa Jodlowska wrote:
> > Hi!
> >
> > *This is a reminder that voting will end December 16, 2019 12:00 UTC.*
> >
> > If you have not yet voted, please do so soon. Momentarily, Ernest will
> > resend all the ballots to those that have not voted yet. If you cannot
> > find your ballot, try searching spam for [email protected]
> > .
> >
> > If you run into any issues, please email myself ([email protected]
> > ) and Ernest ([email protected]
> > ).
> >
> >
> > Thank you,
> >
> > Ewa
> >
> >
> >
> > ___
> > python-committers mailing list -- [email protected]
> > To unsubscribe send an email to [email protected]
> > https://mail.python.org/mailman3/lists/python-committers.python.org/
> > Message archived at
> https://mail.python.org/archives/list/[email protected]/message/V6RLPDRYNOE6PCXIA4DFSGIZ6ND5GTJU/
> > Code of Conduct: https://www.python.org/psf/codeofconduct/
> >
> ___
> python-committers mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/[email protected]/message/INEF7B3X2MLZX2YSA66ZAOCIVSVQTHGI/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/SR7DS3BBG7PMWMEYBEWXELBPGR664LHX/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Possible bug in voting system ? (was: Re: Reminder to vote for the 2020 Steering Council)

2019-12-10 Thread Paul Moore 
On Tue, 10 Dec 2019 at 21:07, Senthil Kumaran  wrote:
>
> > As it turns out I was removed from the list of voters by the above
> > script, without being asked, and would like to be added back again.
>
> I support this, and I hope this can be rectified for this election period 
> itself.

+1 from me as well.

Paul
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/DRI5AJFAX3MMHOJWPJLEV2ELLJCJPGJC/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Possible bug in voting system ? (was: Re: Reminder to vote for the 2020 Steering Council)

2019-12-10 Thread Nick Coghlan 
On Wed, 11 Dec 2019 at 06:52, M.-A. Lemburg  wrote:
> The conversion to an inactive dev is something that core devs need
> to be asked to agree to, and thus needs to be managed as a status
> flag, not depend on commits to the repo.

All committers were asked to check the voter list in mid-November,
before the ballot period started:
https://mail.python.org/archives/list/[email protected]/thread/EXT5XHEHPGJQS3LW5UG7SK63C2GJDJ2P/

The relevant section in PEP 13 is this one:

==
There's no time limit on core team membership. However, in order to
provide the general public with a reasonable idea of how many people
maintain Python, core team members who have stopped contributing are
encouraged to declare themselves as "inactive". Those who haven't made
any non-trivial contribution in two years may be asked to move
themselves to this category, and moved there if they don't respond. To
record and honor their contributions, inactive team members will
continue to be listed alongside active core team members; and, if they
later resume contributing, they can switch back to active status at
will. While someone is in inactive status, though, they lose their
active privileges like voting or nominating for the steering council,
and commit access.
==

So everyone *was* asked if they wanted to be kept as active for this
election, but it wasn't explicitly emphasised to the folks that were
otherwise going to being marked as inactive that this was happening
(as it had to be inferred from the absence of your name, rather than
being called out as a list of voters that had been flagged as
potentially inactive since the last voter roll was generated).

Cheers,
Nick.


-- 
Nick Coghlan   |   [email protected]   |   Brisbane, Australia
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/JNJYVHLFW7RPWNWW77ETNKQOHXZS57HU/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: [RELEASE] Python 3.8.1rc1 is now available for testing

2019-12-10 Thread Jason R. Coombs 
I think I missed the announcement of the cutoff date for 3.8.1; I was hoping to 
get some bug fixes in for 
importlib.metadata.

These aren’t crucial bugfixes, but it would be nice not to have them linger for 
months. Would you consider including these, especially as the code changes are 
pre-vetted in the backport (released 12-01)? Or maybe only if there’s another 
RC for another reason?

If it’s too disruptive, that’s no big deal. Your call.

Thanks for the release work.

On 10 Dec, 2019, at 04:22, Łukasz Langa 
mailto:[email protected]>> wrote:


Python 3.8.1rc1 is the release candidate of the first maintenance release of 
Python 3.8.

The Python 3.8 series is the newest feature release of the Python language, and 
it contains many new features and optimizations. You can find Python 3.8.1rc1 
here:

https://www.python.org/downloads/release/python-381rc1/

Assuming no critical problems are found prior to 2019-12-16, the scheduled 
release date for 3.8.1 as well as Ned Deily's birthday, no code changes are 
planned between this release candidate and the final release.

That being said, please keep in mind that this is a pre-release of 3.8.1 and as 
such its main purpose is testing.

See the “What’s New in Python 
3.8” document for more 
information about features included in the 3.8 series. Detailed information 
about all changes made in 3.8.0 can be found in its change log.

Maintenance releases for the 3.8 series will continue at regular bi-monthly 
intervals, with 3.8.2 planned for February 2020.

We hope you enjoy Python 3.8!

Thanks to all of the many volunteers who help make Python Development and these 
releases possible! Please consider supporting our efforts by volunteering 
yourself or through organization contributions to the Python Software 
Foundation.

https://www.python.org/psf/

___
python-committers mailing list -- 
[email protected]
To unsubscribe send an email to 
[email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/IGJ6ZOAOT2WFY5ZIPRQNTHOSUMPUAO2H/
Code of Conduct: https://www.python.org/psf/codeofconduct/

___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/YX4DTT26DNYQFUBW5EHPODYMRGT4ZOQX/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Possible bug in voting system ? (was: Re: Reminder to vote for the 2020 Steering Council)

2019-12-10 Thread Antoine Pitrou 

Le 10/12/2019 à 23:57, Nick Coghlan a écrit :
> On Wed, 11 Dec 2019 at 06:52, M.-A. Lemburg  wrote:
>> The conversion to an inactive dev is something that core devs need
>> to be asked to agree to, and thus needs to be managed as a status
>> flag, not depend on commits to the repo.
> 
> All committers were asked to check the voter list in mid-November,
> before the ballot period started:
> https://mail.python.org/archives/list/[email protected]/thread/EXT5XHEHPGJQS3LW5UG7SK63C2GJDJ2P/
> 
> The relevant section in PEP 13 is this one:
> [snip]

Well, PEP 13 does not seem mentioned in the e-mail above.  The
relationship ("I have to check this list because I might have been
classified as an inactive core developer") didn't look obvious to me.

> So everyone *was* asked if they wanted to be kept as active for this
> election,

That's not what the e-mail above says, at least.  It just says "check
you're on the list", but does not detail the reasons why one would not
be in the list.  Perhaps you can find out the reason by digging through
hyperlinks, but that's not very intuitive ;-)

Regards

Antoine.
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/MSC6P3MG4WH3I5EPRSBBF74LSKXUJILU/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Possible bug in voting system ?

2019-12-10 Thread Ethan Furman 

On 12/10/2019 02:57 PM, Nick Coghlan wrote:

On Wed, 11 Dec 2019 at 06:52, M.-A. Lemburg wrote:



The conversion to an inactive dev is something that core devs need
to be asked to agree to, and thus needs to be managed as a status
flag, not depend on commits to the repo.


All committers were asked to check the voter list in mid-November,
before the ballot period started:

[...]

So everyone *was* asked if they wanted to be kept as active for this
election


Being asked to check the rolls is not the same thing as being asked if one 
still wants to be considered active.  (I would suggest that this is definitely 
a time when explicit is better than implicit.)

And what if MAL had checked?  How would he have declared he still wanted to be 
active?

--
~Ethan~
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/4MGAV2R3T5O3MY4ATH2KC5LIGSJZYHHQ/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Possible bug in voting system ? (was: Re: Reminder to vote for the 2020 Steering Council)

2019-12-10 Thread Brett Cannon 
We discussed the situation on the steering council and we are fine with making 
an exception for folks who felt caught off-guard asking Ernest to be added to 
the voter roll even though voting has already started.

In the new year I will work with Ernest to draft up a proposal for changing PEP 
13 to make this section of it clearer in regards to the expectations for 
qualifying to vote.
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/HK4LNQEA3CMSZTGOZTC766NIS4CNPG7O/
Code of Conduct: https://www.python.org/psf/codeofconduct/