Hi everyone,
A small update since the last communication from the release team regarding
the status of Python 3.11.0b4.
Unfortunately, even if we have fixed most of the original release blockers
and 4 more that appear during this week, we still have a bunch of release
blockers to deal with. One of them has been reported today.
I would like to release the next beta next week if everything looks good,
but there are also some items that need discussion:.
https://github.com/python/cpython/issues/93910https://github.com/python/cpython/issues/93516
Ideally we should reach consensus as a team on how to proceed in these
issues. In particular, we should decide collectively what is an acceptable
slowdown, specially looking to the release candidate.
If releasing the next betas is further delayed, I will consider delaying
the full release schedule to accommodate for the delay so users have the
appropriate time to test and validate every release.
Please do not hesitate in reaching out if you have any questions or
concerns or if there is any issue you think we should include in the next
release.
Thanks everyone for your help and understanding. I'm sure 3.11 is going to
be an outstanding release thank to all of you :)
Cheers from cloudy London,
Pablo Galindo Salgado
Hi everyone,
Today we are supposed to release Python3.11.0b4 but unfortunately, we have
a bunch of release blockers:
https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+label%3Arel…
Please, if you are involved in the above issues check if they are resolved
or if they are not released blockers. If they are
not release blockers or you think we should defer them, please comment on
why on the issue. Also, please, notice that
the final decision to defer or not a blocker is made by the release
management team.
If you have some time to investigate, that will help a lot!
Please, add me as a reviewer to any PR that needs to be merged to address
these issues.
Thanks for your help!
Regards from sunny London,
Pablo Galindo Salgado
I brought this up on python-dev at
https://mail.python.org/archives/list/python-dev@python.org/thread/ZPBSHENP…
, and the feedback seemed supportive. As such, I am bringing a draft of
what I'm thinking will go into PEP 11 with a bunch of `XXX` placeholders
for people to help me fill in to see how this will look overall.
For any platform(s) you support, please reply with any relevant details
that should be added to the relevant tables below. Once I have these
details I will loop back with the proposed update to PEP 11 and make sure
everyone is still on board with the proposal.
=====
Tiers
=====
Tier 1
======
- `Test suite failures <
https://github.com/python/cpython/actions/workflows/build.yml?query=branch%…>`__
block releases.
- Changes which would break the ``main`` branch are not allowed to be
merged;
any breakage may be reverted immediately.
- All core developers are responsible to keep these platforms working.
- Promotion of this tier requires consensus/SC approval.
=================== =====
Target Triple Notes
=================== =====
i686-windows-msvc
x86_64-windows-msvc
x86_64-apple-darwin macOS 11
x86_64-linux-gnu glibc 2.31 |ubuntu-20_01|_
=================== =====
.. [ubuntu-20_01] https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.4
Tier 2
======
- Must have a stable buildbot.
- At least **two** core developers are signed up to support the platform.
- Changes which break any of these platforms are to be reverted within 24
hours.
- Failures of these platforms block a release.
- Promotion of this tier requires consensus/SC approval.
====================== ==========================
============================================== ========
Target Triple Notes Buildbot
Contacts
====================== ==========================
============================================== ========
aarch64-apple-darwin XXX
https://buildbot.python.org/all/#/builders/725 XXX
aarch64-linux-gnu glibc XXX [fedora-stable]_
https://buildbot.python.org/all/#/builders/125 XXX
glibc 2.28 [RHEL8]_
https://buildbot.python.org/all/#/builders/529 XXX
aarch64-windows-msvc XXX
https://buildbot.python.org/all/#/builders/729 XXX
powerpc64-linux-gnu glibc XXX
https://buildbot.python.org/all/#/builders/237 XXX
powerpcle-linux-gnu glibc XXX
https://buildbot.python.org/all/#/builders/90 XXX
s309x-linux-gnu glibc XXX
https://buildbot.python.org/all/#/builders/223 XXX
glibc 2.28 [RHEL8]_
https://buildbot.python.org/all/#/builders/509 XXX
glibc 2.17 [RHEL7]_
https://buildbot.python.org/all/#/builders/179 XXX
x86_64-linux-gnu glibc 2.17 [RHEL7]_
https://buildbot.python.org/all/#/builders/15 XXX
x86_64-unknown-freebsd XXX
https://buildbot.python.org/all/#/builders/172 XXX
====================== ==========================
============================================== ========
.. [fedora-stable] XXX
.. [RHEL8] https://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux#RHEL_8
.. [RHEL7]
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/ht…
Tier 3
======
- Must have a stable buildbot.
- Code may be checked into ``main`` for the platform.
- At least **one** core developer is signed up to support the platform.
- Test failures do **not** block releases.
- Promotion to this tier is self-service.
========================= ==========================
============================================== ========
Target Triple Notes Buildbot
Contacts
========================= ==========================
============================================== ========
wasm32-unknown-emscripten XXX XXX
Brett Cannon, Christian Heimes
wasm32-unknown-wasi XXX XXX
Brett Cannon, Christian Heimes
========================= ==========================
============================================== ========
All other platforms
===================
- Only code which either supports a higher-tier platform or is a general
improvement may be checked in.
The latest bugfix drop for Python 3.10 is here: Python 3.10.5. This release
packs more than 230 bugfixes and docs changes, so you surely want to update
:) You can get it here:
https://www.python.org/downloads/release/python-3105/
## This is the fourth maintenance release of Python 3.10
Python 3.10.5 is the newest major release of the Python programming
language, and it contains many new features and optimizations.
# Major new features of the 3.10 series, compared to 3.9
Among the new major new features and changes so far:
* [PEP 623](https://www.python.org/dev/peps/pep-0623/) -- Deprecate and
prepare for the removal of the wstr member in PyUnicodeObject.
* [PEP 604](https://www.python.org/dev/peps/pep-0604/) -- Allow writing
union types as X | Y
* [PEP 612](https://www.python.org/dev/peps/pep-0612/) -- Parameter
Specification Variables
* [PEP 626](https://www.python.org/dev/peps/pep-0626/) -- Precise line
numbers for debugging and other tools.
* [PEP 618 ](https://www.python.org/dev/peps/pep-0618/) -- Add Optional
Length-Checking To zip.
* [bpo-12782](https://bugs.python.org/issue12782): Parenthesized context
managers are now officially allowed.
* [PEP 632 ](https://www.python.org/dev/peps/pep-0632/) -- Deprecate
distutils module.
* [PEP 613 ](https://www.python.org/dev/peps/pep-0613/) -- Explicit Type
Aliases
* [PEP 634 ](https://www.python.org/dev/peps/pep-0634/) -- Structural
Pattern Matching: Specification
* [PEP 635 ](https://www.python.org/dev/peps/pep-0635/) -- Structural
Pattern Matching: Motivation and Rationale
* [PEP 636 ](https://www.python.org/dev/peps/pep-0636/) -- Structural
Pattern Matching: Tutorial
* [PEP 644 ](https://www.python.org/dev/peps/pep-0644/) -- Require OpenSSL
1.1.1 or newer
* [PEP 624 ](https://www.python.org/dev/peps/pep-0624/) -- Remove
Py_UNICODE encoder APIs
* [PEP 597 ](https://www.python.org/dev/peps/pep-0597/) -- Add optional
EncodingWarning
[bpo-38605](https://bugs.python.org/issue38605): `from __future__ import
annotations` ([PEP 563](https://www.python.org/dev/peps/pep-0563/)) used to
be on this list
in previous pre-releases but it has been postponed to Python 3.11 due to
some compatibility concerns. You can read the Steering Council
communication about it [here](
https://mail.python.org/archives/list/python-dev@python.org/thread/CLVXXPQ2…)
to learn more.
# More resources
* [Changelog](https://docs.python.org/3.10/whatsnew/changelog.html#changelog
)
* [Online Documentation](https://docs.python.org/3.10/)
* [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](/psf/donations/).
# And now for something completely different
Strange quarks are the third lightest quarks, which are subatomic particles
that are so small, they are believed to be the fundamental particles, and
not further divisible. Like down quarks, strange quarks have a charge of
-1/3. Like all fermions (which are particles that can not exist in the same
place at the same time), strange quarks have a spin of 1/2. What makes
strange quarks different from down quarks–apart from having 25 times the
mass of down quarks–is that they have something that scientists call
"strangeness." Strangeness is basically a resistance to decay against
strong force and electromagnetism. This means that any particle that
contains a strange quark can not decay due to strong force (or
electromagnetism), but instead with the much slower weak force. It was
believed that this was a 'strange' method of decay, which is why the
scientists gave the particles that name.
# 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/
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
Hi everyone, the typing community is considering a proposal to add new
syntax to support generic types. This is likely to be a big change, so we'd
love for any interested core developers to join the discussion early on so
we can get alignment faster.
We'll have a video call next Wednesday to discuss the proposal; any core
devs (or other interested readers) are welcome to join. (Even if your
opinion is "we shouldn't ever do this"—that would be important feedback.)
The proposal is still in its early stages, but it would look something like:
class list[T]:
def append(self, obj: T, /) -> None: ...
def __getitem__(self, i: int, /) -> T: ...
Replacing the current syntax:
from typing import Generic, TypeVar
T = TypeVar("T")
class list(Generic[T]):
def append(self, obj: T, /) -> None: ...
def __getitem__(self, i: int, /) -> T: ...
This is just by way of introduction; I don't want to start a discussion on
this list. If you do want to contribute to the discussion but can't join
the meeting, please reply to the mailing list thread
https://mail.python.org/archives/list/typing-sig@python.org/thread/GPQO2F4N…
.
---------- Forwarded message ---------
De: S Pradeep Kumar <gohanpra(a)gmail.com>
Date: mar, 24 may 2022 a las 18:22
Subject: [Typing-sig] Re: Typing Meetup
To:
Cc: None via Typing-sig <typing-sig(a)python.org>
*Update*: I'm moving the meetup to* Wednesday, June 1, 11:00 am San
Francisco time (UTC-7)* / 7:00 pm London time (UTC+1).
(The main reason for the change is that I want to invite some core dev
folks outside of typing-sig, since we'll be discussing a syntax change. I
don't want a repeat of Callable syntax :| )
*Agenda*:
Syntax for TypeVars, by Sebastian Rittau
Zoom link: https://us02web.zoom.us/j/84291194582. The meeting will be
automatically recorded from the time it starts.
I'll share the recording and notes after the meetup. [1]
--
S Pradeep Kumar
[1]: Meeting recording and notes:
https://docs.google.com/document/d/17iqV7WWvB0IwA43EPlIqlUS6Xuvk08X3sEudAA-…
_______________________________________________
Typing-sig mailing list -- typing-sig(a)python.org
To unsubscribe send an email to typing-sig-leave(a)python.org
https://mail.python.org/mailman3/lists/typing-sig.python.org/
Member address: jelle.zijlstra(a)gmail.com
Hi everyone,
Due to a known incompatibility with pytest and the previous beta release
(Python 3.11.0b2) and after
some deliberation, me and the rest of the release team have decided to do
an expedited release of
Python 3.11.0b3 so the community can continue testing their packages with
pytest and therefore
testing the betas as expected.
# Where can I get the new release?
https://www.python.org/downloads/release/python-3110b3/
# What happened?
Pytest by default rewrites the AST nodes in the testing code to provide
better diagnostics when something
fails in the test. For doing this, it creates new AST nodes that are then
compiled. In Python 3.11, after some
changes in the compiler and AST nodes, these new AST nodes that pytest was
creating were invalid. This causes
CPython to crash in debug mode because we have several assert statements in
the compiler, but in release mode
this doesn't cause always a crash, but it creates potential corrupted
structures in the compiler silently.
In 3.11.0b3 we changed the compiler to reject invalid AST nodes, so what
was a silent problem and a crash in
debug mode turned into an exception being raised. We had a fix to allow the
nodes that pytest is creating to work
to preserve backwards compatibility but unfortunately, it didn't make it
into 3.11.0b2.
Is still possible to use pytest with 3.11.0b2 if you add "--assert=plain"
to the pytest invocation but given how many
users would have to modify their test suite invocation we decided to
proceed with a new release that has the fix.
# What happens with future beta releases
Python 3.11.0b3 should be considered as an extra beta release. Instead of
four beta releases, we will have five and
the next beta release (3.11.0b4) will happen as scheduled on Thursday,
2022-06-16.
# 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/
If you have any questions, please reach out to me or another member of the
release team :)
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