from:"Łukasz Langa"

[python-committers] [RELEASE] Python 3.11.4, 3.10.12, 3.9.17, 3.8.17, 3.7.17, and 3.12.0 beta 2 are now available

2023-06-06 Thread Łukasz Langa

p-0537/>:
3.7.17 <https://www.python.org/downloads/release/python-3717/>
Security-only release with no binaries. 21 commits.

We hope you enjoy the new releases!

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/>.

–
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>
on behalf of your friendly release team,

Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Pablo Galindo Salgado @pablogsal <https://discuss.python.org/u/pablogsal>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>
Thomas Wouters @thomas <https://discuss.python.org/u/thomas>


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

[python-committers] Python Language Summit at PyCon US 2023 in Salt Lake City

2023-02-07 Thread Łukasz Langa

We’re excited to announce that the signups for the Python Language Summit at
PyCon US 2023 are now open.

Full details at: https://us.pycon.org/2023/events/language-summit/

Just like in 2022, we are doing the Summit as an in-person event. We will be
following the health and safety guidelines
of the wider
conference.

TL;DR

When: Wednesday, April 19, 2023 at 10:00am
Where: Salt Palace Convention Center, room TBD

Who
can attend

We welcome Python core developers and triage team members, active contributors
to CPython and alternative Python implementations, and other community members
with a topic to discuss with core developers.

Who
can propose a discussion topic

If you have discussion items; seeking consensus; awaiting decision on a PEP;
needing help with your core dev work; or have specific questions that need
answers from core developers, please submit a proposal. According to feedback,
our audience prefers more discussions and shorter talks.

In your proposal, please include the following:

why is this topic relevant to the core developers;
what is needed from core developers out of this topic.

How
can I learn what’s happening at the event?

Like in 2022, this year’s event will be covered by @AlexWaygood
. A detailed summary of the event
will be published on the Python Software Foundation Blog
.

Is
this event recorded? Can I watch the live stream?

No, there will be no recording and no live stream available. If you’d like to
participate in discussions, please sign up to attend. If you’d like to listen
in, please wait for Alex’s blog posts after the Summit.

We
hope you have a great event!

Your Language Summit cat herding team,
@ambv & @Senthil

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

[python-committers] [RELEASE] Python 3.11.1, 3.10.9, 3.9.16, 3.8.16, 3.7.16, and 3.12.0 alpha 3 are now available

2022-12-06 Thread Łukasz Langa

binaries. 9 commits.

 
<https://discuss.python.org/t/python-3-11-1-3-10-9-3-9-16-3-8-16-3-7-16-and-3-12-0-alpha-3-are-now-available/21724#python-3716-6>Python
 3.7.16

Get it here, read the change log, check PEP 537  
<https://peps.python.org/pep-0537/>to confirm EOL is coming to this version in 
June 2023:

https://www.python.org/downloads/release/python-3716/ 
<https://www.python.org/downloads/release/python-3716/>

Security-only release with no binaries. 8 commits.

 
<https://discuss.python.org/t/python-3-11-1-3-10-9-3-9-16-3-8-16-3-7-16-and-3-12-0-alpha-3-are-now-available/21724#we-hope-you-enjoy-the-new-releases-7>We
 hope you enjoy the new releases!

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/  <https://www.python.org/psf/>
Your friendly release team,

Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Pablo Galindo Salgado @pablogsal <https://discuss.python.org/u/pablogsal>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>
Thomas Wouters @thomas <https://discuss.python.org/u/thomas>


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

[python-committers] [RELEASE] Python versions 3.10.8, 3.9.15, 3.8.15, 3.7.15 now available

2022-10-11 Thread Łukasz Langa

Déjà vu? Right, a month after the expedited releases we are doing the dance 
again. This coincides with the regular scheduled time for 3.10.8 but since we 
accrued a few fixes in 3.7 - 3.9 as well, we’re again releasing all four 
editions at the same time. We’re not promising to continue at this pace 😅

 
<https://discuss.python.org/t/python-versions-3-10-8-3-9-15-3-8-15-3-7-15-now-available/19889#security-content-this-time-1>Security
 content this time

CVE-2022-40674: bundled libexpat was upgraded from 2.4.7 to 2.4.9 which fixes a 
heap use-after-free vulnerability in function doContent
gh-97616: a fix for a possible buffer overflow in list *= int
gh-97612: a fix for possible shell injection in the example script 
get-remote-certificate.py (this issue originally had a CVE assigned to it, 
which its author withdrew)
gh-96577: a fix for a potential buffer overrun in msilib
 
<https://discuss.python.org/t/python-versions-3-10-8-3-9-15-3-8-15-3-7-15-now-available/19889#python-3108-2>Python
 3.10.8

Get it here: https://www.python.org/downloads/release/python-3108/ 
<https://www.python.org/downloads/release/python-3108/>
As a bugfix release coming a mere month after an out-of-schedule security 
release, 3.10.8 is somewhat smaller compared to 3.9.8 released at the same 
stage of the release cycle a year ago. There’s 151 commits vs 204 in 3.9. It’s 
still a larger release than 3.10.7 at 113 commits. One way or the other, it’s 
worth checking out the change log 
<https://docs.python.org/release/3.10.8/whatsnew/changelog.html>.

 
<https://discuss.python.org/t/python-versions-3-10-8-3-9-15-3-8-15-3-7-15-now-available/19889#and-now-for-something-completely-different-3>And
 now for something completely different

Granular convection is a phenomenon where granular material subjected to 
shaking or vibration will exhibit circulation patterns similar to types of 
fluid convection.

It is sometimes described as the Brazil nut effect when the largest particles 
end up on the surface of a granular material containing a mixture of variously 
sized objects; this derives from the example of a typical container of mixed 
nuts, where the largest will be Brazil nuts.

The phenomenon is also known as the muesli effect since it is seen in packets 
of breakfast cereal containing particles of different sizes but similar 
densities, such as muesli mix.

Under experimental conditions, granular convection of variously sized particles 
has been observed forming convection cells similar to fluid motion.

 
<https://discuss.python.org/t/python-versions-3-10-8-3-9-15-3-8-15-3-7-15-now-available/19889#we-hope-you-enjoy-the-new-releases-4>We
 hope you enjoy the new releases!

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.

Your friendly release team,

Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Pablo Galindo Salgado @pablogsal <https://discuss.python.org/u/pablogsal>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>


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

[python-committers] [RELEASE] Python versions 3.10.7, 3.9.14, 3.8.14, 3.7.14 now available with security content

2022-09-07 Thread Łukasz Langa

We have some security content, and plenty of regular bug fixes for 3.10. Let’s 
dive right in.

 
<https://discuss.python.org/#cve-2020-10735httpscvemitreorgcgi-bincvenamecginamecve-2020-10735-1>CVE-2020-10735
 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10735>
Converting between int and str in bases other than 2 (binary), 4, 8 (octal), 16 
(hexadecimal), or 32 such as base 10 (decimal) now raises a ValueError 
<https://docs.python.org/release/3.10.7/whatsnew/3.10.html#notable-security-feature-in-3-10-7>
 if the number of digits in string form is above a limit to avoid potential 
denial of service attacks due to the algorithmic complexity.

Security releases for 3.9.14, 3.8.14, and 3.7.14 are made available 
simultaneously to address this issue, along with some less urgent security 
content.

Upgrading your installations is highly recommended.

 <https://discuss.python.org/#python-3107-2>Python 3.10.7

Get it here:

https://www.python.org/downloads/release/python-3107/ 
<https://www.python.org/downloads/release/python-3107/>


This bugfix version of Python was released out-of-schedule to address the CVE, 
and as such contains a smaller number of changes compared to 3.10.6 (200 
commits), or in fact 3.9.7 (187 commits) at the same stage of the release cycle 
a year ago. But there’s still over a 100 commits in this latest Python version 
so it’s worth checking out the change log 
<https://docs.python.org/release/3.10.7/whatsnew/changelog.html>.

 <https://discuss.python.org/#and-now-for-something-completely-different-3>And 
now for something completely different

In quantum mechanics, the uncertainty principle (also known as Heisenberg’s 
uncertainty principle) is any of a variety of mathematical inequalities 
asserting a fundamental limit to the accuracy with which the values for certain 
pairs of physical quantities of a particle, such as position and momentum or 
the time and the energy can be predicted from initial conditions.

Such variable pairs are known as complementary variables or canonically 
conjugate variables; and, depending on interpretation, the uncertainty 
principle limits to what extent such conjugate properties maintain their 
approximate meaning, as the mathematical framework of quantum physics does not 
support the notion of simultaneously well-defined conjugate properties 
expressed by a single value.

The uncertainty principle implies that it is in general not possible to predict 
the value of a quantity with arbitrary certainty, even if all initial 
conditions are specified.

 <https://discuss.python.org/#we-hope-you-enjoy-the-new-releases-4>We hope you 
enjoy the new releases!

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.

Your friendly release team,

Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Pablo Galindo Salgado @pablogsal <https://discuss.python.org/u/pablogsal>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>


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

[python-committers] [RELEASE] Python 3.9.13 is now available

2022-05-17 Thread Łukasz Langa

This is the thirteenth maintenance release of Python 3.9. Get it here:
Python 3.9.13 <https://www.python.org/downloads/release/python-3913/>
According to the release calendar specified in PEP 596 
<https://www.python.org/dev/peps/pep-0596/>, Python 3.9.13 is the final regular 
maintenance release. Starting now, the 3.9 branch will only accept security 
fixes and releases of those will be made in source-only form until October 2025.

This is a milestone moment for me as it means that now both of my release 
series are security-only. My work as release manager enters its final stage. 
I’m not crying, you’re crying! 🥲

Compared to the 3.8 series, this last regular bugfix release is still pretty 
active at 166 commits since 3.9.12. In comparison, version 3.8.10, the final 
regular bugfix release of Python 3.8, included only 92 commits. However, it’s 
likely that it was 3.8 that was special here with the governance changes 
occupying core developers’ minds. For reference, version 3.7.8, the final 
regular bugfix release of Python 3.7, included 187 commits.

In any case, 166 commits is quite a few changes, some of which being pretty 
important fixes. Take a look at the change log 
<https://docs.python.org/release/3.9.13/whatsnew/changelog.html> for details.

 
<https://discuss.python.org/t/python-3-9-13-is-now-available/15815#major-new-features-of-the-39-series-compared-to-38-1>Major
 new features of the 3.9 series, compared to 3.8

Some of the new major new features and changes in Python 3.9 are:

PEP 573 <https://www.python.org/dev/peps/pep-0573/>, Module State Access from C 
Extension Methods
PEP 584 <https://www.python.org/dev/peps/pep-0584/>, Union Operators in dict
PEP 585 <https://www.python.org/dev/peps/pep-0585/>, Type Hinting Generics In 
Standard Collections
PEP 593 <https://www.python.org/dev/peps/pep-0593/>, Flexible function and 
variable annotations
PEP 602 <https://www.python.org/dev/peps/pep-0602/>, Python adopts a stable 
annual release cadence
PEP 614 <https://www.python.org/dev/peps/pep-0614/>, Relaxing Grammar 
Restrictions On Decorators
PEP 615 <https://www.python.org/dev/peps/pep-0615/>, Support for the IANA Time 
Zone Database in the Standard Library
PEP 616 <https://www.python.org/dev/peps/pep-0616/>, String methods to remove 
prefixes and suffixes
PEP 617 <https://www.python.org/dev/peps/pep-0617/>, New PEG parser for CPython
BPO 38379 <https://bugs.python.org/issue38379>, garbage collection does not 
block on resurrected objects;
BPO 38692 <https://bugs.python.org/issue38692>, os.pidfd_open added that allows 
process management without races and signals;
BPO 39926 <https://bugs.python.org/issue39926>, Unicode support updated to 
version 13.0.0;
BPO 1635741 <https://bugs.python.org/issue1635741>, when Python is initialized 
multiple times in the same process, it does not leak memory anymore;
A number of Python builtins (range, tuple, set, frozenset, list, dict) are now 
sped up using PEP 590 <https://www.python.org/dev/peps/pep-0590> vectorcall;
A number of Python modules (_abc, audioop, _bz2, _codecs, _contextvars, _crypt, 
_functools, _json, _locale, operator, resource, time, _weakref) now use 
multiphase initialization as defined by PEP 489 
<https://www.python.org/dev/peps/pep-0489/>;
A number of standard library modules (audioop, ast, grp, _hashlib, pwd, 
_posixsubprocess, random, select, struct, termios, zlib) are now using the 
stable ABI defined by PEP 384 <https://www.python.org/dev/peps/pep-0384/>.
You can find a more comprehensive list in this release’s “What’s New 
<https://docs.python.org/release/3.9.13/whatsnew/3.9.html>” document.

 
<https://discuss.python.org/t/python-3-9-13-is-now-available/15815#we-hope-you-enjoy-python-39-2>We
 hope you enjoy Python 3.9!

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.

Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>


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

[python-committers] [RELEASE] Python 3.10.4 and 3.9.12 are now available out of schedule

2022-03-24 Thread Łukasz Langa

Did anybody say cursed releases 
<https://discuss.python.org/t/python-3-10-3-3-9-11-3-8-13-and-3-7-13-are-now-available-with-security-content/14353>?
 Well, it turns out that 3.10.3 and 3.9.11 both shipped a regression which 
caused those versions not to build on Red Hat Enterprise Linux 6. While this 
11-year-old version is now out of maintenance support 
<https://access.redhat.com/support/policy/updates/errata>, it’s still used in 
production workloads. Some of those rely on Python 3.9 and/or 3.10. In 
particular, our own manylinux2010 
<https://github.com/pypa/manylinux/tree/manylinux2010_x86_64_centos6_no_vsyscall>
 image used to build widely compatible Linux wheels is based on CentOS 6. 
(Don’t worry, we do have newer manylinux* variants, see PEP 599 
<https://peps.python.org/pep-0599/> and PEP 600 
<https://peps.python.org/pep-0600/> for details.)

Due to the out-of-schedule release, the respective versions released today 
contain a very limited set of changes. Python 3.9.12 only contains 12 other bug 
fixes on top of 3.9.11. Python 3.10.4 only contains 10 other bug fixes on top 
of 3.10.3.

Get 3.10.4 here: Python Release 3.10.4 | Python.org 
<https://www.python.org/downloads/release/python-3104>
Get 3.9.12 here: Python Release 3.9.12 | Python.org 
<https://www.python.org/downloads/release/python-3912>
Hopefully, the third time’s a charm and we’ll return no sooner than May with 
the regularly scheduled bug fix releases of 3.9 and 3.10.

 
<https://discuss.python.org/t/python-3-10-4-and-3-9-12-are-now-available-out-of-schedule/14568#we-hope-you-enjoy-the-new-releases-1>We
 hope you enjoy the new releases

Your friendly release team,
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>
Pablo Galindo Salgado @pablogsal <https://discuss.python.org/u/pablogsal>
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>


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

[python-committers] [RELEASE] Python 3.10.3, 3.9.11, 3.8.13, and 3.7.13 are now available with security content

2022-03-16 Thread Łukasz Langa

. In turn, the 
changes in 3.7.13 
<https://docs.python.org/release/3.7.13/whatsnew/changelog.html> look almost 
identical to the ones in 3.8.13.

Python 3.7 will continue to receive source-only releases until June 2023.


 
<https://discuss.python.org/t/python-3-10-3-3-9-11-3-8-13-and-3-7-13-are-now-available-with-security-content/14353#we-hope-you-enjoy-the-new-releases-5>We
 hope you enjoy the new releases

Your friendly release team,
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>
Pablo Galindo Salgado @pablogsal <https://discuss.python.org/u/pablogsal>
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>


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

[python-committers] [RELEASE] Python 3.10.2, 3.9.10, and 3.11.0a4 are now available

2022-01-14 Thread Łukasz Langa

 3.11.0a5, currently scheduled for 
Wednesday, 2022-02-02.


 
<https://discuss.python.org/t/python-3-10-2-3-9-10-and-3-11-0a4-are-now-available/13146#python-36-is-pining-for-the-fjords-4>Python
 3.6 is pining for the fjords

Python 3.6 is no more. It’s an ex-Python. It has ceased to be. On December 23rd 
2021 is has reached its end-of-life phase 
<https://www.python.org/dev/peps/pep-0494/> after five successful years.

It’s been the first truly popular Python 3 release, introducing f-strings to 
the world and making big improvements to both asyncio (async generators!) and 
typing (variable annotations!).

We’d like to congratulate Ned Deily @nad <https://discuss.python.org/u/nad> on 
successfully driving the 3.6 series to completion as Release Manager. He’s not 
fully retired yet, as 3.7, which he is also managing, is still receiving 
security patches until June 2023.


 
<https://discuss.python.org/t/python-3-10-2-3-9-10-and-3-11-0a4-are-now-available/13146#we-hope-you-enjoy-the-new-releases-5>We
 hope you enjoy the new releases

Your friendly release team,
Pablo Galindo Salgado @pablogsal <https://discuss.python.org/u/pablogsal>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>


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

[python-committers] [RELEASE] Python 3.9.9 hotfix release is now available

2021-11-15 Thread Łukasz Langa

Get it here: https://www.python.org/downloads/release/python-399/
<https://www.python.org/downloads/release/python-399/>
Python 3.9.9 is the eighth maintenance release of the legacy 3.9 series. Python
3.10 is now the latest feature release series of Python 3. Get the latest
release of 3.10.x here <https://python.org/downloads/>.

3.9.9 was released out of schedule as a hotfix for an argparse regression in
Python 3.9.8 which caused complex command-line tools to fail recognizing
sub-commands properly. Details in BPO-45235
<https://bugs.python.org/issue45235>. There are only three other bugfixes in
this release compared to 3.9.8. See the changelog
<https://docs.python.org/release/3.9.9/whatsnew/changelog.html> for details on
what changed.

Upgrading to 3.9.9 is highly recommended if you’re running Python 3.9.8.

The next Python 3.9 maintenance release will be 3.9.10, currently scheduled for
2022-01-03.

<https://discuss.python.org/t/python-3-9-9-hotfix-release-is-now-available/11978#we-apologize-for-the-inconvenience-1>We
apologize for the inconvenience

…and still hope you’ll enjoy the new release!

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

[python-committers] [RELEASE] Python 3.9.8 and 3.11.0a2 are now available

2021-11-05 Thread Łukasz Langa

Tcl/Tk updates

With the recent release of macOS 12 Monterey, we noticed that tkinter file
dialogs are failing to show up on this new operating system, including in our
built-in IDLE. Thanks to rapid help from the Tk team, and Marc Culler in
particular, we were able to fix the issue by bundling Python 3.9.8 and Python
3.11.0a2 with a fixed Tcl/Tk version. In 3.9.8 it’s a patched 8.6.11 release
while 3.11.0a2 is rocking the bleeding-edge 8.6.12rc1.

Since the issue also affected our latest stable version, 3.10.0, an updated
macOS installer for this version was issued. You can recognize it by the post2
version appendix: python-3.10.0post2-macos11.pkg
<https://www.python.org/ftp/python/3.10.0/python-3.10.0post2-macos11.pkg>. We
didn’t have to bump the version number of Python itself since there are no
Python source differences between this package and the original 3.10.0. The
only difference is the bundled patched Tcl/Tk library.

Initially the original 3.10.0 installer was removed from the website after all
URLs got updated to point to the patched version but it turned out this breaks
some workflows
<https://discuss.python.org/t/disappearing-macos-packages-on-python-org/11737>
so the patched installer is now also available under the original filename.

<https://discuss.python.org/t/python-3-9-8-and-3-11-0a2-are-now-available/11763#python-398-2>Python
3.9.8

Get it here: https://www.python.org/downloads/release/python-398/
<https://www.python.org/downloads/release/python-398/>

Python 3.9.8 is the seventh maintenance release of the legacy 3.9 series.
Python 3.10 is now the latest feature release series of Python 3. Get the
latest release of 3.10.x here <https://python.org/downloads/>.
There’s been 202 commits since 3.9.7 which shows that there’s still
considerable interest in improving Python 3.9. To compare, at the same stage of
the release cycle Python 3.8 received over 25% fewer commits. See the changelog
<https://docs.python.org/release/3.9.8/whatsnew/changelog.html> for details on
what changed.

On macOS, the default installer is now the new universal2 variant. It’s
compatible with Mac OS X 10.9 and newer, including macOS 11 Big Sur and macOS
12 Monterey. You may need to upgrade third-party components, like pip, to the
newest versions. You may experience differences in behavior in IDLE and other
Tk-based applications due to using the newest version of Tk. As always, if you
encounter problems when using this installer variant, please check
https://bugs.python.org <https://bugs.python.org/> for existing reports and for
opening new issues.

The next Python 3.9 maintenance release will be 3.9.9, currently scheduled for
2022-01-03.

<https://discuss.python.org/t/python-3-9-8-and-3-11-0a2-are-now-available/11763#python-3110a2-3>Python
3.11.0a2

Get it here: https://www.python.org/downloads/release/python-3110a2/
<https://www.python.org/downloads/release/python-3110a2/>

Python 3.11 is still in development. This release, 3.11.0a2 is the second of
seven planned alpha releases.
Alpha releases are intended to make it easier to test the current state of new
features and bug fixes and to test the release process.

During the alpha phase, features may be added up until the start of the beta
phase (2022-05-06) and, if necessary, may be modified or deleted up until the
release candidate phase (2022-08-01). Please keep in mind that this is a
preview release and its use is not recommended for production environments.

Many new features for Python 3.11 are still being planned and written. Among
the new major new features and changes so far:

PEP 657 <https://www.python.org/dev/peps/pep-0657/> – Include Fine-Grained
Error Locations in Tracebacks
The Faster CPython Project 1 <https://github.com/faster-cpython> is already
yielding some exciting results: this version of CPython 3.11 is ~12% faster on
the geometric mean of the PyPerformance benchmarks <>, compared to 3.10.0.
(Hey, fellow core developer, if a feature you find important is missing from
this list, let Pablo know <mailto:pablog...@python.org>.)
The next pre-release of Python 3.11 will be 3.11.0a3, currently scheduled for
Monday, 2021-12-06.

<https://discuss.python.org/t/python-3-9-8-and-3-11-0a2-are-now-available/11763#we-hope-you-enjoy-the-new-releases-4>We
hope you enjoy the new releases

Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Pablo Galindo Salgado @pablogsal <https://discuss.python.org/u/pablogsal>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>

[python-committers] Re: Dates for the core dev sprints

2021-10-11 Thread Łukasz Langa


> On 11 Oct 2021, at 22:06, Terry Reedy  wrote:
> 
> On 10/11/2021 2:02 PM, Ewa Jodlowska wrote:
> 
>> core devs only; also don't forget to record your Discord username, which is 
>> formatted as r".+#\d+", to https://github.com/python/voters/ 
>>  if you have not already)
> 
> Is voters/python-core.toml the one and only file to edit?

