[Python-Dev] Re: Worried about Python release schedule and lack of stable C-API

On 05. 10. 21 8:59, Nick Coghlan wrote: On Tue, 28 Sep 2021, 6:55 am Brett Cannon, > wrote: On Sun, Sep 26, 2021 at 3:51 AM Phil Thompson via Python-Dev mailto:python-dev@python.org>> wrote: However the stable ABI is still a second class citizen as

[Python-Dev] Re: Worried about Python release schedule and lack of stable C-API

> What I have heard repeatedly, from people who are paid to know, is that most > users don’t care about the latest features, and would rather stick to a > release until it becomes unsupported. (Extreme example: Python 2.) Just a quick note: Until black supports py3.10 fully, I'm sticking with

[Python-Dev] Re: Worried about Python release schedule and lack of stable C-API

On Tue, 28 Sep 2021, 6:55 am Brett Cannon, wrote: > > > On Sun, Sep 26, 2021 at 3:51 AM Phil Thompson via Python-Dev < > python-dev@python.org> wrote: > >> >> However the stable ABI is still a second class citizen as it is still >> not possible (AFAIK) to specify a wheel name that doesn't need

[Python-Dev] Re: Does ensurepip still have to include a copy of setuptools?

On Mon, 4 Oct 2021, 5:23 pm Antoine Pitrou, wrote: > On Sat, 2 Oct 2021 13:27:03 +0100 > Paul Moore wrote: > > On Sat, 2 Oct 2021 at 12:20, Thomas Grainger wrote: > > > > > > I raised an issue about this: https://github.com/pypa/pip/issues/10530 > > > > > I agree with the comment made on that

[Python-Dev] Re: Worried about Python release schedule and lack of stable C-API

On 05/10/2021 07:59, Nick Coghlan wrote: On Tue, 28 Sep 2021, 6:55 am Brett Cannon, wrote: On Sun, Sep 26, 2021 at 3:51 AM Phil Thompson via Python-Dev < python-dev@python.org> wrote: However the stable ABI is still a second class citizen as it is still not possible (AFAIK) to specify a

[Python-Dev] Re: PEP 654 except* formatting

On Tue, Oct 5, 2021 at 10:51 AM Patrick Reader <_...@pxeger.com> wrote: > On 03/10/2021 16:47, Irit Katriel via Python-Dev wrote: > > 1. except *E as e: // except *(E1, E2) as e: > 2. except* E as e: // except* (E1, E2) as e: > > I vote #2, because `except *(e1, e2) as e:` could imply that

[Python-Dev] Thanks for your work in Python 3.10

Hi everyone, Now that 3.10.0 is finally released I wanted to take the time to thank you all for all your fantastic work this past year. Is because of the sum of all your fantastic work that Python 3.10 is going to be such a fantastic release. No matter if you have been working in fixing bugs,

[Python-Dev] Re: python3.10 compilation on OpenBSD: running into ssl issues

On 05/10/2021 16.40, Sandeep Gupta wrote: Trying to compile python3.10 on openbsd 7.0 on Pi4. It seems to run into several openssl issue.  I have installed openssl as I couldn't find libreSSL in the package manager. Your installation is picking up header files from LibreSSL. Python 3.10

[Python-Dev] Re: Worried about Python release schedule and lack of stable C-API

I think that's unfortunate, you can still use and format the subset of Python 3.10 syntax with black. You already do this on python 3.9 for example black doesn't support parenthesized with ___ Python-Dev mailing list -- python-dev@python.org To

[Python-Dev] Re: PEP 654 except* formatting

On 03/10/2021 16:47, Irit Katriel via Python-Dev wrote: >> 1. except *E as e:  //  except *(E1, E2) as e: >> 2. except* E as e:  //  except* (E1, E2) as e: I vote #2, because `except *(e1, e2) as e:` could imply that this is splatting an arbitrary expression there - it looks like it will match

[Python-Dev] Re: PEP 654 except* formatting

On 03/10/2021 16:54, Thomas Grainger wrote: > What about `except case ExceptionGroup[E1 | E2]:`? and use match semantics? > > On Sun, 3 Oct 2021, 16:50 Irit Katriel via Python-Dev, > wrote: > > > We wonder if people have a view on which of the following is > clearer/better: >> 1. except

