[Python-Dev] Python release timeline plot

2021-05-02 Thread Michał Górny 
Hi,

I've been working on visualizing some data on Python in Gentoo, and made
a timeline of Python releases as a side result.  I've figured some of
you might be interested, so I've decided to share it.  The result:

https://mgorny.pl/python-timeline.html

Script: https://github.com/mgorny/gpyutils/blob/master/timeline.py
Data:   https://github.com/mgorny/gpyutils/blob/master/timeline.toml

I've (roughly) covered the versions between 2.5 and 3.10 (2.5 is
the oldest I've seen during my time in Gentoo, also the timeline's
gotten narrow already).

dev covers the period between start of development and first alpha. 
alpha goes from a1 to b1, beta from b1 to rc1, rc from rc1 to final. 
stable goes to the last bugfix release, and security from that until
the last security release.

A few notes:

1. The data is cut off to the right, and for technical reasons this
means tooltips will display early end dates.

2. The right-most data is based on approximate dates where schedules
aren't precise, esp. 3.10 assumes 'approximately 18 months' for stable
status.

3. Start of development is only mentioned in the newest schedules.  For
older versions, I've took the data of the commit changing PYTHON_VERSION
in configure.{ac,in} (which seems to match start of development in newer
schedules).

4. Where data on last bugfix release wasn't available in schedules, I've
looked through release notes.

5. I've deliberately skipped dev period for 2.5 not to overstretch it to
the left.

If you see any mistakes, please let me know.

-- 
Best regards,
Michał Górny


___
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/CLSHKQAFYXYPMRX7J6RWUS2XQSRMIBUN/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Anyone else gotten bizarre personal replies to mailing list posts?

2021-05-02 Thread Jeff Allen 
Yes, I got one from the same address today. Thanks for pointing out 
these are individual peformances: it was annoying when I thought it was 
spam to the list.


Although Hoi Lam Poon is a real (female) name, it may signify a 
generated lampoon.


Jeff Allen

On 23/04/2021 16:38, Nathaniel Smith wrote:
I just got the reply below sent directly to my personal account, and 
I'm confused about what's going on. If it's just a one off I'll chalk 
it up to random internet weirdness, but if other folks are getting 
these too it might be something the list admins should look into? 
Or... something?


-- Forwarded message -
From: *Hoi lam Poon* >
___
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/3EA53I3Y72ACEPDVG467NMNTXHRL3NXL/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Python release timeline plot

2021-05-02 Thread Irit Katriel via Python-Dev 
This is just what I needed, thanks! 

I’m in the process of preparing a presentation for my team at Bank of America 
about how the dev lifecycle of our system (Quartz risk platform) interplays 
with the dev lifecycle of Python (and how we can do better).  I will use this.


> On 2 May 2021, at 08:33, Michał Górny  wrote:
> 
> Hi,
> 
> I've been working on visualizing some data on Python in Gentoo, and made
> a timeline of Python releases as a side result.  I've figured some of
> you might be interested, so I've decided to share it.  The result:
> 
> https://mgorny.pl/python-timeline.html
> 
> Script: https://github.com/mgorny/gpyutils/blob/master/timeline.py
> Data:   https://github.com/mgorny/gpyutils/blob/master/timeline.toml
> 
> I've (roughly) covered the versions between 2.5 and 3.10 (2.5 is
> the oldest I've seen during my time in Gentoo, also the timeline's
> gotten narrow already).
> 
> dev covers the period between start of development and first alpha. 
> alpha goes from a1 to b1, beta from b1 to rc1, rc from rc1 to final. 
> stable goes to the last bugfix release, and security from that until
> the last security release.
> 
> A few notes:
> 
> 1. The data is cut off to the right, and for technical reasons this
> means tooltips will display early end dates.
> 
> 2. The right-most data is based on approximate dates where schedules
> aren't precise, esp. 3.10 assumes 'approximately 18 months' for stable
> status.
> 
> 3. Start of development is only mentioned in the newest schedules.  For
> older versions, I've took the data of the commit changing PYTHON_VERSION
> in configure.{ac,in} (which seems to match start of development in newer
> schedules).
> 
> 4. Where data on last bugfix release wasn't available in schedules, I've
> looked through release notes.
> 
> 5. I've deliberately skipped dev period for 2.5 not to overstretch it to
> the left.
> 
> If you see any mistakes, please let me know.
> 
> -- 
> Best regards,
> Michał Górny
> 
> 
> ___
> 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/CLSHKQAFYXYPMRX7J6RWUS2XQSRMIBUN/
> Code of Conduct: http://python.org/psf/codeofconduct/
___
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/UJFL2SIBSOI6HPY4Y32WG5P7TI4FB6RT/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Existing asyncio features scheduled for removal in Python 3.9 and 3.10

2021-05-02 Thread Illia Volochii 
> I would prefer to wait for 3.11 to remove more deprecated features,
> these ones can survive a little bit longer.
>
> If possible, I suggest to remove functions at the beginning of a new
> Python development cycle, rather than just before the feature freeze.
> So projects tested with the development branch of Python can detect
> issues early and we can more time to either fix these projects, or to
> consider reverting the removals to give more time for updating these
> projects.

Fair enough, Victor :)

> It's common that we forget to remove deprecated functions and so that
> documentation is not accurate. IMO it's not a big deal ;-)

Do you think it is worth updating the documentation and warnings
related to the asyncio features to state that they will be removed in
Python 3.11 instead of 3.9 or 3.10?
___
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/SKHD2UNBGCVHTDDJ3O3YB7PXEB6CTDPU/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Existing asyncio features scheduled for removal in Python 3.9 and 3.10

2021-05-02 Thread Eric V. Smith 

> On May 2, 2021, at 4:25 PM, Illia Volochii  wrote:
> 
> 
>> 
>> I would prefer to wait for 3.11 to remove more deprecated features,
>> these ones can survive a little bit longer.
>> 
>> If possible, I suggest to remove functions at the beginning of a new
>> Python development cycle, rather than just before the feature freeze.
>> So projects tested with the development branch of Python can detect
>> issues early and we can more time to either fix these projects, or to
>> consider reverting the removals to give more time for updating these
>> projects.
> 
> Fair enough, Victor :)
> 
>> It's common that we forget to remove deprecated functions and so that
>> documentation is not accurate. IMO it's not a big deal ;-)
> 
> Do you think it is worth updating the documentation and warnings
> related to the asyncio features to state that they will be removed in
> Python 3.11 instead of 3.9 or 3.10?

I think that’s a good idea. 

Eric


___
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/SNNCH3XH5FAKQMDDJDWMZ7NKEUL4IZPP/
Code of Conduct: http://python.org/psf/codeofconduct/