Yup.

- Ł



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

[python-committers] Re: What is github trying to tell me?

2021-09-08 Thread Łukasz Langa

I looked into this and it looks like there's a blindspot in the Github API 
reporting where it includes a bunch of checks that finished but doesn't list 
checks that haven't started yet at all. In this case the bot reports success 
because there are no pending checks.

Not sure how we can easily improve this since the event that triggers the bot 
simply doesn't contain the missing information. I'll dig further, maybe we can 
just list expected checks somehow in the config to avoid this.

- Ł



> On 4 Sep 2021, at 23:42, Guido van Rossum  wrote:
> 
> I see this all the time and just ignore it. I have a feeling it's due to the 
> miss-islington bot being triggered by some event and checking in on the PR 
> while it is still transitioning. Occasionally I see a very large string of 
> these and assume she's just having a bad day. Also notice that in your PR 
> there are actually two of those failure messages, the second one being 
> suppressed by the GitHub UI.
> 
> But maybe Mariatta has a more reasoned explanation.
> 
> On Sat, Sep 4, 2021 at 1:47 PM Eric V. Smith  > wrote:
> https://github.com/python/cpython/pull/28163 
>  has two messages of:
> 
> @ericvsmith : Status check is done, and it's a 
> failure ❌ .
> 
> Followed by the merge messages, followed by:
> 
> @ericvsmith : Status check is done, and it's a 
> success ✅ .
> 
> What do the failure messages mean? Is it because I didn't wait for the checks 
> to complete before merging?
> 
> (It's a documentation only change that I previously committed to main without 
> incident, so I didn't feel the need to wait for all of the checks to run 
> before merging.)
> 
> Thanks for any insight.
> 
> Eric
> 
> ___
> python-committers mailing list -- python-committers@python.org 
> 
> To unsubscribe send an email to python-committers-le...@python.org 
> 
> https://mail.python.org/mailman3/lists/python-committers.python.org/ 
> 
> Message archived at 
> https://mail.python.org/archives/list/python-committers@python.org/message/U7A4R6TUGBD3KNAF3F2JJGNQ6V7B5G4D/
>  
> 
> Code of Conduct: https://www.python.org/psf/codeofconduct/ 
> 
> 
> 
> --
> --Guido van Rossum (python.org/~guido )
> Pronouns: he/him (why is my pronoun here?) 
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at 
> https://mail.python.org/archives/list/python-committers@python.org/message/VO4XYHUIG6KM66NONOZMMPCQYOBP6YEB/
> Code of Conduct: https://www.python.org/psf/codeofconduct/



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

[python-committers] Re: What is github trying to tell me?

2021-09-08 Thread Łukasz Langa

> On 4 Sep 2021, at 22:15, Eric V. Smith  wrote:
> 
> Is it because I didn't wait for the checks to complete before merging?
> 
> (It's a documentation only change that I previously committed to main without 
> incident, so I didn't feel the need to wait for all of the checks to run 
> before merging.)
> 

While this is somewhat off-topic, I'd like to encourage you not to skip 
required checks on backport branches. We could turn them off if they weren't 
important, in fact quite a few checks are only running on the main branch. We 
leave the rest because backports can easily regress due to differences in 
untouched code. Documentation changes specifically can fail if references 
between branches change or doctests don't have necessary imports. You can also 
trip up a bug in Sphinx 2.4.4 (used by Python 3.9 and 3.8) that is already 
fixed by Sphinx 3.2.1 (used by the main branch and 3.10).

Don't get me wrong, I'm sure you'll use your best judgment. I don't intend to 
police anyone, just wanted to highlight that even innocently looking doc 
changes can break us every now and again.

I understand that you might not have much free time to monitor backports. It's 
fine for you to just leave them, the release managers will sweep them 
periodically.

Cheers!

- Ł

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

[python-committers] Deprecation policy reminder

2021-09-02 Thread Łukasz Langa

Hi there,
I noticed some deprecation activity this week. Nice! I'd just like to remind 
everyone that we have a policy for that described in PEP 387 
  It's a very short PEP so I 
recommend you read it in its entirety. The important piece I want to highlight 
is that we cannot deprecate a feature in one release and remove it in the next 
one. We need at least two releases with the warning.

Relevant quotes:

> Python's yearly release process (PEP 602 
> ) means that the deprecation period 
> must last at least two years.

and:

> Wait for the warning to appear in at least two minor Python versions of the 
> same major version, or one minor version in an older major version (e.g. for 
> a warning in Python 3.10, you either wait until at least Python 3.12 or 
> Python 4.0 to make the change). It's fine to wait more than two releases.

Since this PEP is easy to miss, I linked it to the docs of DeprecationWarning 
in GH-28123 .

Cheers,
Ł


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

[python-committers] [RELEASE] Python 3.9.7 and 3.8.12 are now available

2021-08-30 Thread Łukasz Langa

Python 3.9.7

Get it here: https://www.python.org/downloads/release/python-397/
<https://www.python.org/downloads/release/python-397/>
Python 3.9.7 is the newest major stable release of the Python programming
language, and it contains many new features and optimizations. There’s been 187
commits since 3.9.6 which is a similar amount compared to 3.8 at the same stage
of the release cycle. See the change log
<https://docs.python.org/release/3.9.7/whatsnew/changelog.html> for details.

On macOS, we encourage you to use the universal2 binary installer variant
whenever possible. The legacy 10.9+ Intel-only variant will not be provided for
Python 3.10 and the universal2 variant will become the default download for
3.9.8. You may need to upgrade third-party components, like pip, to later
versions. You may experience differences in behavior in IDLE and other Tk-based
applications due to using the newer version of Tk. As always, if you encounter
problems when using this installer variant, please check
https://bugs.python.org <https://bugs.python.org/> for existing reports and for
opening new issues.

The next Python 3.9 maintenance release will be 3.9.8, currently scheduled for
2021-11-01.

<https://discuss.python.org/t/python-3-9-7-and-3-8-12-now-available/10401#the-second-security-only-release-of-python-38-2>The
Second Security-Only Release of Python 3.8

Get it here: https://www.python.org/downloads/release/python-3812/
<https://www.python.org/downloads/release/python-3812/>
Security content in this release contains four fixes. There are also four
additional fixes for bugs that might have lead to denial-of-service attacks.
Finally, while we’re not providing binary installers anymore, for those users
who produce installers, we upgraded the OpenSSL version used to 1.1.1l. Take a
look at the change log
<https://docs.python.org/release/3.8.12/whatsnew/changelog.html> for details.

According to the release calendar specified in PEP 569
<https://www.python.org/dev/peps/pep-0569/>, Python 3.8 is now in “security
fixes only” stage of its life cycle: 3.8 branch only accepts security fixes and
releases of those are made irregularly in source-only form until October 2024.
Python 3.8 isn’t receiving regular bug fixes anymore, and binary installers are
no longer provided for it. Python 3.8.10 was the last full bugfix release of
Python 3.8 with binary installers.

<https://discuss.python.org/t/python-3-9-7-and-3-8-12-now-available/10401#security-releases-of-3712-and-3615-3>Security
releases of 3.7.12 and 3.6.15

Those aren’t ready just yet but are soon to follow.

Similarly to 3.8, Python 3.7 and 3.6 are now in “security fixes only” stage of
their life cycle. Python 3.7 will be providing source archives until June 2023
while Python 3.6 ends its life in December 2021.

<https://discuss.python.org/t/python-3-9-7-and-3-8-12-now-available/10401#we-hope-you-enjoy-the-new-releases-4>We
hope you enjoy the new releases

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

[python-committers] Developer in Residence Weekly Report, July 12 - 18

2021-07-17 Thread Łukasz Langa

Hello there,
finishing up on the inaugural week, number-wise we're looking as follows: I 
closed 14 issues and 54 PRs, reviewed 9 PRs, and authored 6 own PRs.

Details at: https://lukasz.langa.pl/1c78554f-f81d-43d0-9c89-a602cafc4c5a/ 


- Ł


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

[python-committers] [RELEASE] Python 3.9.6, 3.8.11, 3.7.11, and 3.6.14 are now available

2021-06-28 Thread Łukasz Langa

Python 3.9.6

Get it here: https://www.python.org/downloads/release/python-396/
<https://www.python.org/downloads/release/python-396/>
Python 3.9.6 is the newest major stable release of the Python programming
language, and it contains many new features and optimizations. There’s been 146
commits since 3.9.5 which is a similar amount compared to 3.8 at the same stage
of the release cycle. See the change log
<https://docs.python.org/release/3.9.6/whatsnew/changelog.html> for details.

On macOS, we encourage you to use the universal2 binary installer variant
whenever possible. The legacy 10.9+ Intel-only variant will not be provided for
Python 3.10 and the universal2 variant will become the default download for
future 3.9.x releases. You may need to upgrade third-party components, like
pip, to later versions once they are released. You may experience differences
in behavior in IDLE and other Tk-based applications due to using the newer
version of Tk. As always, if you encounter problems when using this installer
variant, please check https://bugs.python.org <https://bugs.python.org/> for
existing reports and for opening new issues.

The next Python 3.9 maintenance release will be 3.9.7, currently scheduled for
2021-08-30.

The First Security-Only Release of Python 3.8

Get it here: https://www.python.org/downloads/release/python-3811/
<https://www.python.org/downloads/release/python-3811/>
Security content in this release contains three fixes. There’s also two fixes
for 3.8.10 regressions. Take a look at the change log
<https://docs.python.org/release/3.8.11/whatsnew/changelog.html> for details.

According to the release calendar specified in PEP 569
<https://www.python.org/dev/peps/pep-0569/>, Python 3.8 is now in security
fixes only stage of its life cycle: 3.8 branch only accepts security fixes and
releases of those are made irregularly in source-only form until October 2024.
Python 3.8 isn’t receiving regular bugfixes anymore, and binary installers are
no longer provided for it. Python 3.8.10 was the last full bugfix release of
Python 3.8 with binary installers.

Security releases of 3.7.11 and 3.6.14

Get them here:
https://www.python.org/downloads/release/python-3711/
<https://www.python.org/downloads/release/python-3711/>
https://www.python.org/downloads/release/python-3614/
<https://www.python.org/downloads/release/python-3614/>
Security content in those releases contains five fixes each. Check out the
relevant change logs for 3.7.11
<https://docs.python.org/release/3.7.11/whatsnew/changelog.html> and 3.6.14
<https://docs.python.org/release/3.6.14/whatsnew/changelog.html> for details.

Similarly to 3.8, Python 3.7 and 3.6 are now in security fixes only stage of
their life cycle. Python 3.7 will be providing them until June 2023 while
Python 3.6 ends its life in December 2021.

We hope you enjoy the new releases

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

[python-committers] Branch `main` now open for business but there's some busywork for you

2021-05-03 Thread Łukasz Langa

In case you missed this in the long release announcement e-mail, `master` was 
renamed to `main` and unblocked so you can now continue contributing without 
disruption. Well, almost. You need to:

1. go to your fork on GitHub and rename its default branch; and
2. update your local clones.

For both steps GitHub should give you nice by-the-hand instructions when you go 
to your fork's main page. The first one you do right away, and the second will 
be asynchronous, which took a minute or so on my own fork.

In case it doesn't for some reason, the full guide covering both steps is here:
https://docs.github.com/en/github/administering-a-repository/renaming-a-branch 


Don't be shy to ask if you're unsure how to proceed.

Cheers,
Łukasz

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

[python-committers] [RELEASE] Python 3.8.10, 3.9.5, and 3.10.0b1 are now available

2021-05-03 Thread Łukasz Langa

This has been a very busy day for releases and on behalf of the Python
development community we’re happy to announce the availability of three new
Python releases.

Python 3.10 is now in Beta

Get it here: Python 3.10.0b1
<https://www.python.org/downloads/release/python-3100b1/>
Python 3.10 is still in development. 3.10.0b1 is the first of four planned beta
release previews. Beta release previews are intended to give the wider
community the opportunity to test new features and bug fixes and to prepare
their projects to support the new feature release.

We strongly encourage maintainers of third-party Python projects to test with
3.10 during the beta phase and report issues found to the Python bug tracker
<https://bugs.python.org/> as soon as possible. While the release is planned to
be feature complete entering the beta phase, it is possible that features may
be modified or, in rare cases, deleted up until the start of the release
candidate phase (Monday, 2021-08-02). Our goal is have no ABI changes after
beta 4 and as few code changes as possible after 3.10.0rc1, the first release
candidate. To achieve that, it will be extremely important to get as much
exposure for 3.10 as possible during the beta phase.

Please keep in mind that this is a preview release and its use is not
recommended for production environments.

The next pre-release, the second beta release of Python 3.10, will be 3.10.0b2.
It is currently scheduled for 2021-05-25. Please see PEP 619
<https://www.python.org/dev/peps/pep-0619/> for details.

Development Begins on Python 3.11

With Python 3.10 moving to beta, it received its own 3.10 branch in the
repository <https://github.com/python/cpython/>. All new features are now
targeting Python 3.11, to be released in October 2022.

Using the opportunity with the creation of the 3.10 branch, we renamed the
master branch of the repository to main. It’s been a bit rocky
<https://github.community/t/renaming-python-master-branch-to-main-1-4k-prs-700-repositories-triggered-server-http-error-500/178090>
but looks like we’re open for business. Please rename the main branch of your
personal fork using the guide GitHub will give you when you go to your fork’s
main page. In case of any outstanding issues, please contact the 3.11 RM
<https://devguide.python.org/devcycle/#current-administrators>.

Python 3.9.5

Get it here: Python 3.9.5 <https://www.python.org/downloads/release/python-395/>
Python 3.9.5 is the newest major stable release of the Python programming
language, and it contains many new features and optimizations. There’s been 111
commits since 3.9.4 which is a similar amount compared to 3.8 at the same stage
of the release cycle. See the change log
<https://docs.python.org/release/3.9.5/whatsnew/changelog.html> for details.

On macOS, we encourage you to use the universal2 variant whenever possible. The
legacy 10.9+ Intel-only variant will not be provided for Python 3.10 and the
universal2 variant will become the default download for future 3.9.x releases.
You may need to upgrade third-party components, like pip, to later versions
once they are released. You may experience differences in behavior in IDLE and
other Tk-based applications due to using the newer version of Tk. As always, if
you encounter problems when using this installer variant, please check
https://bugs.python.org <https://bugs.python.org/> for existing reports and for
opening new issues.

The next Python 3.9 maintenance release will be 3.9.6, currently scheduled for
2021-06-28.

The Last Regular Bugfix Release of Python 3.8

Get it here: Python 3.8.10
<https://www.python.org/downloads/release/python-3810/>
According to the release calendar specified in PEP 569
<https://www.python.org/dev/peps/pep-0569/>, Python 3.8.10 is the final regular
maintenance release. Starting now, the 3.8 branch will only accept security
fixes and releases of those will be made in source-only form until October
2024. To keep receiving regular bug fixes, please upgrade to Python 3.9.

Compared to the 3.7 series, this last regular bugfix release is relatively
dormant at 92 commits since 3.8.9. Version 3.7.8, the final regular bugfix
release of Python 3.7, included 187 commits. But there’s a bunch of important
updates here regardless, the biggest being macOS Big Sur and Apple Silicon
build support. This work would not have been possible without the effort of
Ronald Oussoren, Ned Deily, Maxime Bélanger, and Lawrence D’Anna from Apple.
Thank you!

Take a look at the change log
<https://docs.python.org/release/3.8.10/whatsnew/changelog.html> for details.

We hope you enjoy the new releases

Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Pablo Galindo Salgado @pablogsal <https:

[python-committers] [Release management team communication] 3.8.10, the last regular bugfix release for the 3.8 series, is 1 week away

2021-04-26 Thread Łukasz Langa

Hi there,
one week from now I will be marking the 3.8 branch as "security fixes only". I
still see activity on the branch, and there's been a bunch of open pull
requests. I reviewed and merged what I could, closed a few stale ones that had
outstanding failing tests, and there's still two left which I pinged.