[Python-Dev] Re: PEP 654 except* formatting

On 03/10/2021 16:59, Patrick Reader wrote: > On 03/10/2021 16:47, Irit Katriel via Python-Dev wrote: >>> 1. except *E as e:  //  except *(E1, E2) as e: >>> 2. except* E as e:  //  except* (E1, E2) as e: > > I vote #2, because `except *(e1, e2) as e:` could imply that this is > splatting an

[Python-Dev] python3.10 compilation on OpenBSD: running into ssl issues

Trying to compile python3.10 on openbsd 7.0 on Pi4. It seems to run into several openssl issue. I have installed openssl as I couldn't find libreSSL in the package manager. The configure seems to passthe ssl test. configure:17559: checking whether compiling and linking against OpenSSL works

[Python-Dev] Re: PEP 654 except* formatting

I agree that *(E1, E2) looks like unpacking, how about except *E1 as error: ... except (*E1, *E2) as error: ... even better would be if we could drop the braces: except *E1, *E2 as error: ... ___ Python-Dev mailing list -- python-dev@python.org To

[Python-Dev] Re: PEP 654 except* formatting

On Tue, Oct 05, 2021 at 11:17:25AM -0400, Calvin Spealman wrote: > On Tue, Oct 5, 2021 at 10:51 AM Patrick Reader <_...@pxeger.com> wrote: > > > On 03/10/2021 16:47, Irit Katriel via Python-Dev wrote: > > > > 1. except *E as e: // except *(E1, E2) as e: > > 2. except* E as e: // except* (E1,

[Python-Dev] Re: PEP 654 except* formatting

What do the PEP authors think about `except group`? Bikeshedding aside, that’s still the best alternative I’ve seen. It’s unambiguous, self-descriptive, and can’t be confused with unpacking syntax. -Barry > On Oct 5, 2021, at 11:15, sascha.schlemmer--- via Python-Dev > wrote: > > I agree

[Python-Dev] Re: PEP 654 except* formatting

What do the PEP authors think about `except group`? Bikeshedding aside, that’s still the best alternative I’ve seen. It’s unambiguous, self-descriptive, and can’t be confused with unpacking syntax. -Barry > On Oct 5, 2021, at 11:15, sascha.schlemmer--- via Python-Dev > wrote: > > I agree

[Python-Dev] Re: PEP 654 except* formatting

On 2021-10-06 02:12, Barry Warsaw wrote: What do the PEP authors think about `except group`? Bikeshedding aside, that’s still the best alternative I’ve seen. It’s unambiguous, self-descriptive, and can’t be confused with unpacking syntax. +1 ___

[Python-Dev] Re: PEP 654 except* formatting

On 10/5/21 6:32 PM, MRAB wrote: > On 2021-10-06 02:12, Barry Warsaw wrote: >> What do the PEP authors think about `except group`? Bikeshedding aside, that’s still the best alternative I’ve seen. >> It’s unambiguous, self-descriptive, and can’t be confused with unpacking syntax. >> > +1 +1

[Python-Dev] Re: Worried about Python release schedule and lack of stable C-API

Thanks for info, that's becoming a black spot in the tool it seems. It's more for production codes, now I can give it a try! Kind Regards, Abdur-Rahmaan Janhangeer about | blog github

[Python-Dev] Re: Thanks for your work in Python 3.10

Seconding that. I'd also like to add a big thank you to all the contributors for engaging through each release with the downstream Python redistributors as well, hearing us, working with us, helping us shape the future of a big part of the linux (and not only) ecosystem. On Tue, Oct 5, 2021 at

[Python-Dev] Re: PEP 654 except* formatting

On 6/10/21 7:15 am, sascha.schlemmer--- via Python-Dev wrote: except (*E1, *E2) as error: ... Then we would have to decide whether to allow except (E1, *E2) as error: ... and if so, what it would mean. -- Greg ___ Python-Dev mailing list --

[Python-Dev] Re: Thanks for your work in Python 3.10

Thank you for managing the release, Pablo! And for the awesome astrophysics snippets. :D ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org