[Python-Dev] [RELEASE] The cursed fourth Python 3.11 beta (3.11.0b4) is available

2022-07-11 Thread Pablo Galindo Salgado
I cannot believe I am writing this, but Python 3.11.b4 is finally
available!! [image: :scream:] [image: :tada:] [image: :tada:] [image:
:tada:]

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

##[image: :warning:][image: :warning:][image: :warning:] PLEASE HELP US TO
TEST THIS RELEASE [image: :warning:][image: :warning:][image: :warning:]

Due to the modified release schedule and the stability concerns regarding
the past beta releases, please, please, please, please, help us to test
Python 3.11 by testing this beta releases.

* if you maintain a library or a third-party package. Test the beta
releases!
* If you have code that you maintain at work/research
centre/classroom/whatever. Test the beta releases!
* If you are a multi-million corporation that uses Python. Test the beta
releases!
* If you are a single-person company that uses Python. Test the beta
releases!
* If you have a bunch of Python scripts. Test the beta releases!
* If you use Python for work, research, teaching or literally for anything.
Test the beta releases!
* If you ...

In summary: no matter who you are or what you do. Test the beta releases!

Is **very** important for us that we identify all possible things that may
break your code **before** the final release is done and we can only do
this if you help us by testing the beta releases and then report anything
that doesn't work!

## Credit where credit is due [image: :pray:]

Lots of thanks to Christian Heimes, Brandt Bucher, Irit Katriel, Mark
Shannon, Dennis Sweeney, Kumar Aditya and other contributors (sorry if I am
missing any names) that worked really hard against time to help me and the
release team with the release blockers. They are all awesome and we and the
Python community are very lucky to have them in the team [image: :heart:]

## What happens with the next betas?