I do realize that stars aligned and we will be releasing this last bugfix
version of 3.8 at the same time as 3.9.5, and more importantly 3.10.0 beta 1.
So there might still be some backport pull requests coming my way for 3.8. This
is all good and expected, just be a little conservative whether it makes sense
to backport a particular change. While there's still 2200 open issues on BPO
listing 3.8 as one of the affected versions, I hope we won't be seeing that
many PRs this week ;-)

I'm personally rooting for https://github.com/python/cpython/pull/25274
to get in.

In any case, on Monday, May 3rd at 12pm CEST I will be cutting the 3.8.10
release. Any regular bugfix not merged and buildbot-tested by then will be
omitted. If you need to block this release for any reason, use the BPO "release
blocker" status and mark 3.8 as an affected version.

3.9.5 being less urgent will be made on the same day after 3.8.10 is up on
python.org .

- Ł___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/W5TUMGZXMO3GO6NXDWSSLQQUEUKM3V4K/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] The Python Language Summit 2021 schedule is up

2021-04-09 Thread Łukasz Langa

This is a heads up that the full schedule has been posted at
https://us.pycon.org/2021/summits/language/
. We look forward to have lively
discussions surrounding these topics with those of you who signed up! You
should already have received an e-mail confirming your attendance. If so, and
it mistakenly mentions the year 2020, yes, I know. 20 years of professional
copy-pasting and I still can't do it right. Anyway, if you haven't heard from
us at all, please ping us to sort it out. This is important as we will be
sending the Zoom link for the meetings closer to the date of the event.

We received numerous topic proposals from Python core developers as well as
from members of the wider Python community. This year's attendance list is a
bit wider than in previous years, and we are expecting 65 attendees if
everybody shows up! It was the first year where we had to send out official
rejection letters. I can't say we enjoyed that. We prioritized attendance to
Python core developers, core developers of other Python implementations,
open-source project maintainers, and active contributors to CPython.

There will be a journalist among the attendees writing up a summary of the
event for the PSF blog. Please be on the lookout for those blog posts after the
event.

Mariatta & Łukasz___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/MEMCVZVNAHOUPZHSXN6RIK36TNTAAYLA/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.9.4 hotfix is now available

2021-04-04 Thread Łukasz Langa

Python 3.9.3 was released two days ago on Friday, April 2nd. It contains
important security content listed below for reference. Unfortunately, it also
introduced an unintentional ABI incompatibility, making some C extensions built
with Python 3.9.0 - 3.9.2 crash with Python 3.9.3 on 32-bit systems. To
minimize disruption, I decided to recall 3.9.3 and introduce this hotfix
release: 3.9.4.

We highly recommend upgrading your Python 3.9 installations to 3.9.4 at your
earliest convenience.

Get it here:

https://www.python.org/downloads/release/python-394/
<https://www.python.org/downloads/release/python-394/>
What is “ABI compatibility”?

Python guarantees that within a given language series (like the current 3.9)
binary extensions written in C or C++ and compiled against headers of one
release (like 3.9.0) will be importable from other versions in the same series
(like 3.9.3). If this weren’t the case, library authors would have to ship
separate binary wheels on PyPI for every single bugfix release of Python. That
would be very inconvenient.

<https://discuss.python.org/t/python-3-9-4-hotfix-is-now-available/8056#what-broke-in-python-393>What
broke in Python 3.9.3?

In a fix for a corner-case crash around recursion limits and exceptions, the
PyThreadState struct needed to change. While PyThreadState’s only documented
public member is the *interp field
<https://docs.python.org/3.9/c-api/init.html#c.PyThreadState>, it’s not
uncommon for C extensions to access other fields in this struct as well.

When I approved the backport of this fix, I missed the fact that the variable
size change would change the memory layout of said struct on 32-bit systems (on
64-bit systems alignment rules made the size change backwards compatible).
Merging the backport was a mistake, and so 3.9.4 reverts it to restore
compatibility with binary extensions built against Python 3.9.0 - 3.9.2.
Details in bpo-43710 <https://bugs.python.org/issue43710>.

<https://discuss.python.org/t/python-3-9-4-hotfix-is-now-available/8056#security-content-in-python-393>Security
Content in Python 3.9.3

bpo-43631 <https://bugs.python.org/issue43631>: high-severity CVE-2021-3449 and
CVE-2021-3450 were published for OpenSSL, it’s been upgraded to 1.1.1k in CI,
and macOS and Windows installers.
bpo-42988 <https://bugs.python.org/issue42988>: CVE-2021-3426: Remove the
getfile feature of the pydoc module which could be abused to read arbitrary
files on the disk (directory traversal vulnerability). Moreover, even source
code of Python modules can contain sensitive data like passwords. Vulnerability
reported by David Schwörer.
bpo-43285 <https://bugs.python.org/issue43285>: ftplib no longer trusts the IP
address value returned from the server in response to the PASV command by
default. This prevents a malicious FTP server from using the response to probe
IPv4 address and port combinations on the client network. Code that requires
the former vulnerable behavior may set a trust_server_pasv_ipv4_address
attribute on their ftplib.FTP instances to True to re-enable it.
bpo-43439 <https://bugs.python.org/issue43439>: Add audit hooks for
gc.get_objects(), gc.get_referrers() and gc.get_referents(). Patch by Pablo
Galindo.

<https://discuss.python.org/t/python-3-9-4-hotfix-is-now-available/8056#release-calendar>Release
Calendar

Maintenance releases for the 3.9 series will continue at regular bi-monthly
intervals, with 3.9.5 planned for May 3rd 2021 as well.

<https://discuss.python.org/t/python-3-9-4-hotfix-is-now-available/8056#whats-new>What’s
new?

The Python 3.9 series contains many new features and optimizations over 3.8.
See the “What’s New in Python 3.9
<https://docs.python.org/3.9/whatsnew/3.9.html>” document for more information
about features included in the 3.9 series. We also have a detailed change log
for 3.9.3 <https://docs.python.org/release/3.9.3/whatsnew/changelog.html>
specifically.

Detailed information about all changes made in version 3.8.9 can be found in
its respective changelog
<https://docs.python.org/release/3.8.9/whatsnew/changelog.html>.

<https://discuss.python.org/t/python-3-9-4-hotfix-is-now-available/8056#we-hope-you-enjoy-those-new-releases>We
hope you enjoy those new releases!

Your friendly release team,
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committe

[python-committers] NOTE: Python 3.9.3 contains an unintentional ABI incompatibility leading to crashes on 32-bit systems

2021-04-03 Thread Łukasz Langa

The memory layout of PyThreadState was unintentionally changed in the recent 
3.9.3 bugfix release. This leads to crashes on 32-bit systems when importing 
binary extensions compiled for Python 3.9.0 - 3.9.2. This is a regression.

We will be releasing a hotfix 3.9.4 around 24 hours from now to address this 
issue and restore ABI compatibility with C extensions built for Python 3.9.0 - 
3.9.2.

Details:
https://bugs.python.org/issue43710

- Ł___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/OUCNKMFBNGFK2AI4B7S7MF5O6UVLBSMB/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.9.3 and 3.8.9 are now available

2021-04-02 Thread Łukasz Langa

Those are expedited security releases, recommended to all users. Get them here:

https://www.python.org/downloads/release/python-393/
<https://www.python.org/downloads/release/python-393/>

https://www.python.org/downloads/release/python-389/
<https://www.python.org/downloads/release/python-389/>
Security Content

<https://discuss.python.org/t/python-3-9-3-and-3-8-9-are-now-available/8024#release-calendar>Release
Calendar

Due to the security fixes, those releases are made a month sooner than planned.
I decided to keep the release calendar intact, meaning that the last full
regular maintenance release of Python 3.8 is still planned for May 3rd 2021,
after which it will shift to source releases only for security bug fixes only.
Maintenance releases for the 3.9 series will continue at regular bi-monthly
intervals, with 3.9.3 planned for May 3rd 2021 as well.

<https://discuss.python.org/t/python-3-9-3-and-3-8-9-are-now-available/8024#whats-new>What’s
new?

Detailed information about all changes made in version 3.8.9 can be found in
its respective changelog
<https://docs.python.org/release/3.8.9/whatsnew/changelog.html>.

<https://discuss.python.org/t/python-3-9-3-and-3-8-9-are-now-available/8024#we-hope-you-enjoy-those-new-releases>We
hope you enjoy those new releases!

Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/JQZZT5TEDHUCDWYUEC2PRVBT4RR7267F/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Python Language Summit 2021 Signups Are Now Open

2021-02-24 Thread Łukasz Langa

I’m happy to announce that we’ve opened the sign-up forms for the 2021 Python
Language Summit!

TL;DR

When: Tuesday, May 11, 2021 (4 hours) and Wednesday, May 12, 2021 (4 hours).
Exact times TBD depending on attendee timezones.
Where: Online via Zoom (link will be sent via email to attendees)
Co-chairs: Mariatta Wijaya & Łukasz Langa
Blogger: Joanna Jablonski
Sign up to attend and actively participate: https://forms.gle/cgmGnmQMDhD2mhHY8
<https://forms.gle/cgmGnmQMDhD2mhHY8> (closes after March 22nd, 2021 AoE)
Propose a topic: https://forms.gle/Jui9mxsHrB4fVvAB8
<https://forms.gle/Jui9mxsHrB4fVvAB8> (closes after March 22nd, 2021 AoE)
To get an idea of past Python Language Summits, you can read these blog posts:

2020: Python Software Foundation News: The 2020 Python Language Summit
<https://pyfound.blogspot.com/2020/04/the-2020-python-language-summit.html>
2019: http://pyfound.blogspot.com/2019/05/the-2019-python-language-summit.html
<http://pyfound.blogspot.com/2019/05/the-2019-python-language-summit.html>
2018: The 2018 Python Language Summit [LWN.net]
<https://lwn.net/Articles/754152/>
2017: The 2017 Python Language Summit [LWN.net]
<https://lwn.net/Articles/723251/>
Do I need to sign up if I’m a Python core developer?

Yes please! While in the past we have limited attendance to 50 people, this
time, due to virtual format, we will be a bit more flexible, but will still
keep it small and manageable. We aren’t planning to go beyond 80 participants.
Please register to reserve your space.

Can I sign up if I’m not a Python core developer?

Yes you can. In the past, we had quite a number of participants who were not
Python core devs. Among them were maintainers and representatives from BeeWare,
CircuitPython, PSF board member, PyCharm, PyPA, etc. Register if you want to
participate. Note that until you hear back from us, your attendance is not
confirmed. As explained in the question above, our “space” is more flexible
than usual, but in the interest of maintaining a vigorous discussion space, we
might still be unable to invite everyone who signs up.

What kind of topics are covered?

Python Language Summit is a special event with very specific audience: Python
core developers. Ideally your topic is not an “announcement” or “project
status” but rather something that will encourage further discussion and
questions. The more controversial, the better. An open issue, group of issues,
or a PEP that is awaiting decision are all good topics to propose. You can also
further explain why this is better discussed in person instead of online.

According to last year’s feedback, our audience prefer more discussions and
shorter talks.

Who can present a talk?

Anyone, even if you’re not a Python core developer. However, please understand
that we will have to be selective as space and time are limited. In particular,
we are prioritizing active core contributors, as well as those who we believe
will be able to improve the quality of the discussions at the event and bring a
more diverse perspective to core Python developers. Note that your topic is not
confirmed until you hear back from us.

Code of Conduct

PyCon’s Code of Conduct <https://us.pycon.org/2020/about/code-of-conduct/>
applies and will be enforced.

Thanks!

@mariatta <https://discuss.python.org/u/mariatta> & @ambv
<https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/J4AC33NZ3SUWYF2GOQRBHXLG7ZECIDBW/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.9.2 and 3.8.8 are now available

2021-02-19 Thread Łukasz Langa

Convinced of the wonders of free two-day deliveries, I’m pleased to present you
Python 3.9.2 and 3.8.8. Get them from:

https://www.python.org/downloads/release/python-392/
<https://www.python.org/downloads/release/python-392/>

https://www.python.org/downloads/release/python-388/
<https://www.python.org/downloads/release/python-388/>

Next up, the last full regular maintenance release of Python 3.8 is planned for
May 3rd 2021, after which it will shift to source releases only for security
bug fixes only. Maintenance releases for the 3.9 series will continue at
regular bi-monthly intervals, with 3.9.3 planned for early May 2021.

Why the expedited final release?

This release, just as the candidate before it, contains two security fixes:

bpo-42938 <https://bugs.python.org/issue42938>: Avoid static buffers when
computing the repr of ctypes.c_double and ctypes.c_longdouble values. This
issue was assigned CVE-2021-3177
<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3177>.

bpo-42967 <https://bugs.python.org/issue42967>: Fix web cache poisoning
vulnerability by defaulting the query args separator to &, and allowing the
user to choose a custom separator. This issue was assigned CVE-2021-23336
<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23336>.

Since the announcement of the release candidates for 3.9.2 on 3.8.8, we
received a number of inquiries from end users urging us to expedite the final
releases due to the security content, especially CVE-2021-3177
<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3177>.

This took us somewhat by surprise since we believed security content is
cherry-picked by downstream distributors from source either way, and the RC
releases provide installers for everybody else interested in upgrading in the
meantime. It turns out that release candidates are mostly invisible to the
community and in many cases cannot be used due to upgrade processes which users
have in place.

In turn, the other active release managers and I decided to stop providing
release candidates for bugfix versions. Starting from now on after the initial
3.x.0 final release, all subsequent releases are going to be provided as is in
bi-monthly intervals. The release calendar PEPs for 3.8 and 3.9 have been
updated accordingly.

On the severity of CVE-2021-3177

We recommend you upgrade your systems to Python 3.8.8 or 3.9.2.

Our understanding is that while the CVE is listed as “remote code execution”,
practical exploits of this vulnerability as such are very unlikely due the
following conditions needing to be met for successful RCE:

pass an untrusted floating point number from a remote party to
ctypes.c_double.from_param (note: Python floating point numbers were not
affected);

have that object be passed to repr() (for instance through logging);

have that float point number be valid machine code;

have the buffer overflow overwrite the stack at exactly the right place for the
code to get executed.

In fact, Red Hat’s evaluation of the vulnerability was consistent with ours.
They write: “the highest threat from this vulnerability is to system
availability <https://access.redhat.com/security/cve/cve-2021-3177>.”

To be sure, denial of service through malicious input is also a serious issue.
Thus, to help the community members for whom the release candidate was
insufficient, we are releasing the final versions of 3.9.2 and 3.8.8 today.

What’s new?

The Python 3.9 series contains many new features and optimizations over 3.8.
See the “What’s New in Python 3.9 2
<https://docs.python.org/3.9/whatsnew/3.9.html>” document for more information
about features included in the 3.9 series. We also have a detailed change log
for 3.9.2rc1
<https://docs.python.org/release/3.9.2/whatsnew/changelog.html#python-3-9-2-release-candidate-1>
specifically. The final release only contains a single bugfix
<https://github.com/python/cpython/pull/24554> over the release candidate.

Detailed information about all changes made in version 3.8.8rc1 specifically
can be found in its respective changelog
<https://docs.python.org/release/3.8.8/whatsnew/changelog.html#python-3-8-8-release-candidate-1>.
The final version contains no changes over the release candidate.

We hope you enjoy those new releases!

[python-committers] [RELEASE] Python 3.9.2rc1 and 3.8.8rc1 are now available for testing

2021-02-17 Thread Łukasz Langa

I’m happy to announce two release candidates today: Python 3.9.2rc1, and Python 
3.8.8rc1. Get them from:

https://www.python.org/downloads/release/python-392rc1/ 
<https://www.python.org/downloads/release/python-392rc1/>

https://www.python.org/downloads/release/python-388rc1/ 
<https://www.python.org/downloads/release/python-388rc1/>

Unless critical issues are discovered, both release candidates will become 
their respective final versions on Monday, March 1st.
Following that, the last full regular maintenance release of Python 3.8 is 
planned for May 3rd 2021, after which it will shift to source releases only for 
security bug fixes only. Maintenance releases for the 3.9 series will continue 
at regular bi-monthly intervals, with 3.9.3 planned for early May 2021.

Notable security content in today’s releases

bpo-42967 <https://bugs.python.org/issue42967>: Fix web cache poisoning 
vulnerability by defaulting the query args separator to &, and allowing the 
user to choose a custom separator.

bpo-42938 <https://bugs.python.org/issue42938>: Avoid static buffers when 
computing the repr of ctypes.c_double and ctypes.c_longdouble values.

What’s new?

The Python 3.9 series contains many new features and optimizations over 3.8. 
See the “What’s New in Python 3.9 
<https://docs.python.org/3.9/whatsnew/3.9.html>” document for more information 
about features included in the 3.9 series. We also have a detailed change log 
for 3.9.2rc1 
<https://docs.python.org/release/3.9.2rc1/whatsnew/changelog.html#changelog> 
specifically.

Detailed information about all changes made in version 3.8.8rc1 specifically 
can be found in its change log 
<https://docs.python.org/release/3.8.8rc1/whatsnew/changelog.html#python-3-8-8-release-candidate-1>.

We hope you enjoy those new releases!

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.

Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/T4IZOGQB7DW4KNKJZBQ6U4VMYETK6EVR/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [HELP WANTED] Do you see yourself chairing the Python Language Summit at PyCon US next year? Come talk to us!

2021-01-11 Thread Łukasz Langa

Hi there,
Mariatta and I are about to kick off preparations for the Language Summit at
PyCon US this year. We've been doing this since 2019 and we feel like passing
the baton to new people in 2022. We don't want to start planning anything
before we have 2 people lined up to cover this post for 2022.

Interested? Get in touch with us before Jan 18th!

You can expect the following responsibilities if another remote Summit comes
along:
- write e-mails (invitations, talk acceptance and rejections, reminders);
- set up video conferencing tech;
- herd cats in terms of talk preparation;
- moderate the event while it's happening.

In-person Summits have different expectations:
- you don't have to do so much in terms of video conferencing; but
- you get to herd cats in real life in terms of talk slides; as well as
- organize the physical space, including making sure catering works for the
attendees.

In any case, you should not expect the Spanish inquisition. Joking aside, we
really hope to hear from you. This will make things much easier than the
"kidnap and blackmail" Plan B we outlined with Mariatta last week. You have no
idea how annoying international travel restrictions are these days.

Cheers,
Mariatta and Łukasz

PS. If you're a committer just wondering about the Language Summit: yes, it's
happening! It's going to be another Zoom-driven experience but hopefully we'll
get to see each other in real life next year! This year it will again be split
into two days: May 11th (Tuesday before the conference), and May 12th
(Wednesday before the conference). Four hours each, different times each to
make sure that the world of Python stays connected despite timezone challenges.
Invitations, forms, and everything are coming up but we want our new 2022
chairs to be able to shadow us during this process.

PS2. "Wait, what is the Language Summit?" Glad you asked! The Python Language
Summit is an event for the developers of Python implementations (CPython, PyPy,
Jython, and so on) to share information, discuss our shared problems, and —
hopefully — solve them. One of the goals of the Language Summit is to speed up
the discussions and decision making process as communication over Discourse and
mailing lists is generally more time consuming.___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/37I55NNZKXBADAFRYIBJ3SCOVURHKRFW/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.7 is now available

2020-12-21 Thread Łukasz Langa

Python 3.8.7 is the seventh maintenance release of Python 3.8. Go get it here:

https://www.python.org/downloads/release/python-387/
<https://www.python.org/downloads/release/python-387/>
Note: this is a bugfix release for the 3.8 series which was superseded by
Python 3.9, currently the latest feature release series of Python 3. You can
find the latest release of 3.9.x here <https://www.python.org/downloads/>.

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

