Hello,
In the end of 2019 I've reported an issue where all b.p.o notifications
would get into my spam folder (apparently because my ISP's mail server
marks them as suspicious in the e-mail headers):
https://github.com/python/psf-infra-meta/issues/16
Then since the beginning of 2020 I haven't been receiving b.p.o
notifications anymore. Not even in my spam folder:
https://github.com/python/psf-infra-meta/issues/54
I've never had a single response on those two issues. This means that I
miss all messages that are being posted on issues for which I am in the
nosy list, except in extremely rare cases when I visit an issue for
unrelated reasons (I rarely find myself casually browsing the bug
tracker these days).
I realize that e-mail delivery issues are not necessarily trivial. But
at least I would hope that problems like this don't get completely
ignored. Is there a way to get this sorted out?
Regards
Antoine.
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 <https://docs.python.org/release/3.8.2/whatsnew/changelog.html#python-3-8-2-…>. 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/ <https://www.python.org/downloads/release/python-382/>
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.3 planned for April 2020 (at the PyCon US sprints <https://us.pycon.org/2020/events/sprints/>).
Python 3.9.0a4
An early developer preview of Python 3.9 is also ready:
https://www.python.org/downloads/release/python-390a4/ <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/ <https://www.python.org/psf/>
Your friendly release team,
Ned Deily
Steve Dower
Łukasz Langa
(cross posting to python-committers and python-dev)
I'm happy to announce that the signups for Python Language Summit at PyCon
2020 is now open.
Full details at: https://us.pycon.org/2020/events/languagesummit/
*TL;DR*
When: Wednesday, April 15, 2020, 9am–4pm (Note, we’re starting 1 hour
earlier than usual!)
Where: David L. Lawrence Convention Center, Pittsburgh, PA, room TBD
Sign up to attend: https://forms.gle/Fg7ayhYTaY75J1r7A (closes Feb 29th,
2020 AoE)
Sign up to discuss a topic: https://forms.gle/g4BXezH1Vcn7tLds5 (closes Feb
29th, 2020 AoE)
*Who can attend*
We welcome Python core developers, active core contributors to Python and
alternative Python implementations, and anyone else who has 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
last year’s feedback, our audience prefer more discussions and shorter
talks.
To get an idea of past language summits, you can read past years' coverage:
2019:
http://pyfound.blogspot.com/2019/05/the-2019-python-language-summit.html
2018: https://lwn.net/Articles/754152/
2017: https://lwn.net/Articles/723251/
This year's event will be covered by A. Jesse Jiryu Davis again, and will
be posted on PSF's blog.
<https://us.pycon.org/2020/events/languagesummit/>
Some changes to note this year:
1) We plan to start 1 hour earlier (9AM)
2) The room will have U-shaped table layout
Thanks!
Mariatta & Łukasz
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/ <https://www.python.org/downloads/release/python-382rc2/>
Why a second release candidate?
The major reason for RC2 is that GH-16839 <https://github.com/python/cpython/pull/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 <https://bugs.python.org/issue27657>). 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 <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.2 specifically can be found in its change log <https://docs.python.org/release/3.8.2rc2/whatsnew/changelog.html#python-3-8…>.
We hope you enjoy Python 3.8!
Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation.
https://www.python.org/psf/ <https://www.python.org/psf/>
- Ł
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
Howdy!
I'm trying to get the 3.3 and 3.4 branches so I can check my libraries compatibility with older versions, but I do not see those branches as being available:
$ git branch --remote 89
remotes/upstream/2.7
remotes/upstream/3.5
remotes/upstream/3.6
remotes/upstream/3.7
remotes/upstream/3.8
remotes/upstream/buildbot-custom
remotes/upstream/master
How can I get those?
--
~Ethan~
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/ <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?
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.2 specifically can be found in its change log <https://docs.python.org/release/3.8.2rc1/whatsnew/changelog.html#python-3-8…>.
We hope you enjoy Python 3.8!
Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation.
https://www.python.org/psf/ <https://www.python.org/psf/>
- Ł
The steering council is interested in hearing from *core developers* about
their thoughts around the idea of hiring people to help with the project.
The thinking is if we can pay people to help/assist with the aspects of
development that us volunteers do not enjoy doing or simply lack the time.
This is so we can help maximize our impact as a team of volunteers and
improve Python the best we can. We are also gathering info from folks about
what they (dis)like about the development process at the same time.
The survey can be found at https://forms.gle/p1F9utFiG3PJemaN7. We are
currently restricting this to *only core developers* and one response per
core dev. We would love responses sooner rather than later so we can
analyze the responses in time for PyCon US. Please aim to respond by Feb 15.