As stated in [my previous communication](
https://mail.python.org/archives/list/python-dev@python.org/thread/3JWVCSBPBFWY5ZWSJ7RYB6FS5NIMCEOY/)
we are in a special situation regarding beta releases. As the requirements
to continue with the regular schedule are met, we are going to still target
the final release of Monday, 2022-10-03.

Python 3.11.0b5 was supposed to be released two days ago, so we are
obviously delayed. As we are targeting the regular release schedule, I'm
going to try to release 3.11.0b5 on Thursday, 2022-07-25.

## This is a beta preview of Python  3.11

Python 3.11 is still in development. 3.11.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.

We **strongly encourage** maintainers of third-party Python projects to
**test with 3.11** during the beta phase and report issues found to [the
Python bug tracker](https://github.com/python/cpython/issues) 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 5 and as few code
changes as possible after 3.11.0rc1, the first release candidate.  To
achieve that, it will be **extremely important** to get as much exposure
for 3.11 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.11 series, compared to 3.10

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

## General changes

* [PEP 657](https://www.python.org/dev/peps/pep-0657/) -- Include
Fine-Grained Error Locations in Tracebacks
* [PEP 654](https://www.python.org/dev/peps/pep-0654/) -- Exception Groups
and except*
* [PEP 680](https://www.python.org/dev/peps/pep-0680/)-- tomllib: Support
for Parsing TOML in the Standard Library
* [PEP 681](https://www.python.org/dev/peps/pep-0681/)-- Data Class
Transforms
* [bpo-46752](https://bugs.python.org/issue46752)-- Introduce task groups
to asyncio
* [bpo-433030](https://github.com/python/cpython/issues/34627/) -- Atomic
grouping ((?>...)) and possessive quantifiers (`*+, ++, ?+, {m,n}+`) are
now supported in regular expressions.
* The [Faster Cpython Project](https://github.com/faster-cpython/) is
already yielding some exciting results. Python 3.11 is up to 10-60% faster
than Python 3.10. On average, we measured a 1.22x speedup on the standard
benchmark suite. See [Faster CPython](
https://docs.python.org/3.11/whatsnew/3.11.html#faster-cpython) for details.

## Typing and typing language changes

* [PEP 673](https://www.python.org/dev/peps/pep-0673/)  -- Self Type
* [PEP 646](https://www.python.org/dev/peps/pep-0646/)-- Variadic Generics
* [PEP 675](https://www.python.org/dev/peps/pep-0675/)-- Arbitrary Literal
String Type
* [PEP 655](https://www.python.org/dev/peps/pep-0655/)-- Marking individ

[Python-Dev] Re: [RELEASE] The cursed fourth Python 3.11 beta (3.11.0b4) is available

2022-07-11 Thread Pablo Galindo Salgado
BSD-style checksum format hashes for the release artefacts:

SHA256 (python-3.11.0b4-embed-arm64.zip) =
272c6bb4948c597f6578f64c2b15a70466c5dfb49f9b84dba57a84e59e7bd4ef
SHA256 (python-3.11.0b4-amd64.exe) =
a3514b0401e6a85416f3e080586c86ccd9e2e62c8a54b9119d9e6415e3cadb62
SHA256 (python-3.11.0b4-macos11.pkg) =
860647775d4e6cd1a8d71412233df5dbe3aa2886fc16d82a59ab2f625464f2d7
SHA256 (python-3.11.0b4-embed-win32.zip) =
36b81da7986f8d59be61adb452681dbd3257ebb90bd89092b2fbbd9356e06425
SHA256 (python-3.11.0b4-arm64.exe) =
ad0d1429682ba1edc0c0cf87f68a3d1319b887b715da70a91db41d02be4997a4
SHA256 (python-3.11.0b4-embed-amd64.zip) =
66e6bb44c36da36ecc1de64efdb92f52ba3a19221dba2a89e22e39f715bd205b
SHA256 (Python-3.11.0b4.tar.xz) =
1d93b611607903e080417c1a9567f5fbbf5124cc5c86f4afbba1c8fd34c5f6fb
SHA256 (python-3.11.0b4.exe) =
6febc152711840337f53e2fd5dc12bb2b1314766f591129282fd372c855fa877
SHA256 (Python-3.11.0b4.tgz) =
257e753db2294794fa8dec072c228f3f53fd541a303de9418854b3c2512ccbec
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/NOBNKLWKMJAHGLV6GVNITUBJ7OFJLIXY/
Code of Conduct: http://python.org/psf/codeofconduct/


[Python-Dev] Presenting PEP 695: Type Parameter Syntax

2022-07-11 Thread Guido van Rossum
After several rounds of debate on typing-sig, I'd like to request feedback
on PEP 695: https://peps.python.org/pep-0695/

I am sponsoring this PEP, which was written by Eric Traut. The PEP attempts
to solve the problem that defining generic classes, functions and type
aliases currently is lacking dedicated syntax, instead using the cumbersome
`T = TypeVar("T", ...)` notation to create global variables that serve as
type variables.

As a personal historical note, I should mention that over 22 years ago I
already pondered type parameters. In an old document that I saved I found
the following code snippet:
```
def f (a: T) -> T: ...
```
which is eerily close to the proposal in this PEP, except that the PEP uses
square brackets:
```
def f[T](a: T) -> T: ...
```
It's been a long and circuitous road!

I am not quoting the entire PEP here, please follow the link:
https://peps.python.org/pep-0695/

-- 
--Guido van Rossum (python.org/~guido)
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/65KXYQOKHMZBGBHWKU6DRGOTN6PTZHFP/
Code of Conduct: http://python.org/psf/codeofconduct/


[Python-Dev] Re: 3.11 enhanced error location - can it be smarter?

2022-07-11 Thread John Belmonte
On 1/18/22 10:43 AM, Mats Wichmann wrote:

> A thought - how about omitting the underline line if the
> to-be-underlined part would be the whole line?

I wasn't aware of this thread, but that's exactly what I implemented for
3.11.0b4.

About this thread-- I understand debating solutions, but there was at least
an agreement here about the problem.  For visibility, it would have been
better to open an issue than let the topic drop.  (When filing the issue, I
was wondering "how can I be alone thinking this is a problem?"-- then was
surprised to see the support come out for the change.)

Regards,
--John
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/QPBESYL43T2ZVWLM7JI4UQD7VEGL3A55/
Code of Conduct: http://python.org/psf/codeofconduct/