macOS 11 Big Sur not fully supported

Python 3.8.7 is not yet fully supported on macOS 11 Big Sur. It will install on
macOS 11 Big Sur and will run on Apple Silicon Macs using Rosetta 2
translation. However, a few features do not work correctly, most noticeably
those involving searching for system libraries (vs user libraries) such as
ctypes.util.find_library() and in Distutils. This limitation affects both Apple
Silicon and Intel processors. We are looking into improving the situation for
Python 3.8.8.

Python 3.9.1 <https://www.python.org/downloads/release/python-391/> provides
full support for Big Sur and Apple Silicon Macs, including building natively on
Apple Silicon Macs and support for universal2 binaries.

What’s new?

The Python 3.8 series contains many new features and optimizations over 3.7.
See the “What’s New in Python 3.8
<https://docs.python.org/3.8/whatsnew/3.8.html>” document for more information
about features included in the 3.8 series.

Detailed information about all changes made in version 3.8.7 specifically can
be found in its change log
<https://docs.python.org/release/3.8.7/whatsnew/changelog.html#python-3-8-7>.
Note that compared to 3.8.6 this release also contains all changes present in
3.8.7rc1.

We hope you enjoy Python 3.8!

Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/MMLVSZLBWXUCX2UTBIEV7PTPVQA4BCZW/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.9.1rc1 is now ready for testing

2020-11-26 Thread Łukasz Langa

Python 3.9.1rc1 is the release candidate of the first maintenance release of
Python 3.9. Go get it here:
https://www.python.org/downloads/release/python-391rc1/
<https://www.python.org/downloads/release/python-391rc1/>
Assuming no critical problems are found prior to 2020-12-11, the currently
scheduled release date for 3.9.1, 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.9.1 and as such its main purpose is testing.

Maintenance releases for the 3.9 series will continue at regular bi-monthly
intervals, with 3.9.2 planned for end of January 2021.

Installer news

3.9.1rc1 is the first version of Python to support macOS 11 Big Sur. With Xcode
11 and later it is now possible to build “Universal 2” binaries which work on
Apple Silicon. We are providing such an installer as the macosx11.0 variant.
This installer can be deployed back to older versions, tested down to OS X
10.9. As we are waiting for an updated version of pip, please consider the
macosx11.0 installer experimental.

This work would not have been possible without the effort of Ronald Oussoren,
Ned Deily, and Lawrence D’Anna from Apple. Thank you!

In other news, this is the first version of Python to default to the 64-bit
installer on Windows. The installer now also actively disallows installation on
Windows 7. Python 3.9 is incompatible with this unsupported version of Windows.

What’s new in Python 3.9.1rc1?

We’ve made 240 changes since v3.9.0 which is a significant amount. To compare,
3.8.1rc1 only saw 168 commits since 3.8.0. See the full change log at

https://docs.python.org/release/3.9.1rc1/whatsnew/changelog.html
<https://docs.python.org/release/3.9.1rc1/whatsnew/changelog.html>.

For more information about features included in the 3.9 series, see the “What’s
New in Python 3.9 <https://docs.python.org/release/3.9.0/whatsnew/3.9.html>”
document.

What about Python 3.8.7rc1?

There’s additional work needed to make this release support macOS 11 Big Sur.
This should be ready next week, stay tuned.

We hope you enjoy the new releases!

https://www.python.org/psf/ <https://www.python.org/psf/>
More resources

Online Documentation <https://docs.python.org/3.9/>
PEP 596 <https://www.python.org/dev/peps/pep-0596/>, 3.9 Release Schedule
PEP 619 <https://www.python.org/dev/peps/pep-0619/>, 3.10 Release Schedule
Report bugs at https://bugs.python.org <https://bugs.python.org/>.
Help fund Python and its community <https://www.python.org/psf/donations/>.
Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/OD2JED7GACLTK7ETE2D27OGERKMWSCEV/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Travis CI is no longer mandatory on Python pull requests

2020-10-19 Thread Łukasz Langa


> On 19 Oct 2020, at 21:22, Ned Deily  wrote:
>>> Let's just disable Travis on all branches for now until there is reason to 
>>> believe the problems we've seen are fixed.
>> +1 from me.
> 
> Pablo, Łukasz: any objections to disabling Travis on your branches?  If not, 
> one of us, or Ernest, can just do it.

Absolutely, go ahead. In fact I see somebody already did. Good. Faster 
backports FTW.

- Ł___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/NSJHERYW4DOTPKSWOPX5OXNEDNAHHCXT/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Thank you Larry Hastings!

2020-10-05 Thread Łukasz Langa


> On 5 Oct 2020, at 20:38, Barry Warsaw  wrote:
> 
> Larry, from all of us, and from me personally, thank you so much for your 
> invaluable contributions to Python.

Yes, definitely! Thank you.


> Enjoy your retirement!

Not so fast! Now you have all that extra free time to return to the Gilectomy! 🤓

- Ł
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/T4OEUJWMSKXC4GJ5UY3ZECWFI5PYFWVP/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.9.0 is now available, and you can already test 3.10.0a1!

2020-10-05 Thread Łukasz Langa

On behalf of the Python development community and the Python 3.9 release team,
I’m pleased to announce the availability of Python 3.9.0.

Python 3.9.0 is the newest feature release of the Python language, and it
contains many new features and optimizations. You can find Python 3.9.0 here:

https://www.python.org/downloads/release/python-390/
<https://www.python.org/downloads/release/python-390/>

Most third-party distributors of Python should be making 3.9.0 packages
available soon.

See the “What’s New in Python 3.9
<https://docs.python.org/release/3.9.0/whatsnew/3.9.html>” document for more
information about features included in the 3.9 series. Detailed information
about all changes made in 3.9.0 can be found in its change log
<https://docs.python.org/release/3.9.0/whatsnew/changelog.html#changelog>.

Maintenance releases for the 3.9 series will follow at regular bi-monthly
intervals starting in late November of 2020.

OK, boring! Where is Python 4?

Not so fast! The next release after 3.9 will be 3.10. It will be an incremental
improvement over 3.9, just as 3.9 was over 3.8, and so on.

In fact, our newest Release Manager, Pablo Galindo Salgado, prepared the first
alpha release of what will become 3.10.0 a year from now. You can check it out
here:

https://www.python.org/downloads/release/python-3100a1/
<https://www.python.org/downloads/release/python-3100a1/>

We hope you enjoy the new releases!

https://www.python.org/psf/ <https://www.python.org/psf/>
More resources

Online Documentation <https://docs.python.org/3.9/>
PEP 596 <https://www.python.org/dev/peps/pep-0596/>, 3.9 Release Schedule
PEP 619 <https://www.python.org/dev/peps/pep-0619/>, 3.10 Release Schedule
Report bugs at https://bugs.python.org <https://bugs.python.org/>.
Help fund Python and its community <https://www.python.org/psf/donations/>.
Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Pablo Galindo Salgado @pablogsal <https://discuss.python.org/u/pablogsal>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/ZSQOHQYBEZV3DUZPDXCI4QWWZJI2KVXE/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.6 is now available

2020-09-24 Thread Łukasz Langa

Python 3.8.6 is the sixth maintenance release of Python 3.8. Go get it here:

https://www.python.org/downloads/release/python-386/
<https://www.python.org/downloads/release/python-386/>

Maintenance releases for the 3.8 series will continue at regular bi-monthly
intervals, with 3.8.7 planned for mid-November 2020.

What’s new?

The Python 3.8 series is the newest feature release of the Python language, and
it contains many new features and optimizations. See the “What’s New in Python
3.8 <https://docs.python.org/3.8/whatsnew/3.8.html>” document for more
information about features included in the 3.8 series.

Python 3.8 is becoming more stable. Our bugfix releases are becoming smaller as
we progress. This one contains 122 changes, less than two thirds of the
previous average for a new release. Detailed information about all changes made
in version 3.8.6 specifically can be found in its change log
<https://docs.python.org/release/3.8.6/whatsnew/changelog.html#python-3-8-6>.
Note that compared to 3.8.5 this release also contains all changes present in
3.8.6rc1.

We hope you enjoy Python 3.8!

Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/AOBUH5WPNZ2TKICKU6GYKJTAEI3VGAP6/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.9.0rc2 is now available for testing

2020-09-17 Thread Łukasz Langa

Python 3.9.0 is almost ready. This release, 3.9.0rc2, is the last planned 
preview before the final release of Python 3.9.0 on 2020-10-05. Get it here:

https://www.python.org/downloads/release/python-390rc2/ 
<https://www.python.org/downloads/release/python-390rc2/>
In the mean time, we strongly encourage maintainers of third-party Python 
projects to prepare their projects for 3.9 compatibility during this phase. As 
always, report any issues to the Python bug tracker <https://bugs.python.org/>.

Please keep in mind that this is a preview release and its use is not 
recommended for production environments.

Information for core developers

The 3.9 branch is now accepting changes for 3.9.1. To maximize stability, the 
final release will be cut from the v3.9.0rc2 tag. If you need the release 
manager to cherry-pick any critical fixes, mark issues as release blockers 
and/or add him as a reviewer on a critical backport PR on GitHub.

To see which changes are currently cherry-picked for inclusion in 3.9.0, look 
at the short-lived branch-v3.9.0 
<https://github.com/python/cpython/tree/branch-v3.9.0> on GitHub.

Installer news

This is the first version of Python to default to the 64-bit installer on 
Windows. The installer now also actively disallows installation on Windows 7. 
Python 3.9 is incompatible with this unsupported version of Windows.

Major new features of the 3.9 series, compared to 3.8

Some of the new major new features and changes in Python 3.9 are:

PEP 584 <https://www.python.org/dev/peps/pep-0584/>, Union Operators in dict
PEP 585 <https://www.python.org/dev/peps/pep-0585/>, Type Hinting Generics In 
Standard Collections
PEP 593 <https://www.python.org/dev/peps/pep-0593/>, Flexible function and 
variable annotations
PEP 602 <https://www.python.org/dev/peps/pep-0602/>, Python adopts a stable 
annual release cadence
PEP 615 <https://www.python.org/dev/peps/pep-0615/>, Support for the IANA Time 
Zone Database in the Standard Library
PEP 616 <https://www.python.org/dev/peps/pep-0616/>, String methods to remove 
prefixes and suffixes
PEP 617 <https://www.python.org/dev/peps/pep-0617/>, New PEG parser for CPython
BPO 38379 <https://bugs.python.org/issue38379>, garbage collection does not 
block on resurrected objects;
BPO 38692 <https://bugs.python.org/issue38692>, os.pidfd_open added that allows 
process management without races and signals;
BPO 39926 <https://bugs.python.org/issue39926>, Unicode support updated to 
version 13.0.0;
BPO 1635741 <https://bugs.python.org/issue1635741>, when Python is initialized 
multiple times in the same process, it does not leak memory anymore;
A number of Python builtins (range, tuple, set, frozenset, list, dict) are now 
sped up using PEP 590 <https://www.python.org/dev/peps/pep-0590> vectorcall;
A number of Python modules (_abc, audioop, _bz2, _codecs, _contextvars, _crypt, 
_functools, _json, _locale, operator, resource, time, _weakref) now use 
multiphase initialization as defined by PEP 489 
<https://www.python.org/dev/peps/pep-0489/>;
A number of standard library modules (audioop, ast, grp, _hashlib, pwd, 
_posixsubprocess, random, select, struct, termios, zlib) are now using the 
stable ABI defined by PEP 384 <https://www.python.org/dev/peps/pep-0384/>.
More resources

Online Documentation <https://docs.python.org/3.9/>
PEP 596 <https://www.python.org/dev/peps/pep-0596/>, 3.9 Release Schedule
Report bugs at https://bugs.python.org <https://bugs.python.org/>.
Help fund Python and its community <https://www.python.org/psf/donations/>.

Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/72MT4F4BXHZOVJB35LFW74GGIU74YGIW/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.6rc1 is now ready for testing

2020-09-08 Thread Łukasz Langa

Python 3.8.6rc1 is the release candidate of the sixth maintenance release of
Python 3.8. Go get it here:

https://www.python.org/downloads/release/python-386rc1/
<https://www.python.org/downloads/release/python-386rc1/>

Assuming no critical problems are found prior to 2020-09-21, the scheduled
release date for 3.8.6, 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 and as such its
main purpose is testing.

Maintenance releases for the 3.8 series will continue at regular bi-monthly
intervals, with 3.8.7 planned for mid-November 2020.

What’s new?

Python 3.8 is becoming more stable. Our bugfix releases are becoming smaller as
we progress. This one contains 80 changes, not even a half of what we got in
3.8.4 (the following release was a hotfix). Detailed information about all
changes made in version 3.8.6 specifically can be found in its change log
<https://docs.python.org/release/3.8.6rc1/whatsnew/changelog.html#python-3-8-6-release-candidate-1>.

We hope you enjoy Python 3.8!

Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/WCMNX3JKHZVOUA2NET2NRWCU6K6OJXNY/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.9.0rc1 is now available

2020-08-11 Thread Łukasz Langa

Python 3.9.0 is *almost* ready. This release, *3.9.0rc1*, is the penultimate 
release preview. You can get it here:

https://www.python.org/downloads/release/python-390rc1/
Entering the release candidate phase, only reviewed code changes which are 
clear bug fixes are allowed between this release candidate and the final 
release. The second candidate and the last planned release preview is currently 
planned for 2020-09-14.

Please keep in mind that this is a preview release and its use is *not* 
recommended for production environments.

Calls to action

Core developers: all eyes on the docs now

 * Are all *your* changes properly documented?
 * Did you notice *other* changes you know of to have insufficient 
documentation?
Community members

We *strongly encourage* maintainers of third-party Python projects to prepare 
their projects for 3.9 compatibility during this phase. As always, report any 
issues to the Python bug tracker .

Installer news

This is the first version of Python to default to the 64-bit installer on 
Windows. The installer now also actively disallows installation on Windows 7. 
Python 3.9 is incompatible with this unsupported version of Windows.

Major new features of the 3.9 series, compared to 3.8

Some of the new major new features and changes in Python 3.9 are:

 * PEP 584 , Union Operators in  
`dict`
 * PEP 585 , Type Hinting Generics 
In Standard Collections
 * PEP 593 , Flexible function and 
variable annotations
 * PEP 602 , Python adopts a stable 
annual release cadence
 * PEP 615 , Support for the IANA 
Time Zone Database in the Standard Library
 * PEP 616 , String methods to 
remove prefixes and suffixes
 * PEP 617 , New PEG parser for 
CPython
 * BPO 38379 , garbage collection does not 
block on resurrected objects;
 * BPO 38692 , os.pidfd_open added that 
allows process management without races and signals;
 * BPO 39926 , Unicode support updated to 
version 13.0.0;
 * BPO 1635741 , when Python is 
initialized multiple times in the same process, it does not leak memory anymore;
 * A number of Python builtins (range, tuple, set, frozenset, list, dict) are 
now sped up using PEP 590  vectorcall;
 * A number of Python modules (_abc, audioop, _bz2, _codecs, _contextvars, 
_crypt, _functools, _json, _locale, operator, resource, time, _weakref) now use 
multiphase initialization as defined by PEP 489 
;
 * A number of standard library modules (audioop, ast, grp, _hashlib, pwd, 
_posixsubprocess, random, select, struct, termios, zlib) are now using the 
stable ABI defined by PEP 384 .
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/FFVG5DAE7RHE5ZYUVVJW5TPAZ2ALRFHB/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Reminder: this coming Monday, Aug 10 is the planned date for Python 3.9.0rc1

2020-08-10 Thread Łukasz Langa

Update: I’m receiving my laptop back tomorrow (Tuesday), so I decided to push 
the release of 3.9.0rc1 to then as it will be much easier for me to make 
properly.

- Ł


> On 7 Aug 2020, at 11:30, Łukasz Langa  wrote:
> 
> Entering the release candidate phase is an exciting and necessary step 
> towards releasing a production-grade 3.9.0.
> 
> At this stage stability is of utmost importance. That's why the development 
> process described in our Dev Guide specifies that "a branch preparing for an 
> RC release can only have bugfixes applied that have been reviewed by other 
> core developers". See more at 
> https://devguide.python.org/devcycle/#release-candidate-rc
> 
> Note that due to the new PEP 602-compliant release calendar we are planning 
> to have two release candidates: the first this coming Monday, August 10th, 
> and the second on September 14th. As a reminder: expanding the RC phase was 
> done to help operating system distributors include the latest release of 
> Python in their own Autumn releases. To make it work, we need approach the 
> release candidates with as much care as we will put into 3.9.0 itself.
> 
> Lastly, and this is a little embarrassing to admit, my laptop is being 
> serviced by Apple at the moment due to a swollen battery. I'm ready to make 
> the release without it should it not return by Monday. However, in case it 
> turns out to be impossible, I'll let you know in a separate e-mail.
> 
> -- 
> Best regards,
> Łukasz Langa
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/6WSEQZKFTDFDIPYJNAUMOSVQUTW7MZJK/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Reminder: this coming Monday, Aug 10 is the planned date for Python 3.9.0rc1

2020-08-07 Thread Łukasz Langa

Entering the release candidate phase is an exciting and necessary step towards 
releasing a production-grade 3.9.0.

At this stage stability is of utmost importance. That's why the development 
process described in our Dev Guide specifies that "a branch preparing for an RC 
release can only have bugfixes applied that have been reviewed by other core 
developers". See more at 
https://devguide.python.org/devcycle/#release-candidate-rc

Note that due to the new PEP 602-compliant release calendar we are planning to 
have two release candidates: the first this coming Monday, August 10th, and the 
second on September 14th. As a reminder: expanding the RC phase was done to 
help operating system distributors include the latest release of Python in 
their own Autumn releases. To make it work, we need approach the release 
candidates with as much care as we will put into 3.9.0 itself.

Lastly, and this is a little embarrassing to admit, my laptop is being serviced 
by Apple at the moment due to a swollen battery. I'm ready to make the release 
without it should it not return by Monday. However, in case it turns out to be 
impossible, I'll let you know in a separate e-mail.

-- 
Best regards,
Łukasz Langa___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/ES2ZJ7GUSTZMJLP3UORQHQEWWHZRDP7H/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.5 released as a security hotfix. 3.9.0b5, the last beta before 3.9.0, also available

2020-07-20 Thread Łukasz Langa

n modules (_abc, audioop, _bz2, _codecs, _contextvars, _crypt, 
_functools, _json, _locale, operator, resource, time, _weakref) now use 
multiphase initialization as defined by PEP 489 
<https://www.python.org/dev/peps/pep-0489/>;

A number of standard library modules (audioop, ast, grp, _hashlib, pwd, 
_posixsubprocess, random, select, struct, termios, zlib) are now using the 
stable ABI defined by PEP 384 <https://www.python.org/dev/peps/pep-0384/>.

(Hey, fellow core developer, if a feature you find important is missing from 
this list, let Łukasz know <mailto:luk...@python.org>.)

We hope you enjoy the new releases!

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.

Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/GOOPZAAPCJT55CN5UOEMKKAKEGDQCOZN/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Planning a hotfix Python 3.8.5

2020-07-16 Thread Łukasz Langa

Good call, Matthias. We will include it as long as it's merged before Monday 
8am CEST.

- Ł



> On 16 Jul 2020, at 20:00, Matthias Klose  wrote:
> 
> On 7/16/20 7:36 PM, Łukasz Langa wrote:
>> Hey team,
>> there are 3 security-related fixes in the 3.8 branch post 3.8.4, one with a 
>> CVE, another with a pending CVE if I understood Steve correctly. I'd like to 
>> release a hotfix 3.8.5 on Monday.
>> 
>> Since this is a special security-focused release, it will be essentially 
>> 3.8.4 + those three changes cherry-picked. That gives us enough confidence 
>> about the release that we can skip a release candidate for it.
>> 
>> If you have any other security-related changes you think belong in 3.8, 
>> please merge them before Monday 8am CEST.
> 
> what about https://bugs.python.org/issue41295 ?
> 
> This is marked as a regression compared to 3.8.3.
> 
> Matthias
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/62YEVIS7DNAC2H2MUWAOBPFMJIOJCUYD/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Planning a hotfix Python 3.8.5

2020-07-16 Thread Łukasz Langa

Hey team,
there are 3 security-related fixes in the 3.8 branch post 3.8.4, one with a 
CVE, another with a pending CVE if I understood Steve correctly. I'd like to 
release a hotfix 3.8.5 on Monday.

Since this is a special security-focused release, it will be essentially 3.8.4 
+ those three changes cherry-picked. That gives us enough confidence about the 
release that we can skip a release candidate for it.

If you have any other security-related changes you think belong in 3.8, please 
merge them before Monday 8am CEST.


Cheers,
Ł
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/YFSIH37DA3LQFIENE6MBNSGKJJ62EXEP/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.4 is now available

2020-07-13 Thread Łukasz Langa

Python 3.8.4 is the fourth maintenance release of Python 3.8. Go get it here:

https://www.python.org/downloads/release/python-384/
<https://www.python.org/downloads/release/python-384/>
Maintenance releases for the 3.8 series will continue at regular bi-monthly
intervals, with 3.8.5 planned for mid-September 2020.

What’s new?

This is the first bugfix release that is considerably smaller than the previous
three. There’s almost 20% fewer changes at 162 commits than the average of
previous three bugfix releases. Detailed information about all changes made in
version 3.8.4 specifically can be found in its change log
<https://docs.python.org/release/3.8.4/whatsnew/changelog.html#python-3-8-4-final>.
Note that compared to 3.8.3, version 3.8.4 also contains the changes
introduced in 3.8.4rc1.

We hope you enjoy Python 3.8!

Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/JV6BY6UJTMRGS5WL2VH3ZNPCVESZAINZ/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Please avoid non-bugfix changes during the beta phase

2020-07-06 Thread Łukasz Langa

Hi there,
here's a reminder: 
https://discuss.python.org/t/please-avoid-non-bugfix-changes-during-the-beta-phase/4665

- Ł
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/LU7L5JQ6LD4X56QR2MI674E7XFJCKUGI/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.9.0b4 is now ready for testing

2020-07-03 Thread Łukasz Langa

On behalf of the entire Python development community, and the currently serving 
Python release team in particular, I’m pleased to announce the release of 
Python 3.9.0b4. Get it here:

https://www.python.org/downloads/release/python-390b4/ 
<https://www.python.org/downloads/release/python-390b4/>

This is a beta preview of Python 3.9

Python 3.9 is still in development. This release, 3.9.0b4, is the fourth of 
five planned beta release previews.

Beta release previews are intended to give the wider community the opportunity 
to test new features and bug fixes and to prepare their projects to support the 
new feature release.

Call to action

We strongly encourage maintainers of third-party Python projects to test with 
3.9 during the beta phase and report issues found to the Python bug tracker 
<https://bugs.python.org/> as soon as possible. While the release is planned to 
be feature complete entering the beta phase, it is possible that features may 
be modified or, in rare cases, deleted up until the start of the release 
candidate phase (2020-08-10). Our goal is have no ABI changes after beta 5 and 
as few code changes as possible after 3.9.0rc1, the first release candidate. To 
achieve that, it will be extremely important to get as much exposure for 3.9 as 
possible during the beta phase.

Please keep in mind that this is a preview release and its use is not 
recommended for production environments.

Major new features of the 3.9 series, compared to 3.8

Some of the new major new features and changes in Python 3.9 are:

PEP 584 <https://www.python.org/dev/peps/pep-0584/>, Union Operators in dict

PEP 585 <https://www.python.org/dev/peps/pep-0585/>, Type Hinting Generics In 
Standard Collections

PEP 593 <https://www.python.org/dev/peps/pep-0593/>, Flexible function and 
variable annotations

PEP 602 <https://www.python.org/dev/peps/pep-0602/>, Python adopts a stable 
annual release cadence

PEP 615 <https://www.python.org/dev/peps/pep-0615/>, Support for the IANA Time 
Zone Database in the Standard Library

PEP 616 <https://www.python.org/dev/peps/pep-0616/>, String methods to remove 
prefixes and suffixes

PEP 617 <https://www.python.org/dev/peps/pep-0617/>, New PEG parser for CPython

BPO 38379 <https://bugs.python.org/issue38379>, garbage collection does not 
block on resurrected objects;

BPO 38692 <https://bugs.python.org/issue38692>, os.pidfd_open added that allows 
process management without races and signals;

BPO 39926 <https://bugs.python.org/issue39926>, Unicode support updated to 
version 13.0.0;

BPO 1635741 <https://bugs.python.org/issue1635741>, when Python is initialized 
multiple times in the same process, it does not leak memory anymore;

A number of Python builtins (range, tuple, set, frozenset, list, dict) are now 
sped up using PEP 590 <https://www.python.org/dev/peps/pep-0590> vectorcall;

A number of Python modules (_abc, audioop, _bz2, _codecs, _contextvars, _crypt, 
_functools, _json, _locale, operator, resource, time, _weakref) now use 
multiphase initialization as defined by PEP 489 
<https://www.python.org/dev/peps/pep-0489/>;

A number of standard library modules (audioop, ast, grp, _hashlib, pwd, 
_posixsubprocess, random, select, struct, termios, zlib) are now using the 
stable ABI defined by PEP 384 <https://www.python.org/dev/peps/pep-0384/>.

(Hey, fellow core developer, if a feature you find important is missing from 
this list, let Łukasz know <mailto:luk...@python.org>.)

The next pre-release, the fifth beta release of Python 3.9, will be 3.9.0b5. It 
is currently scheduled for 2020-07-20.

More resources

Online Documentation <https://docs.python.org/3.9/>
PEP 596 <https://www.python.org/dev/peps/pep-0596/>, 3.9 Release Schedule
Report bugs at https://bugs.python.org <https://bugs.python.org/>.
Help fund Python and its community <https://discuss.python.org/psf/donations/>.
Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/2YXZ35N5IIHC2VXQ3IIFJOX2B32ZJASP/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Please welcome Lysandros Nikolaou to the team!

2020-06-30 Thread Łukasz Langa

Welcome, Lysandros! Happy to see you here.

- Ł

> On 30 Jun 2020, at 21:21, Brett Cannon  wrote:
> 
> 
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at 
> https://mail.python.org/archives/list/python-committers@python.org/message/OQPA633CV5TA44BBYFBMU3CI4WRT4AVC/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/O53DYUPYMJVNRJI6R5DDXE64BBRBTZDB/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.4rc1 is now ready for testing

2020-06-30 Thread Łukasz Langa

Python 3.8.4rc1 is the release candidate of the fourth maintenance release of 
Python 3.8. Go get it here:
https://www.python.org/downloads/release/python-384rc1/ 
<https://www.python.org/downloads/release/python-384rc1/>
Assuming no critical problems are found prior to 2020-07-13, the scheduled 
release date for 3.8.4, 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 and as such its 
main purpose is testing.

Maintenance releases for the 3.8 series will continue at regular bi-monthly 
intervals, with 3.8.5 planned for mid-September 2020.

What’s new?

The Python 3.8 series is the newest feature release of the Python language, and 
it contains many new features and optimizations. See the “What’s New in Python 
3.8 <https://docs.python.org/3.8/whatsnew/3.8.html>” document for more 
information about features included in the 3.8 series.

This is the first bugfix release that is considerably smaller than the previous 
three. There’s 20% less changes at 130 commits than the average of previous 
three releases. Detailed information about all changes made in version 3.8.4 
specifically can be found in its change log 
<https://docs.python.org/release/3.8.4rc1/whatsnew/changelog.html#python-3-8-4-release-candidate-1>.

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.

Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/VVK3CFZJOB54KKL2QUKCLWSFNSM6BRDV/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.9.0b3 is now available for testing

2020-06-09 Thread Łukasz Langa

On behalf of the entire Python development community, and the currently serving 
Python release team in particular, I’m pleased to announce the release of 
Python 3.9.0b3. Get it here:

https://www.python.org/downloads/release/python-390b3/ 
<https://www.python.org/downloads/release/python-390b3/>
Wait, Beta 3? What happened to Beta 2?

Beta 2? Speak of him no more. We disappeared him. He was a bad release. Truly 
awful. I get shivers just thinking about it. Never mention that name again in 
this house.

I mean, long story short, in Beta 2 you couldn’t do 
urllib.request.urlopen("https://www.python.org";).read() because it wouldn’t 
find root certificates due to a bug <https://bugs.python.org/issue40924>. Since 
this was a problem only apparent on an installed Python, it wasn’t identified 
by unit tests and was only found by Ned while he was testing his Mac installer. 
By the time we learned of the severity of the bug I already tagged and 
published the release on python.org <http://python.org/>. That’s why we 
couldn’t just re-do the release under the same version.

Sorry for the trouble. We’re tweaking our release process to catch this problem 
sooner in future releases. Now, back to regular programming…

This is a beta preview of Python 3.9

Python 3.9 is still in development. This release, 3.9.0b3, is the third of five 
planned beta release previews.

Beta release previews are intended to give the wider community the opportunity 
to test new features and bug fixes and to prepare their projects to support the 
new feature release.

Call to action

We strongly encourage maintainers of third-party Python projects to test with 
3.9 during the beta phase and report issues found to the Python bug tracker 
<https://bugs.python.org/> as soon as possible. While the release is planned to 
be feature complete entering the beta phase, it is possible that features may 
be modified or, in rare cases, deleted up until the start of the release 
candidate phase (2020-08-10). Our goal is have no ABI changes after beta 5 and 
as few code changes as possible after 3.9.0rc1, the first release candidate. To 
achieve that, it will be extremely important to get as much exposure for 3.9 as 
possible during the beta phase.

Please keep in mind that this is a preview release and its use is not 
recommended for production environments.

Major new features of the 3.9 series, compared to 3.8

Some of the new major new features and changes in Python 3.9 are:

PEP 584 <https://www.python.org/dev/peps/pep-0584/>, Union Operators in dict

PEP 585 <https://www.python.org/dev/peps/pep-0585/>, Type Hinting Generics In 
Standard Collections

PEP 593 <https://www.python.org/dev/peps/pep-0593/>, Flexible function and 
variable annotations

PEP 602 <https://www.python.org/dev/peps/pep-0602/>, Python adopts a stable 
annual release cadence

PEP 616 <https://www.python.org/dev/peps/pep-0616/>, String methods to remove 
prefixes and suffixes

PEP 617 <https://www.python.org/dev/peps/pep-0617/>, New PEG parser for CPython

BPO 38379 <https://bugs.python.org/issue38379>, garbage collection does not 
block on resurrected objects;

BPO 38692 <https://bugs.python.org/issue38692>, os.pidfd_open added that allows 
process management without races and signals;

BPO 39926 <https://bugs.python.org/issue39926>, Unicode support updated to 
version 13.0.0;

BPO 1635741 <https://bugs.python.org/issue1635741>, when Python is initialized 
multiple times in the same process, it does not leak memory anymore;

A number of Python builtins (range, tuple, set, frozenset, list, dict) are now 
sped up using PEP 590 <https://www.python.org/dev/peps/pep-0590> vectorcall;

A number of Python modules (_abc, audioop, _bz2, _codecs, _contextvars, _crypt, 
_functools, _json, _locale, operator, resource, time, _weakref) now use 
multiphase initialization as defined by PEP 489 
<https://www.python.org/dev/peps/pep-0489/>;

A number of standard library modules (audioop, ast, grp, _hashlib, pwd, 
_posixsubprocess, random, select, struct, termios, zlib) are now using the 
stable ABI defined by PEP 384 <https://www.python.org/dev/peps/pep-0384/>.

(Hey, fellow core developer, if a feature you find important is missing from 
this list, let Łukasz know <mailto:luk...@python.org>.)

The next pre-release, the fourth beta release of Python 3.9, will be 3.9.0b4. 
It is currently scheduled for 2020-06-29.

More resources

Online Documentation <https://docs.python.org/3.9/>
PEP 596 <https://www.python.org/dev/peps/pep-0596/>, 3.9 Release Schedule
Report bugs at https://bugs.python.org <https://bugs.python.org/>.
Help fund Python and its community <https://discuss.python.org/psf/donations/>.
Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>

[python-committers] Re: Please welcome our next Release Manager, Pablo!

2020-05-19 Thread Łukasz Langa

I'm very happy about this!

Pablo is a natural candidate for the role. As one of the people caring for our 
buildbots, he helped me during releases many times. And this past 3.9.0b1, 
while I was working on the new 3.9 maintenance branch, he made the master 
branch successfully build a Python with a double-digit minor version number. 
Strong start!

Welcome!

PS. Thank you for the kind words, Barry, it will take some more releases for me 
to make before I retire: eyes fixed on 3.9.0 in particular. Exciting times! :-)

-- 
Best regards,
Łukasz Langa

> On 20 May 2020, at 00:54, Barry Warsaw  wrote:
> 
> In light of the release of Python 3.9b1, let’s take a moment to celebrate 
> all the great work that our Python 3.8 and 3.9 release manager Łukasz has 
> done.  The role of Python Release Manager is hugely important to each 
> successful release, and it can be a lot of work, often unseen and thankless 
> to shepherd a new Python version through its first alpha release to its last 
> security release.  With all of your immeasurable help, the Release Manager 
> ensures solid, feature-full releases that the entire Python community eagerly 
> awaits.
> 
> Łukasz carries on the fine tradition of all of our past release managers, and 
> now that his second release has entered beta phase, I’m very happy to 
> announce our next Release Manager, for Python 3.10 and 3.11: Pablo Galindo 
> Salgado!
> 
> Since becoming a core developer in 2018, Pablo has contributed significantly 
> to Python.  With the change to an annual release cycle (PEP 602, authored by 
> Łukasz), the time commitment for release managers has been reduced as well, 
> and we will continue to look for ways to make the selection process for 
> release managers more transparent and accessible.  I know that in addition to 
> admirably managing the releases for 3.10 and 3.11, Pablo will also help to 
> continually improve the process of selecting and serving as release manager.
> 
> Please join me in welcoming Pablo in his new role!
> 
> Cheers,
> -Barry
> 
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at 
> https://mail.python.org/archives/list/python-committers@python.org/message/44TLJO5YX6XYM4ICWSHMBMCKPBBQQP5S/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/EBUGAIJWJ6DVL2IYHBJQSQGVIK2TV6SD/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Heads up: the master branch now points to Python 3.10

2020-05-19 Thread Łukasz Langa

Along with the release of Python 3.9.0b1, a 3.9 maintenance branch was created 
and the master branch now holds work that will become Python 3.10a1 at some 
point. This change was made here: https://github.com/python/cpython/pull/20198 


Note that this means you have to have your bugfix pull requests backported to 
3.9 using the newly created GitHub label. If you don't do this, they will only 
be available in Python 3.10.

Note I wrote bugfix pull requests. We entered the beta phase and new features 
will have to wait until next year's release.

Creating a new maintenance branch is the most manual piece of the release 
process we have. If you notice any place where Python 3.10 is missing in a 
list, or that suggests that master is still Python 3.9, let me know and we'll 
handle it. Thank you to Victor Stinner who proactively found a bunch of those 
things very quickly. (Julien is taking care of the JS version pickers in the 
docs.)

Cheers!


- Ł___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/HFDJGJJG7QV26CTLXX7KLVZIGFH6JEIS/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.9.0b1 is now available for testing

2020-05-19 Thread Łukasz Langa

On behalf of the entire Python development community, and the currently serving 
Python release team in particular, I’m pleased to announce the release of 
Python 3.9.0b1. Get it here:

https://www.python.org/downloads/release/python-390b1/ 
<https://www.python.org/downloads/release/python-390b1/>

This is a beta preview of Python 3.9

Python 3.9 is still in development. This release, 3.9.0b1, is the first of four 
planned beta release previews.

Beta release previews are intended to give the wider community the opportunity 
to test new features and bug fixes and to prepare their projects to support the 
new feature release.

Call to action

We strongly encourage maintainers of third-party Python projects to test with 
3.9 during the beta phase and report issues found to the Python bug tracker 
<https://bugs.python.org/> as soon as possible. While the release is planned to 
be feature complete entering the beta phase, it is possible that features may 
be modified or, in rare cases, deleted up until the start of the release 
candidate phase (2020-08-10). Our goal is have no ABI changes after beta 4 and 
as few code changes as possible after 3.9.0rc1, the first release candidate. To 
achieve that, it will be extremely important to get as much exposure for 3.9 as 
possible during the beta phase.

Please keep in mind that this is a preview release and its use is not 
recommended for production environments.

Major new features of the 3.9 series, compared to 3.8

Some of the new major new features and changes in Python 3.9 are:

PEP 584 <https://www.python.org/dev/peps/pep-0584/>, Union Operators in dict

PEP 585 <https://www.python.org/dev/peps/pep-0585/>, Type Hinting Generics In 
Standard Collections

PEP 593 <https://www.python.org/dev/peps/pep-0593/>, Flexible function and 
variable annotations

PEP 602 <https://www.python.org/dev/peps/pep-0602/>, Python adopts a stable 
annual release cadence

PEP 616 <https://www.python.org/dev/peps/pep-0616/>, String methods to remove 
prefixes and suffixes

PEP 617 <https://www.python.org/dev/peps/pep-0617/>, New PEG parser for CPython

BPO 38379 <https://bugs.python.org/issue38379>, garbage collection does not 
block on resurrected objects;

BPO 38692 <https://bugs.python.org/issue38692>, os.pidfd_open added that allows 
process management without races and signals;

BPO 39926 <https://bugs.python.org/issue39926>, Unicode support updated to 
version 13.0.0;

BPO 1635741 <https://bugs.python.org/issue1635741>, when Python is initialized 
multiple times in the same process, it does not leak memory anymore;

A number of Python builtins (range, tuple, set, frozenset, list, dict) are now 
sped up using PEP 590 <https://www.python.org/dev/peps/pep-0590> vectorcall;

A number of Python modules (_abc, audioop, _bz2, _codecs, _contextvars, _crypt, 
_functools, _json, _locale, operator, resource, time, _weakref) now use 
multiphase initialization as defined by PEP 489 
<https://www.python.org/dev/peps/pep-0489/>;

A number of standard library modules (audioop, ast, grp, _hashlib, pwd, 
_posixsubprocess, random, select, struct, termios, zlib) are now using the 
stable ABI defined by PEP 384 <https://www.python.org/dev/peps/pep-0384/>.

(Hey, fellow core developer, if a feature you find important is missing from 
this list, let Łukasz know <mailto:luk...@python.org>.)

The next pre-release, the second beta release of Python 3.9, will be 3.9.0b2. 
It is currently scheduled for 2020-06-08.

More resources

Online Documentation <https://docs.python.org/3.9/>
PEP 596 <https://www.python.org/dev/peps/pep-0596/>, 3.9 Release Schedule
Report bugs at https://bugs.python.org <https://bugs.python.org/>.
Help fund Python and its community <https://discuss.python.org/psf/donations/>.
Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/LQGV4LVIQEOM2HRPSAFXBJKDTEBZ2Z5R/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: All hands on deck: the release of Python 3.9.0b1 is currently blocked

2020-05-18 Thread Łukasz Langa

Looks like everything is handled in one way or another. We can start work on 
releasing beta 1!

- Ł


> On 18 May 2020, at 17:25, Łukasz Langa  wrote:
> 
> Hi there fellow core developers,
> the beta 1 release of Python 3.9.0 planned for today is as of now blocked on 
> three issues marked as "release blocker":
> 
> - https://bugs.python.org/issue26317 <https://bugs.python.org/issue26317>
> - https://bugs.python.org/issue40661 <https://bugs.python.org/issue40661>
> - https://bugs.python.org/issue40257 <https://bugs.python.org/issue40257>
> 
> If you can help addressing those ASAP, please do. We need to tag beta1 this 
> week to help getting the new release on time for inclusion in Linux 
> distributions.
> 
> - Ł
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at 
> https://mail.python.org/archives/list/python-committers@python.org/message/EPIKAUNJTSLOF4QWOJGANCQVBFO4ZIAZ/
> Code of Conduct: https://www.python.org/psf/codeofconduct/

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

[python-committers] All hands on deck: the release of Python 3.9.0b1 is currently blocked

2020-05-18 Thread Łukasz Langa

Hi there fellow core developers,
the beta 1 release of Python 3.9.0 planned for today is as of now blocked on 
three issues marked as "release blocker":

- https://bugs.python.org/issue26317 
- https://bugs.python.org/issue40661 
- https://bugs.python.org/issue40257 

If you can help addressing those ASAP, please do. We need to tag beta1 this 
week to help getting the new release on time for inclusion in Linux 
distributions.

- Ł___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/EPIKAUNJTSLOF4QWOJGANCQVBFO4ZIAZ/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.3 is now available

2020-05-14 Thread Łukasz Langa

On behalf of the entire Python development community, and the currently serving 
Python release team in particular, I’m pleased to announce the release of 
Python 3.8.3, the third maintenance release of Python 3.8. You can find it here:

https://www.python.org/downloads/release/python-383/ 
<https://www.python.org/downloads/release/python-383/>

It contains two months worth of bug fixes. Detailed information about all 
changes made in 3.8.3 can be found in its change log 
<https://docs.python.org/release/3.8.3/whatsnew/changelog.html#python-3-8-3-final>.
 Note that compared to 3.8.2, version 3.8.3 also contains the changes 
introduced in 3.8.3rc1.

The Python 3.8 series is the newest feature release of the Python language, and 
it contains many new features and optimizations. See the “What’s New in Python 
3.8 <https://docs.python.org/3.8/whatsnew/3.8.html>” document for more 
information about features included in the 3.8 series.

Maintenance releases for the 3.8 series will continue at regular bi-monthly 
intervals, with 3.8.4 planned for mid-July 2020.
One more thing

Unless blocked on any critical issue, Monday May 18th will be the release date 
of Python 3.9.0 beta 1. It’s a special release for us because this is when we 
lock the feature set for Python 3.9. If you can help testing the current 
available alpha release, that would be very helpful:

https://www.python.org/downloads/release/python-390a6/ 
<https://www.python.org/downloads/release/python-390a6/>
We hope you enjoy the new Python release!

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/ <https://www.python.org/psf/>


Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/6HMMY7U7X6ZDNGNSITN5IQZNEV6ND2F6/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.3rc1 is now ready for testing

2020-04-29 Thread Łukasz Langa

Python 3.8.3rc1 is the release candidate of the third maintenance release of 
Python 3.8. Go get it here:

https://www.python.org/downloads/release/python-383rc1/ 
<https://www.python.org/downloads/release/python-383rc1/> 

Assuming no critical problems are found prior to 2020-05-11, the scheduled 
release date for 3.8.3, 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 and as such its 
main purpose is testing.

Maintenance releases for the 3.8 series will continue at regular bi-monthly 
intervals, with 3.8.4 planned for mid-July 2020.

What’s new?

The Python 3.8 series is the newest feature release of the Python language, and 
it contains many new features and optimizations. See the “What’s New in Python 
3.8  <https://docs.python.org/3.8/whatsnew/3.8.html>” document for more 
information about features included in the 3.8 series.

Detailed information about all changes made in version 3.8.3 specifically can 
be found in its change log 
<https://docs.python.org/release/3.8.3rc1/whatsnew/changelog.html#python-3-8-3-release-candidate-1>.

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.

Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/XGZBXYQAJFZOLYJPJ7UOLK3O4GZNQDSF/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.9.0a6 is now available for testing

2020-04-28 Thread Łukasz Langa

On behalf of the entire Python development community, and the currently serving 
Python release team in particular, I’m pleased to announce the release of 
Python 3.9.0a6. Get it here:

https://www.python.org/downloads/release/python-390a6/ 
<https://www.python.org/downloads/release/python-390a6/>
This is an early developer preview of Python 3.9

Python 3.9 is still in development. This release, 3.9.0a6, is the last out of 
six planned alpha releases. Alpha releases are intended to make it easier to 
test the current state of new features and bug fixes and to test the release 
process. During the alpha phase, features may be added up until the start of 
the beta phase (2020-05-18) and, if necessary, may be modified or deleted up 
until the release candidate phase (2020-08-10). Please keep in mind that this 
is a preview release and its use is not recommended for production environments.

Major new features of the 3.9 series, compared to 3.8

Many new features for Python 3.9 are still being planned and written. Among the 
new major new features and changes so far:

PEP 584 <https://www.python.org/dev/peps/pep-0584/>, Union Operators in dict
PEP 585 <https://www.python.org/dev/peps/pep-0585/>, Type Hinting Generics In 
Standard Collections
PEP 593 <https://www.python.org/dev/peps/pep-0593/>, Flexible function and 
variable annotations
PEP 602 <https://www.python.org/dev/peps/pep-0602/>, Python adopts a stable 
annual release cadence
PEP 616 <https://www.python.org/dev/peps/pep-0616/>, String methods to remove 
prefixes and suffixes
PEP 617 <https://www.python.org/dev/peps/pep-0617/>, New PEG parser for CPython
BPO 38379 <https://bugs.python.org/issue38379>, garbage collection does not 
block on resurrected objects;
BPO 38692 <https://bugs.python.org/issue38692>, os.pidfd_open added that allows 
process management without races and signals;
BPO 39926 <https://bugs.python.org/issue39926>, Unicode support updated to 
version 13.0.0
BPO 1635741 <https://bugs.python.org/issue1635741>, when Python is initialized 
multiple times in the same process, it does not leak memory anymore
A number of Python builtins (range, tuple, set, frozenset, list) are now sped 
up using PEP 590 <https://www.python.org/dev/peps/pep-0590> vectorcall
A number of standard library modules (audioop, ast, grp, _hashlib, pwd, 
_posixsubprocess, random, select, struct, termios, zlib) are now using the 
stable ABI defined by PEP 384 <https://www.python.org/dev/peps/pep-0384/>.
(Hey, fellow core developer, if a feature you find important is missing from 
this list, let Łukasz know <mailto:luk...@python.org>.)
The next pre-release, the first beta release of Python 3.9, will be 3.9.0b1. It 
is currently scheduled for 2020-05-18.

Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/JJWIXYICQHCEFCJCCXVSWTP5O67UVCQC/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.9.0a5 is now available for testing

2020-03-23 Thread Łukasz Langa

On behalf of the entire Python development community, and the currently serving 
Python release team in particular, I’m pleased to announce the release of 
Python 3.9.0a5. Get it here:

https://www.python.org/downloads/release/python-390a5/ 
<https://www.python.org/downloads/release/python-390a5/>

This is an early developer preview of Python 3.9

Python 3.9 is still in development. This releasee, 3.9.0a5 is the fifth of six 
planned alpha releases. Alpha releases are intended to make it easier to test 
the current state of new features and bug fixes and to test the release 
process. During the alpha phase, features may be added up until the start of 
the beta phase (2020-05-18) and, if necessary, may be modified or deleted up 
until the release candidate phase (2020-08-10). Please keep in mind that this 
is a preview release and its use is not recommended for production environments.

Major new features of the 3.9 series, compared to 3.8

Many new features for Python 3.9 are still being planned and written. Among the 
new major new features and changes so far:

PEP 584 <https://www.python.org/dev/peps/pep-0584/>, Union Operators in dict
PEP 593 <https://www.python.org/dev/peps/pep-0593/>, Flexible function and 
variable annotations
PEP 602 <https://www.python.org/dev/peps/pep-0602/>, Python adopts a stable 
annual release cadence
BPO 38379 <https://bugs.python.org/issue38379>, garbage collection does not 
block on resurrected objects;
BPO 38692 <https://bugs.python.org/issue38692>, os.pidfd_open added that allows 
process management without races and signals;
BPO 39926 <https://bugs.python.org/issue39926>, Unicode support updated to 
version 13.0.0
BPO 1635741 <https://bugs.python.org/issue1635741>, when Python is initialized 
multiple times in the same process, it does not leak memory anymore
A number of Python builtins (range, tuple, set, frozenset, list) are now sped 
up using PEP 570 <https://www.python.org/dev/peps/pep-0570> vectorcall
A number of standard library modules (audioop, ast, grp, _hashlib, pwd, 
_posixsubprocess, random, select, struct, termios, zlib) are now using the 
stable ABI defined by PEP 384 <https://www.python.org/dev/peps/pep-0384/>.
(Hey, fellow core developer, if a feature you find important is missing from 
this list, let Łukasz know <mailto:luk...@python.org>.)
The next pre-release, the last alpha release of Python 3.9, will be 3.9.0a6. It 
is currently scheduled for 2020-04-22. Until then, stay safe!

Your friendly release team,
Ned Deily @nad <https://discuss.python.org/u/nad>
Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower>
Łukasz Langa @ambv <https://discuss.python.org/u/ambv>___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/QD7NHTGJ4X5N7GIWZ5UBD74PITIAE64Q/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Policy around compile-time flags in bugfix releases

2020-03-01 Thread Łukasz Langa

Hey there,
the release managers noticed Stefan adding a new compile flag and backporting 
it to (soon to be) 3.7.7 and (eventually to be) 3.8.3.

Context: https://bugs.python.org/issue39794

Should this go in? It does look like a new feature to us.

- Ł and Ned___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/5XUQVY4IUPMFZKQP4GPTU2UMJTOLNBQC/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Python 3.8.2 and 3.9.0a4 are now available

2020-02-25 Thread Łukasz Langa

On behalf of the entire Python development community, and the currently serving
Python release team in particular, I’m pleased to announce the release of two
of the latest Python editions.

Python 3.8.2

Python 3.8.2 is the second maintenance release of Python 3.8 and contains two
months worth of bug fixes. Detailed information about all changes made in 3.8.2
can be found in its change log
.
Note that compared to 3.8.1, version 3.8.2 also contains the changes
introduced in 3.8.2rc1 and 3.8.2rc2.

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.2 here:
https://www.python.org/downloads/release/python-382/

See the “What’s New in Python 3.8
” document for more information
about features included in the 3.8 series.

Maintenance releases for the 3.8 series will continue at regular bi-monthly
intervals, with 3.8.3 planned for April 2020 (at the PyCon US sprints
).

Python 3.9.0a4

An early developer preview of Python 3.9 is also ready:
https://www.python.org/downloads/release/python-390a4/

Python 3.9 is still in development. This releasee, 3.9.0a4 is the fourth of six
planned alpha releases. Alpha releases are intended to make it easier to test
the current state of new features and bug fixes and to test the release
process. During the alpha phase, features may be added up until the start of
the beta phase (2020-05-18) and, if necessary, may be modified or deleted up
until the release candidate phase (2020-08-10). Please keep in mind that this
is a preview release and its use is not recommended for production environments.

We hope you enjoy both!

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/
Your friendly release team,
Ned Deily
Steve Dower
Łukasz Langa___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/YLMHMKLQB23XBMQGSG6HOTK6URA2FB5L/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.2rc2 is now available for testing

2020-02-18 Thread Łukasz Langa

Python 3.8.2rc2 is the second release candidate of the second maintenance
release of Python 3.8. Go get it here:

https://www.python.org/downloads/release/python-382rc2/

Why a second release candidate?

The major reason for RC2 is that GH-16839
has been reverted.

The original change was supposed to fix for some edge cases in urlparse
(numeric paths, recognizing netlocs without //; details in BPO-27657
). Unfortunately it broke third parties
relying on the pre-existing undefined behavior.

Sadly, the reverted fix has already been released as part of 3.8.1 (and 3.7.6
where it’s also reverted now). As such, even though the revert is itself a bug
fix, it is incompatible with the behavior of 3.8.1.

Please test.

Timeline

Assuming no critical problems are found prior to 2020-02-24, the currently
scheduled release date for 3.8.2 (as well as 3.9.0 alpha 4!), 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.2 and as
such its main purpose is testing.

Maintenance releases for the 3.8 series will continue at regular bi-monthly
intervals, with 3.8.3 planned for April 2020 (during sprints at PyCon US).

What’s new?

The Python 3.8 series is the newest feature release of the Python language, and
it contains many new features and optimizations. 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 version 3.8.2 specifically can
be found in its change log
.

We hope you enjoy Python 3.8!

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

- Ł___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/DW2XBRKSZZCREQ42HSPTJIGFTKXQGW2X/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Cannot release 3.9.0a4

2020-02-17 Thread Łukasz Langa

Currently Buildbots are reporting that master is not in a releasable state:
https://buildbot.python.org/all/#/release_status 


Namely, it does not build on Windows 7:
- https://buildbot.python.org/all/#/builders/150/builds/338 

- https://buildbot.python.org/all/#/builders/81/builds/390 


and suffers from test failures on:
- macOS (importlib) - https://buildbot.python.org/all/#/builders/275/builds/249 

- Fedora (shutil and zipfile) - 
https://buildbot.python.org/all/#/builders/449/builds/31 



Please look at this, especially the Windows compile failure. I will be 
attempting 3.9.0a4 next week with 3.8.2 final.

- Ł___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/7HTKJO4APMRTLGUB2N5TGJ6CJBVR3UZX/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: A urlparse regression in minor version

2020-02-16 Thread Łukasz Langa

OK, let's revert this for 3.8.2. I will make 3.8.2rc2 with this to highlight 
the revert and get some testing in.

-- 
Best regards,
Łukasz Langa

> On 16 Feb 2020, at 19:31, Senthil Kumaran  wrote:
> 
> 
> I have created the PRs for the revert in 3.8.2 and 3.7.7 
> 
> https://github.com/python/cpython/pull/18525 (3.8) - Acceptance definitely 
> depends on the RM ( Łukasz' s call) and I will support it.
> https://github.com/python/cpython/pull/18526 (3.7) - Let this be reverted 
> only if 3.8 gets reverted.
> 
> @Ned - 
> > Note that we strongly imply that we sanely handle them by offering the 
> > "scheme=" parameter to urlparse. 
> 
> It is a good idea. I will dig deeper with the help of test cases for 3.8. ( 
> At the moment, given the tests cases the only test case which obviously fails 
> the expectation in 'localhost:8000')
> But it seems that in the bug report, it was discussed and analyzed before the 
> call was taken to simplify the logic of parsing support.
> So, for 3.9 use case, we can revisit this decision separately and i will 
> account for the points that you have brought up.
> 
> If do not end up reverting in 3.8.2 - at the moment, my approach will be to 
> document the behavior and encourage users to make sure that URL's have a 
> scheme for the valid parsing behavior between 3.7, 3.8, and 3.9
> 
> 
> 
> 
>> On Sun, Feb 16, 2020 at 4:21 AM Antoine Pitrou  wrote:
>> 
>> FWIW, I agree with Senthil here.  A slight behaviour change in 3.9 is
>> fine, especially in an area where the "right" semantics are not
>> immediately obvious.  What we want to avoid is breaking behaviour
>> changes in bugfix releases.
>> 
>> Regards
>> 
>> Antoine.
>> 
>> 
>> Le 16/02/2020 à 13:13, Senthil Kumaran a écrit :
>> > 
>> > On Sun, Feb 16, 2020 at 2:20 AM Ned Deily > > <mailto:n...@python.org>> wrote:
>> > 
>> > 
>> > 
>> > For 3.9.0, I recommend we reconsider this change (temporarily
>> > reverting it) and consider whether an API change to accommodate the
>> > various use cases would be better
>> > 
>> > 
>> > For 3.9. - I am ready to defend the patch even at the cost of the
>> > breaking of the parsing of undefined behavior.  We should keep it. The
>> > patch simplifies a lot of corner cases and fixes the reported bugs. We
>> > don't guarantee backward compatibility between major versions, so I
>> > assume users will be careful when relying upon this undefined behavior
>> > and will take corrective action on their side before upgrading to 3.9.
>> > 
>> > We want patch releases to be backward compatible. That was the
>> > user-complaint.
>> > 
>> > Thanks,
>> > Senthil
>> > 
>> > 
>> > 
>> > ___
>> > python-committers mailing list -- python-committers@python.org
>> > To unsubscribe send an email to python-committers-le...@python.org
>> > https://mail.python.org/mailman3/lists/python-committers.python.org/
>> > Message archived at 
>> > https://mail.python.org/archives/list/python-committers@python.org/message/SQE6TKOYZKEFGWMUHU5RCHRVWJ27TIQV/
>> > Code of Conduct: https://www.python.org/psf/codeofconduct/
>> > 
>> ___
>> python-committers mailing list -- python-committers@python.org
>> To unsubscribe send an email to python-committers-le...@python.org
>> https://mail.python.org/mailman3/lists/python-committers.python.org/
>> Message archived at 
>> https://mail.python.org/archives/list/python-committers@python.org/message/P6N7GWW5RQ66467NXYJPHV6JKBY4QM27/
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at 
> https://mail.python.org/archives/list/python-committers@python.org/message/CVYPD6QL4O6GDEMYWRGWX3SSCBFJ6TYE/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/OLJL6SIAOYTPZPSEWHLQ33VFHMLSRSQT/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: A urlparse regression in minor version

2020-02-14 Thread Łukasz Langa

Ned, what are you doing with this for 3.7.7? Reverting?

- Ł


> On 13 Feb 2020, at 22:18, Barry Warsaw  wrote:
> 
> On Feb 11, 2020, at 05:26, Łukasz Langa  wrote:
>> 
>> I'll let others voice their opinions but my intuition for 3.8.x is to leave 
>> your patch be. True, it should not have been backported but it was, and it 
>> was already released as part of 3.8.1 and now 3.8.2rc1.
> 
> I don’t think you should worry about 3.8.2rc1.  That’s not a release version 
> so shouldn’t impact the decision IMHO.
> 
> Whether 3.8.1 is important enough not to revert this change is an RM decision.
> 
> -Barry
> 
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/ZEOOB6K4256UIDFWQLYTSYJ6AWEGGAY7/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: A urlparse regression in minor version

2020-02-11 Thread Łukasz Langa

I'll let others voice their opinions but my intuition for 3.8.x is to leave 
your patch be. True, it should not have been backported but it was, and it was 
already released as part of 3.8.1 and now 3.8.2rc1.

The user will have to special-case the change in behavior anyway. I feel like 
it is easier for them to do so by only special-casing "sys.version_info < (3, 
8, 1)". The alternative if you revert your patch will be to special case both 
"sys.version_info < (3, 9)" and "sys.version_info == (3, 8, 1)" (let alone 
3.8.2rc1). That is worse I think.

So, the only thing to do is to clearly document that there was a change, not in 
3.9 but in 3.8.1 and forward.

Agreed that it's a bit of a mess for 3.7 since that was way later in the 
release cadence with only 3.7.6 getting the change. I will let Ned decide here.

- Ł


> On 10 Feb 2020, at 15:27, Senthil Kumaran  wrote:
> 
> Hello Python-Committers,
> 
> In https://bugs.python.org/issue27657 , I 
> introduced a regression in a minor release.
> The original patch to parsing logic of URL, cleaned up a lot of corner cases 
> (https://github.com/python/cpython/pull/661 
> ) and I felt good about the 
> change.
> However, the mistake was with the backport.
> 
> Demo:
> 
> $ ./python 
> Python 3.8.0 (default, Feb 10 2020, 06:15:43) 
> [GCC 9.2.1 20191008] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> from urllib.parse import urlparse
> >>> urlparse('localhost:8080')
> ParseResult(scheme='', netloc='', path='localhost:8080', params='', query='', 
> fragment='')
> 
> 
> 
> $ ./python 
> Python 3.8.1+ (heads/3.8:b086ea5edc, Feb 10 2020, 06:15:44) 
> [GCC 9.2.1 20191008] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> from urllib.parse import urlparse
> >>> urlparse('localhost:8080')
> ParseResult(scheme='localhost', netloc='', path='8080', params='', query='', 
> fragment='')
> 
> ---
> 
> When I read an associated bug report against a user of the software (like 
> this: https://github.com/mozilla/bleach/issues/503 
> ) - I feel that this was a 
> mistake.
> The change of test-suite in minor versions should have alerted me, but I seem 
> to have missed it.
> 
> I am planning to revert this change in 3.8.2 and 3.7.7
> Should I highlight this in any documentation?  Thoughts and opinions?
> 
> Thank you,
> Senthil
> 
> 
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at 
> https://mail.python.org/archives/list/python-committers@python.org/message/2ONL562L35S77FGCLYH2ZDWVAXHH2BZP/
> Code of Conduct: https://www.python.org/psf/codeofconduct/

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

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

2020-02-11 Thread Łukasz Langa

Python 3.8.2rc1 is the release candidate of the second maintenance release of
Python 3.8. Go get it here:

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

Assuming no critical problems are found prior to 2020-02-17, the scheduled
release date for 3.8.2 (as well as 3.9.0 alpha 4!), 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.2 and as
such its main purpose is testing.

Maintenance releases for the 3.8 series will continue at regular bi-monthly
intervals, with 3.8.3 planned for April 2020 (during sprints at PyCon US).

What’s new?

Detailed information about all changes made in version 3.8.2 specifically can
be found in its change log
.

We hope you enjoy Python 3.8!

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

- Ł
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/TNYC4DPNMKAGRERBFEXTJ4RE4CRB7WW3/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.9.0a3 available for testing

2020-01-25 Thread Łukasz Langa

Go get it here: https://www.python.org/downloads/release/python-390a3/ 

This is an early developer preview of Python 3.9

Python 3.9 is still in development. This releasee, 3.9.0a3 is the third of six 
planned alpha releases. Alpha releases are intended to make it easier to test 
the current state of new features and bug fixes and to test the release 
process. During the alpha phase, features may be added up until the start of 
the beta phase (2020-05-18) and, if necessary, may be modified or deleted up 
until the release candidate phase (2020-08-10). Please keep in mind that this 
is a preview release and its use is not recommended for production environments.

Major new features of the 3.9 series, compared to 3.8

Many new features for Python 3.9 are still being planned and written. Among the 
new major new features and changes so far:

PEP 602 , Python adopts a stable 
annual release cadence
BPO 38379 , garbage collection does not 
block on resurrected objects;
BPO 38692 , os.pidfd_open added that allows 
process management without races and signals;
A number of standard library modules (audioop, ast, grp, _hashlib, pwd, 
_posixsubprocess, random, select, struct, termios, zlib) are now using the 
stable ABI defined by PEP 384 .
(Hey, fellow core developer, if a feature you find important is missing from 
this list, let Łukasz know .)
The next pre-release of Python 3.9 will be 3.9.0a4, currently scheduled for 
2020-02-17.

- Ł


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

[python-committers] [RELEASE] Python 3.8.1, 3.7.6, 3.6.10, and 3.9.0a2 are now available!

2019-12-19 Thread Łukasz Langa

from locale import seasons_greetings
seasons_greetings()

On behalf of the entire Python development community, and the currently serving 
Python release team in particular, I'm pleased to announce the unprecedented 
combined release of no less than four versions of Python. Let's dig in!


Python 3.8.1

Python 3.8.1 is 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.1 here:

https://www.python.org/downloads/release/python-381/ 
<https://www.python.org/downloads/release/python-381/>

See the “What’s New in Python 3.8 
<https://docs.python.org/3.8/whatsnew/3.8.html>” document for more information 
about features included in the 3.8 series. Detailed information about all 
changes made in 3.8.1 can be found in its change log 
<https://docs.python.org/release/3.8.1/whatsnew/changelog.html#changelog>.

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



Python 3.7.6

Python 3.7.6, the next bugfix release of Python 3.7, is also available. You can 
find the release files, a link to the change log, and more information here:

https://www.python.org/downloads/release/python-376/ 
<https://www.python.org/downloads/release/python-376/>



Python 3.9.0a2

An early developer preview of Python 3.9 is also ready: 
https://www.python.org/downloads/release/python-390a2/ 
<https://www.python.org/downloads/release/python-390a2/>

Python 3.9 is still in development. This releasee, 3.9.0a2 is the second of six 
planned alpha releases. Alpha releases are intended to make it easier to test 
the current state of new features and bug fixes and to test the release 
process. During the alpha phase, features may be added up until the start of 
the beta phase (2020-05-18) and, if necessary, may be modified or deleted up 
until the release candidate phase (2020-08-10). Please keep in mind that this 
is a preview release and its use is not recommended for production environments.


Python 3.6.10

And, one more thing: Python 3.6.10, the next security fix release of Python 
3.6, is also available:

https://www.python.org/downloads/release/python-3610/ 
<https://www.python.org/downloads/release/python-3610/>



We hope you enjoy all those!

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/ <https://www.python.org/psf/>


Your friendly release team,
Ned Deily
Steve Dower
Łukasz Langa


signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/6T5GL5LN6OC5QY32Y6RV5VN335NNRHAO/
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 -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/X4V3MV5BKWCG6T7Q6R2CTJUXE5HPQPJD/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[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!

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

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

[python-committers] [RELEASE] Python 3.9.0a1 available for testing

2019-11-19 Thread Łukasz Langa

Go get it here: https://www.python.org/downloads/release/python-390a1/ 

This is an early developer preview of Python 3.9

Python 3.9 is still in development. This releasee, 3.9.0a1 is the first of six 
planned alpha releases. Alpha releases are intended to make it easier to test 
the current state of new features and bug fixes and to test the release 
process. During the alpha phase, features may be added up until the start of 
the beta phase (2020-05-18) and, if necessary, may be modified or deleted up 
until the release candidate phase (2020-08-10). Please keep in mind that this 
is a preview release and its use is not recommended for production environments.

Major new features of the 3.9 series, compared to 3.8

Many new features for Python 3.9 are still being planned and written. Among the 
new major new features and changes so far:

PEP 602 , Python adopts a stable 
annual release cadence
BPO 38379 , garbage collection does not 
block on resurrected objects;
BPO 38692 , os.pidfd_open added that allows 
process management without races and signals;
A number of standard library modules (audioop, ast, grp, _hashlib, pwd, 
_posixsubprocess, random, select, struct, termios, zlib) are now using the 
stable ABI defined by PEP 384 .
(Hey, fellow core developer, if a feature you find important is missing from 
this list, let Łukasz know .)
The next pre-release of Python 3.9 will be 3.9.0a2, currently scheduled for 
2019-12-16.

- Ł


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

[python-committers] [RELEASE] Python 3.8.0 is now available

2019-10-14 Thread Łukasz Langa

On behalf of the Python development community and the Python 3.8 release team,
I’m pleased to announce the availability of Python 3.8.0.

Python 3.8.0 is the newest feature release of the Python language, and it
contains many new features and optimizations. You can find Python 3.8.0 here:

https://www.python.org/downloads/release/python-380/

Most third-party distributors of Python should be making 3.8.0 packages
available soon.

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 follow at regular bi-monthly
intervals starting in December of 2019.

We hope you enjoy Python 3.8!

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

- Ł

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

[python-committers] I'm working on the release of Python 3.8.0 right now

2019-10-14 Thread Łukasz Langa

Please hold your breath. Unless you have some last minute blocker, then let me 
know immediately.

- Ł


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

[python-committers] [RELEASE] Python 3.8.0rc1 is now available

2019-10-01 Thread Łukasz Langa

Python 3.8.0 is almost ready. After a rather tumultuous few days, we are very 
happy to announce the availability of the release candidate:

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


This release, 3.8.0rc1, is the final planned release preview. Assuming no 
critical problems are found prior to 2019-10-14, the scheduled release date for 
3.8.0, no code changes are planned between this release candidate and the final 
release.
Please keep in mind that this is not the gold release yet and as such its use 
is not recommended for production environments.

Major new features of the 3.8 series, compared to 3.7

Some of the new major new features and changes in Python 3.8 are:

PEP 572 , Assignment expressions
PEP 570 , Positional-only arguments
PEP 587 , Python Initialization 
Configuration (improved embedding)
PEP 590 , Vectorcall: a fast calling 
protocol for CPython
PEP 578 , Runtime audit hooks
PEP 574 , Pickle protocol 5 with 
out-of-band data
Typing-related: PEP 591  (Final 
qualifier), PEP 586  (Literal types), 
and PEP 589  (TypedDict)
Parallel filesystem cache for compiled bytecode
Debug builds share ABI as release builds
f-strings support a handy = specifier for debugging
continue is now legal in finally: blocks
on Windows, the default asyncio event loop is now ProactorEventLoop
on macOS, the spawn start method is now used by default in multiprocessing
multiprocessing can now use shared memory segments to avoid pickling costs 
between processes
typed_ast is merged back to CPython
LOAD_GLOBAL is now 40% faster
pickle now uses Protocol 4 by default, improving performance
(Hey, fellow core developer, if a feature you find important is missing from 
this list, let Łukasz know .)
Call to action: focus on the docs now

Are all your changes properly documented?
Did you notice other changes you know of to have insufficient documentation?
Can you help with the “What’s New 
” document?

- Ł



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

[python-committers] Re: Currently working on the release of Python 3.8.0rc1

2019-10-01 Thread Łukasz Langa


> On 30 Sep 2019, at 20:43, Terry Reedy  wrote:
> 
> On 9/30/2019 3:48 AM, Łukasz Langa wrote:
> 
>> To help our chances, please avoid any source-related activity on the 3.8 
>> branch from now until the release of 3.8.0. Yes, that also counts for bug 
>> fixes unless they are critical. (Yeah, it might be a bit annoying but nobody 
>> wants to be the person who introduced a last minute regression in a major 
>> release.)
> 
> In the past, x.y.zrc1 has been tagged and branched somehow so that commits to 
> x.y are commits to x.y.z+, the future x.y.(z+1).  (I never paid attention to 
> the details).  For instance, 3.7 is currently 3.7.4+. As soon as Ned makes 
> 3.7.5rc1, commits to 3.7 will go to 3.7.5+, the future 3.7.6, and will not 
> disturb 3.7.5rc1 until Ned cherry picks them into the rc branch for 3.7.5.
> 
> Similarly, 3.8 is currently 3.8.b4+.  As soon as you make 3.8.0rc1, if you do 
> it the same way x.y.0rc1 has been done before recently, 3.8 commits should go 
> to 3.8.0+, the future 3.8.1.  Nothing should go into 3.8.0 until you pull it 
> in or authorize it for those who know how to put it there (I don't). There 
> should be no need to halt 3.8 activity.

Right, this is what we were doing and it's what we'll be doing this time 
around, too.

However, I feel that the release candidate for a .0 version is rather crucial. 
Cherry-picking changes to the gold release from an active support branch has 
non-zero risk of unexpected consequences. That can be due to non-trivial 
relationships between new commits or due to the release manager messing up the 
cherry-pick.

Another complication is a post-release merge conflict due to cherry picks.

This is why the overall recommendation I received from the more experienced 
release managers is that if there's too much activity on the branch we should 
release another preview. I agree with that, otherwise it gets too messy.

...but I don't want another RC if we can help it :-)

- Ł


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

[python-committers] Re: Currently working on the release of Python 3.8.0rc1

2019-10-01 Thread Łukasz Langa

I merged it. In the future: you can use priorities on BPO issues to make it 
more visible.

- Ł



> On 1 Oct 2019, at 07:03, Giampaolo Rodola'  wrote:
> 
> Hello Łukasz,
> I consider this one critical enough to get into 3.8:
> https://bugs.python.org/issue38319 <https://bugs.python.org/issue38319>
> Long story short: shutil.copyfile() and socket.sendfile() are broken on 
> 32-bit platforms for files >= 2GiB.
> shutil.copyfile() was modified by me in the 3.8 cycle so the bug only affects 
> 3.8 and 3.9.
> 
> 
> On Mon, Sep 30, 2019 at 3:48 PM Łukasz Langa  <mailto:luk...@langa.pl>> wrote:
> Team,
> amazing job on getting us back on track over the weekend.
> 
> Thank you
> All release blockers and deferred release blockers solved. And there was 
> relatively little additional activity on the branch -- as expected at this 
> point! Thank you for this, it will help get the release candidate out on time.
> 
> I'm working on cutting RC1 today
> Hopefully all sanity checks, as well as building the source tarball and the 
> binary installers for macOS and Windows will all work out fine and we'll be 
> seeing RC1 out tonight.
> 
> RC2 and the date of 3.8.0 gold
> If we manage to avoid the need for RC2, we will be able to release 3.8.0 on 
> October 14th. If we need an RC2, that will slip by a week. I hope we won't. 
> Ideally RC1 should be identical codewise to 3.8.0.
> 
> To help our chances, please avoid any source-related activity on the 3.8 
> branch from now until the release of 3.8.0. Yes, that also counts for bug 
> fixes unless they are critical. (Yeah, it might be a bit annoying but nobody 
> wants to be the person who introduced a last minute regression in a major 
> release.)
> 
> Note I didn't say I forbid any activity. I have no power over you, actually. 
> More importantly though, I trust your judgement if you assess some bug is bad 
> enough the fix absolutely has to get into 3.8.0. Moreover, I specifically 
> said source-related activity because...
> 
> 3.8.0 is important. To some users it will be the first and the last release 
> in the 3.8 series they will see.
> 
> We need you to focus on the docs now
> Are all your changes properly documented?
> Did you notice other changes you know of to have insufficient documentation?
> Can you help with the "What's New" document?
> 
> anxiously configure-&&-makingly y'rs
> - Ł
> ___
> python-committers mailing list -- python-committers@python.org 
> <mailto:python-committers@python.org>
> To unsubscribe send an email to python-committers-le...@python.org 
> <mailto:python-committers-le...@python.org>
> https://mail.python.org/mailman3/lists/python-committers.python.org/ 
> <https://mail.python.org/mailman3/lists/python-committers.python.org/>
> Message archived at 
> https://mail.python.org/archives/list/python-committers@python.org/message/ACMKEQNGK4FVUIZ6TYD5H26OSPIO5GSN/
>  
> <https://mail.python.org/archives/list/python-committers@python.org/message/ACMKEQNGK4FVUIZ6TYD5H26OSPIO5GSN/>
> Code of Conduct: https://www.python.org/psf/codeofconduct/ 
> <https://www.python.org/psf/codeofconduct/>
> 
> 
> --
> Giampaolo - http://grodola.blogspot.com <http://grodola.blogspot.com/>
> 



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

[python-committers] Re: Currently working on the release of Python 3.8.0rc1

2019-09-30 Thread Łukasz Langa


> On 30 Sep 2019, at 16:09, Nick Coghlan  wrote:
> 
> I've filed https://bugs.python.org/issue38326 as a release blocker, as
> I don't think we should be cutting RCs when changes have been made to
> a PEP-approved API without any pre-merge design discussion.

Nick, Victor, as co-authors of said PEP, please reach a decision ASAP.

- Ł


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

[python-committers] Currently working on the release of Python 3.8.0rc1

2019-09-30 Thread Łukasz Langa

Team,
amazing job on getting us back on track over the weekend.

Thank you
All release blockers and deferred release blockers solved. And there was
relatively little additional activity on the branch -- as expected at this
point! Thank you for this, it will help get the release candidate out on time.

I'm working on cutting RC1 today
Hopefully all sanity checks, as well as building the source tarball and the
binary installers for macOS and Windows will all work out fine and we'll be
seeing RC1 out tonight.

RC2 and the date of 3.8.0 gold
If we manage to avoid the need for RC2, we will be able to release 3.8.0 on
October 14th. If we need an RC2, that will slip by a week. I hope we won't.
Ideally RC1 should be identical codewise to 3.8.0.

To help our chances, please avoid any source-related activity on the 3.8 branch
from now until the release of 3.8.0. Yes, that also counts for bug fixes unless
they are critical. (Yeah, it might be a bit annoying but nobody wants to be the
person who introduced a last minute regression in a major release.)

Note I didn't say I forbid any activity. I have no power over you, actually.
More importantly though, I trust your judgement if you assess some bug is bad
enough the fix absolutely has to get into 3.8.0. Moreover, I specifically said
source-related activity because...

3.8.0 is important. To some users it will be the first and the last release in
the 3.8 series they will see.

We need you to focus on the docs now
Are all your changes properly documented?
Did you notice other changes you know of to have insufficient documentation?
Can you help with the "What's New" document?

anxiously configure-&&-makingly y'rs
- Ł

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

[python-committers] ATTENTION: Python 3.8.0rc1 is due on Monday, Sep 30th

2019-09-27 Thread Łukasz Langa

Hello fellow core developers and testers,
as documented in PEP 569, we're less than 72 hours away from tagging the 
release candidate of Python 3.8.0. Ideally we'd only need one.

Sadly, at the moment we're looking rather miserable release-blocker wise:

https://bugs.python.org/issue?%40action=search&%40columns=activity&%40columns=id&%40columns=status&%40columns=title&%40pagesize=50&%40sort=activity&%40sortdir=on&%40startwith=0&ignore=file%3Acontent&priority=1&status=1&versions=22
 



The buildbots look better but they're also not perfect (there's too much red in 
recent history):

https://buildbot.python.org/all/#/grid?branch=3.8&tag=stable 



If you're on any of the release blockers, please work on fixing them ASAP.
If you're not on any release blockers, please avoid any commits to 3.8 for the 
time being.
The release candidate should ideally *be* 3.8.0, we don't want any untested 
last-minute changes.


Stabilizingly y'rs
- Ł


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

[python-committers] [RELEASE] ACTION REQUIRED: Python 3.8.0b4 now available for testing

2019-08-30 Thread Łukasz Langa

It's time for the last beta release of Python 3.8. Go find it at:

https://www.python.org/downloads/release/python-380b4/

This release is the last of four planned beta release previews. Beta release
previews are intended to give the wider community the opportunity to test new
features and bug fixes and to prepare their projects to support the new feature
release. The next pre-release of Python 3.8 will be 3.8.0c1, the first release
candidate, currently scheduled for 2019-09-30.

Call to action

We strongly encourage maintainers of third-party Python projects to test with
3.8 during the beta phase and report issues found to the Python bug tracker as
soon as possible. Please note this is the last beta release, there is not much
time left to identify and fix issues before the release of 3.8.0. If you were
hesitating trying it out before, now is the time.

While the release is planned to be feature complete entering the beta phase, it
is possible that features may be modified or, in rare cases, deleted up until
the start of the release candidate phase (2019-09-30). Our goal is have no ABI
changes after beta 3 and no code changes after 3.8.0c1, the release candidate.

To achieve that, it will be extremely important to get as much exposure for 3.8
as possible during the beta phase. That beta phase is coming to an end. Please
test now.

Please keep in mind that this is a preview release and its use is not
recommended for production environments.

Acknowledgments

Many developers worked hard for the past four weeks to squash remaining bugs,
some requiring non-obvious decisions. Many thanks to the most active, namely
Raymond Hettinger, Steve Dower, Victor Stinner, Terry Jan Reedy, Serhiy
Storchaka, Pablo Galindo Salgado, Tal Einat, Zackery Spytz, Ronald Oussoren,
Neil Schemenauer, Inada Naoki, Christian Heimes, and Andrew Svetlov.

3.8.0 would not reach the Last Beta without you. Thank you!

- Ł

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

[python-committers] [RELEASE] Python 3.8.0b3 is now available for testing

2019-07-29 Thread Łukasz Langa

This time without delays, I present you Python 3.8.0b3:

https://www.python.org/downloads/release/python-380b3/

This release is the third of four planned beta release previews. Beta release
previews are intended to give the wider community the opportunity to test new
features and bug fixes and to prepare their projects to support the new feature
release. The next pre-release of Python 3.8 will be 3.8.0b4, the last beta
release, currently scheduled for 2019-08-26.

Call to action

We strongly encourage maintainers of third-party Python projects to test with
3.8 during the beta phase and report issues found to the Python bug tracker
as soon as possible. While the release is planned to
be feature complete entering the beta phase, it is possible that features may
be modified or, in rare cases, deleted up until the start of the release
candidate phase (2019-09-30). Our goal is have no ABI changes after beta 3 and
no code changes after 3.8.0rc1, the release candidate. To achieve that, it will
be extremely important to get as much exposure for 3.8 as possible during the
beta phase.

Please keep in mind that this is a preview release and its use is not
recommended for production environments.

Last beta coming

Beta 4 can only be released if all “Release blocker” and “Deferred blocker”
issues on bugs.python.org for 3.8.0 are resolved.
Please prioritize those for the next four weeks.

Acknowledgements

Thanks to our binary builders, Ned and Steve, who were very quick today to get
the macOS and Windows installers ready. The Windows story in particular got
pretty magical, it’s now really fully automatic end-to-end.

Thanks to Victor for vastly improving the reliability of multiprocessing tests
since Beta 2.

Thanks to Pablo for keeping the buildbots green.

- Ł

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

[python-committers] [RELEASE] Python 3.8.0b2 is now available for testing

2019-07-04 Thread Łukasz Langa

After a few days of delay, but somewhat cutely timed with the US Independence
Day, I present you Python 3.8.0b2:

https://www.python.org/downloads/release/python-380b2/

This release is the second of four planned beta release previews. Beta release
previews are intended to give the wider community the opportunity to test new
features and bug fixes and to prepare their projects to support the new feature
release. The next pre-release of Python 3.8 will be 3.8.0b3, currently
scheduled for 2019-07-29.

Call to action

Please keep in mind that this is a preview release and its use is not
recommended for production environments.

No more non-bugfixes allowed on the “3.8” branch

The time has come, team. Please help make Python 3.8 as stable as possible and
keep all features not currently landed for Python 3.9. Don’t fret, it’ll come
faster than you think.

- Ł

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

[python-committers] Re: python-committers is now running on Mailman 3

2019-06-06 Thread Łukasz Langa

Thanks! This message is posted directly from HyperKitty.
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/QKI6ANMYZ2DBTLDQRKV2TN3UPJS7BXMS/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.0b1 is now available for testing

2019-06-04 Thread Łukasz Langa

The time has come for Python 3.8.0b1:
https://www.python.org/downloads/release/python-380b1/ 

This release is the first of four planned beta release previews. Beta release 
previews are intended to give the wider community the opportunity to test new 
features and bug fixes and to prepare their projects to support the new feature 
release. The next pre-release of Python 3.8 will be 3.8.0b2, currently 
scheduled for 2019-07-01.


Call to action

We strongly encourage maintainers of third-party Python projects to test with 
3.8 during the beta phase and report issues found to the Python bug tracker 
 as soon as possible. While the release is planned to 
be feature complete entering the beta phase, it is possible that features may 
be modified or, in rare cases, deleted up until the start of the release 
candidate phase (2019-09-30). Our goal is have no ABI changes after beta 3 and 
no code changes after 3.8.0rc1, the release candidate. To achieve that, it will 
be extremely important to get as much exposure for 3.8 as possible during the 
beta phase.

Please keep in mind that this is a preview release and its use is not 
recommended for production environments.


A new challenger has appeared!

With the release of Python 3.8.0b1, development started on Python 3.9. The 
“master” branch in the cpython repository now tracks development of 3.9 while 
Python 3.8 received its own branch, called simply “3.8”.


Acknowledgments

As you might expect, creating new branches triggers a lot of changes in 
configuration for all sorts of tooling that we’re using. Additionally, the 
inevitable deadline for new features caused a flurry of activity that tested 
the buildbots to the max. The revert hammer got  used more than once.

I would not be able to make this release available alone. Many thanks to the 
fearless duo of Pablo Galindo Salgado and Victor Stinner for spending tens of 
hours during the past week working on getting the buildbots green for release. 
Seriously, that took a lot of effort. We are all so lucky to have you both.

Thanks to Andrew Svetlov for his swift fixes to asyncio and to Yury Selivanov 
for code reviews, even when jetlagged. Thanks to Julien Palard for untangling 
the documentation configs. Thank you to Zachary Ware for help with buildbot and 
CI configuration. Thanks to Mariatta for helping with the bots. Thank you to 
Steve Dower for delivering the Windows installers.

Most importantly though, huge thanks to Ned Deily who not only helped me 
understand the scope of this special release but also did some of the grunt 
work involved.

Last but not least, thanks to you for making this release more meaty than I 
expected. There’s plenty of super exciting changes in there. Just take a look 
at “What’s New ”!


One more thing

Hey, fellow Core Developer, Beta 2 is in four weeks. If your important new 
feature got reverted last minute, or you decided not to merge due to inadequate 
time, I have a one time offer for you (restrictions apply). If you:

find a second core developer champion for your change; and
in tandem you finish your change complete with tests and documentation before 
Beta 2
then I will let it in. I’m asking for a champion because it’s too late now for 
changes with hasty design or code review. And as I said, restrictions apply. 
For instance, at this point changes to existing APIs are unlikely to be 
accepted. Don’t start new work with 3.8 in mind. 3.9 is going to come sooner 
than you think!



- Ł


signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Python 3.8.0b1 not there yet

2019-06-04 Thread Łukasz Langa


> On 4 Jun 2019, at 22:05, Terry Reedy  wrote:
> 
> > On 4 Jun 2019, at 21:43, Terry Reedy  wrote:
> >> May I merge non-intrusive changes (to IDLE)?On 6/4/2019 3:46 PM,
> 
> Łukasz Langa wrote:
>> You can but they won't be in beta1 anymore. I am waiting for .exe files to 
>> branch 3.8 out. Sources and Mac binaries for beta 1 are already built.
> 
> Sounds like it would be better to wait until there is a 3.8 branch and a 
> working Backport 3.8 label.

The branch is already there, we'll see how much fiddling is getting the 
backport label to work.

- Ł



signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Python 3.8.0b1 not there yet

2019-06-04 Thread Łukasz Langa

You can but they won't be in beta1 anymore. I am waiting for .exe files to 
branch 3.8 out. Sources and Mac binaries for beta 1 are already built.

- Ł


> On 4 Jun 2019, at 21:43, Terry Reedy  wrote:
> 
> On 6/4/2019 12:12 PM, Victor Stinner wrote:
>> Le mar. 4 juin 2019 à 16:45, Mark Shannon  a écrit :
>>> Does this mean that https://github.com/python/cpython/pull/6641 isn't
>>> going to get in 3.8?
>> Maybe we can consider to put it in beta2, but please don't push any
>> further intrusive change before beta1!
> 
> May I merge non-intrusive changes (to IDLE)?
> 
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/



signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Python 3.8.0b1 not there yet

2019-06-03 Thread Łukasz Langa

tl;dr - We're on it but Beta 1 is special and the buildbots need more
cowbell^H^H more green.

---

Today Victor's been very active helping getting the stable buildbots green. Two
main issues that were blocking Beta 1 were: a coredump in new functionality for
subinterpreters (BPO-33608) and asyncio tests being flaky by altering the
environment (BPO-37137).

The former was solved by reverting the offending change. Victor did merge a few
changes to help with the latter but it's sadly still red on the stable
buildbots.

While it's "just" an altered environment, I'd feel really bad about releasing
the first beta with three stable buildbots in the red. Thankfully, Andrew
Svetlov is looking at the problem as you're reading this.

Another thing about Beta 1 is that it's the moment where the branch is cut,
which also triggers quite a few required configuration changes in CI, Github,
Buildbot, Roundup, and so on. Ned has been helping me understand the full scope
of this today.

**Please avoid pushing last minute changes while we are trying to get the
stable buildbots all green for release. Thanks for your understanding!**

- Ł



signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Python 3.8.0b1 branch cut-off moved to Monday

2019-05-30 Thread Łukasz Langa

I received a few pleas to create the 3.8 branch on Monday. Weekends are 
apparently when unpaid contributors can spend some extra time on their labor of 
love. Given the current flurry of activity, I see no issue allowing for those 
extra three days.

Happy hacking, please leave the branch squeaky clean by Sunday EOD AoE.

- Ł


signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.0a4 is now available for testing

2019-05-07 Thread Łukasz Langa

It's time for the LAST alpha of Python 3.8.0. Go get it here:
https://www.python.org/downloads/release/python-380a4/ 


Python 3.8.0a4 is the fourth and final alpha release of Python 3.8,
the next feature release of Python.  During the alpha phase, Python 3.8
remains under heavy development: additional features will be added
and existing features may be modified or deleted.  Please keep in mind
that this is a preview release and its use is not recommended for
production environments.  The first beta release, 3.8.0b1, is planned
for 2019-05-31.

The release has slipped a week because of me being overwhelmed
with PyCon US this year.  There was also a release blocker and
a breaking change to ElementTree.  Anyway, sorry for the wait!
I moved the planned date of beta1 a few days to make up for it.

If you have a feature you're working on and you'd like to see it in
3.8.0, NOW IS THE TIME TO ACT. Please don't wait until May 30th,
get a proper review and land your change as soon as possible.

Q: Can I get my feature in after that date if I ask nicely?
A: Yes, of course. I will release it in Python 3.9.

- Ł


signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.0a3 is now available for testing

2019-03-26 Thread Łukasz Langa

It's time for the third alpha of Python 3.8.0. Go get it here:
https://www.python.org/downloads/release/python-380a3/

Python 3.8.0a3 is the third of four planned alpha releases of Python 3.8,
the next feature release of Python.  During the alpha phase, Python 3.8
remains under heavy development: additional features will be added
and existing features may be modified or deleted.  Please keep in mind
that this is a preview release and its use is not recommended for
production environments.  The last alpha release, 3.8.0a4, is planned
for 2019-04-29.

I am happy to say that this time all buildbots were properly green. Thank you 
to everybody who worked on that.

- Ł


signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Announcing: signups are open for the 2019 Python Language Summit

2019-02-27 Thread Łukasz Langa


> On 27 Feb 2019, at 14:22, Łukasz Langa  wrote:
> 
> The Python Language Summit is an event for the developers of Python
> implementations (CPython, PyPy, Jython, and so on) to share information,
> discuss our shared problems, and — hopefully — solve them.

Oh, you'd also like to know *when* and *where* it is? Fine.

- When: Wednesday, May 1st 2019
- Where: 0Huntington Convention Center in Cleveland, Ohio

Sorry for missing this in the original e-mail,
Ł


signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Announcing: signups are open for the 2019 Python Language Summit

2019-02-27 Thread Łukasz Langa

The Python Language Summit is an event for the developers of Python
implementations (CPython, PyPy, Jython, and so on) to share information,
discuss our shared problems, and — hopefully — solve them.

These issues might be related to the language itself, the standard
library, the development process, status of Python 3.8 (or plans for
3.9), the documentation, packaging, the website, et cetera. The Summit
focuses on discussion more than on presentations.

If you’d like to attend **and actively participate** in the discussions
during the Language Summit, please fill in this form by March 21st 2019:

https://goo.gl/forms/pexfOGDjpV0BWMer2

We will be evaluating all applications and confirm your attendance by
April 15th. Note: **your attendance is not confirmed** until you heard
back from us.  You don't need to be registered for PyCon in order to
attend the summit.

One of the goals of the Language Summit is to speed up the discussions
and decision making process. Communication over Discourse (or mailing
lists!) is generally more time consuming. As part of efforts to make
this event more open and less mysterious, we are not requiring
invitations by core developers anymore.

However, please understand that we will have to be selective as space
and time are limited. In particular, we are prioritizing active core
contributors, as well as those who we believe will be able to improve
the quality of the discussions at the event and bring a more diverse
perspective to core Python developers.

As for other changes this year, A. Jesse Jiryu Davis will be covering
the event and will post a detailed write up on the official blog of the
PSF shortly after the conference.

We hope to see you at the Summit!
- Mariatta and Łukasz

PS. If you have any questions, the Users section of our Discourse
instance (https://discuss.python.org/c/users) is the best place to ask.
For private communication, write to maria...@python.org and/or
luk...@python.org.



signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.0a1 is now available for testing

2019-02-25 Thread Łukasz Langa

I packaged another release. Go get it here:
https://www.python.org/downloads/release/python-380a2/

Python 3.8.0a2 is the second of four planned alpha releases of Python 3.8,
the next feature release of Python.  During the alpha phase, Python 3.8
remains under heavy development: additional features will be added
and existing features may be modified or deleted.  Please keep in mind
that this is a preview release and its use is not recommended for
production environments.  The next preview release, 3.8.0a3, is planned
for 2019-03-25.

This time around the stable buildbots were a bit less green than they should 
have. This early in the cycle, I didn't postpone the release and I didn't use 
the revert hammer. But soon enough, I will. Let's make sure future changes keep 
the buildbots happy.

- Ł


signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] [RELEASE] Python 3.8.0a1 is now available for testing

2019-02-04 Thread Łukasz Langa

I packaged my first release. *wipes sweat off of face*

Go get it here:
https://www.python.org/downloads/release/python-380a1/

Python 3.8.0a1 is the first of four planned alpha releases of Python 3.8,
the next feature release of Python.  During the alpha phase, Python 3.8
remains under heavy development: additional features will be added
and existing features may be modified or deleted.  Please keep in mind
that this is a preview release and its use is not recommended for
production environments.  The next preview release, 3.8.0a2, is planned
for 2019-02-24.

Apart from building the Mac installers, Ned helped me a lot with the
process, thank you!  Ernest was super quick providing me with all
required access and fixing a Unicode problem I found in Salt,
thank you!

Finally, this release was made on a train to Düsseldorf. There's a PyPy
sprint there. The train is pretty cool, makes this "Wasm! Wasm!" sound.

- Ł



signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] REMINDER: governance vote is closing by end of this week

2018-12-12 Thread Łukasz Langa

You have time until December 16th AoE to rank proposals and cast your ballot. 
More information in PEP 8001.

Note: reading the candidate PEPs will take you a while. Don't wait until Sunday.

- Ł
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] PEP 8012 FAQ

2018-11-27 Thread Łukasz Langa

Answers to some questions I keep getting about PEP 8012: 
https://discuss.python.org/t/pep-8012-frequently-asked-questions/487 


- Ł___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] GOVERNANCE VOTE SCHEDULE UPDATE: Dec 1 - Dec 16 2018

2018-11-15 Thread Łukasz Langa

Thank you to everybody who voiced concern that the originally planned voting 
schedule of Nov 16 - Nov 30 was rushed. In the interest of ensuring everybody 
feels included, as well as to allow time for PEP 801x review and 
clarifications, Barry Warsaw and the other PEP 801x authors [1]_ decided to 
move the vote by two weeks. Barry opened a PR [2]_ which I just merged.

Summary of changes:
- starting tomorrow until December 1st we are entering an official PEP 801x 
review period. Substantive changes to those PEPs are discouraged, 
clarifications as the result of the discussion are encouraged.
- the actual vote will happen on CIVS between December 1st and December 16th.

All details are in PEP 8001 which has been now Accepted and will be marked 
Final sometime later this week after the dust settles. Please read it carefully.

We are sorry for the late change and any inconvenience this might have caused 
you. Our foremost concern is to ensure the vote is going to be considered fair, 
inclusive and legitimate. We hope adjusting the timing helps with that.

One last thing. During the discussion phase, please try to keep discussions on 
Discourse where they were held until this point. Moderators will be available 
in this period to help with readability.

- Ł



.. [1]  Well, we couldn't reach Steve who is in Scotland and Jack. We are sorry 
we couldn't wait for your opinions but the pressure of time didn't allow us to 
do so.
.. [2]  https://github.com/python/peps/pull/841/
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] How do you find Discourse so far?

2018-11-13 Thread Łukasz Langa

Here's a poll:
https://discuss.python.org/t/how-do-you-find-discourse-so-far/429 


- Ł___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Vote on governance will happen between Nov 16 - Nov 30

2018-10-22 Thread Łukasz Langa

The voting procedure is described in PEP 8001. I flipped it from "Draft" to 
"Active" without further changes a few minutes ago. That's in the interest of 
giving everybody enough lead time as well as resolving the situation "well 
before PyCon 2019" as per Guido's and Carol's requests.

Please read all the governance PEPs, ask for clarifications, voice all your 
concerns now. Ideally we will make all of the required changes to the PEPs 
early and not last minute before the vote.

There were some suggestions on Discourse for changes to the selected model, the 
biggest being Stefan's suggestion to encrypt the votes and Donald's suggestion 
to use STAR instead of IRV for counting votes. We ended up not going with those 
suggestions. See Brett's comment here as to why:
https://discuss.python.org/t/pep-8001-python-governance-voting-process/233/46 


- Ł___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Moderation of the Python community

2018-10-17 Thread Łukasz Langa

> On 17 Oct 2018, at 20:44, Brian Curtin  wrote:
> 
> To me that's still a thing we should at least start to work on amongst 
> ourselves, as opposed to something like the issues of offensive word choice 
> or name calling. With the former we have some things to work on smoothing out 
> towards a common goal, and the latter we just want none of.

We should all strive to be professional. The CoC is there to give everyone the 
ability to work toward, as you say, a common goal. While I would like to 
believe that we judge ideas on technical merit, since we are invested in this 
project, all too often we see conversations get heated. Things spill over from 
the technical ideas to ad hominems.

I hope that we can improve discussions and moderation. If we do, then the CoC 
becomes infrequently used. Yet, it is important to have as a reminder and a 
signal to pause when things get overly heated or personal.

- Ł

signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

1 2 >

1 - 100 of 149 matches

Mail list logo