[Python-Dev] Re: GDB not breaking at the right place

On Tue, May 25, 2021 at 7:42 PM Inada Naoki wrote: > On Tue, May 25, 2021 at 5:38 AM Guido van Rossum wrote: > > > > To the contrary, I think if you want the CI jobs to be faster you should > add the CFLAGS to the configure call used to run the CI jobs. > > > > -Og makes it faster not only CI jo

[Python-Dev] Re: PEP 659: Specializing Adaptive Interpreter

On Tue, May 25, 2021 at 7:56 PM Brett Cannon wrote: > > On Tue., May 25, 2021, 12:58 Guido van Rossum, wrote: > >> [...] >> Or do you think the "Standards Track" PEP should just codify general >> agreement that we're going to implement a specializing adaptive >> interpreter, with the level of de

[Python-Dev] Re: GDB not breaking at the right place

On Tue, May 25, 2021 at 7:49 PM Inada Naoki wrote: > On Tue, May 25, 2021 at 5:38 AM Guido van Rossum wrote: > > > > To the contrary, I think if you want the CI jobs to be faster you should > add the CFLAGS to the configure call used to run the CI jobs. > > > > -Og makes it faster not only CI jo

[Python-Dev] Re: PEP 659: Specializing Adaptive Interpreter

On Tue., May 25, 2021, 12:58 Guido van Rossum, wrote: > On Tue, May 25, 2021 at 12:34 PM Brett Cannon wrote: > >> >> I personally think it should be a Standards Track PEP. This PEP isn't >> documenting some detail like PEP 13 or some release schedule, but is >> instead proposing a rather major c

[Python-Dev] Re: GDB not breaking at the right place

On Tue, May 25, 2021 at 5:38 AM Guido van Rossum wrote: > > To the contrary, I think if you want the CI jobs to be faster you should add > the CFLAGS to the configure call used to run the CI jobs. > -Og makes it faster not only CI jobs, but also everyday "edit code and run `make test` with all a

[Python-Dev] Re: Difficulty of testing beta releases now available

> - Cython doesn't work because of _PyGen_Send change [1] I think this is fixed on the latest cython (0.29.23) On Wed, 26 May 2021 at 01:05, Neil Schemenauer wrote: > On 2021-05-04, Łukasz Langa wrote: > > We strongly encourage maintainers of third-party Python projects > > to test with 3.10 d

[Python-Dev] Difficulty of testing beta releases now available

On 2021-05-04, Łukasz Langa wrote: > 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 as soon as > possible. Testing with Python 3.10b1 is not easy, at least for

[Python-Dev] Re: PEP 659: Specializing Adaptive Interpreter

To potentially help provide a little bit of additional detail around our approach I've spent some time writing up our internal details of the shadow byte code implementation, and landed that in our Cinder repo here: https://github.com/facebookincubator/cinder/blob/cinder/3.8/CinderDoc/shadowcode.rs

[Python-Dev] Re: PEP 659: Specializing Adaptive Interpreter

On Tue, May 25, 2021 at 1:50 PM Łukasz Langa wrote: > > On 25 May 2021, at 21:57, Guido van Rossum wrote: > > On Tue, May 25, 2021 at 12:34 PM Brett Cannon wrote: > >> >> I personally think it should be a Standards Track PEP. This PEP isn't >> documenting some detail like PEP 13 or some release

[Python-Dev] Re: PEP 659: Specializing Adaptive Interpreter

> On 25 May 2021, at 21:57, Guido van Rossum wrote: > > On Tue, May 25, 2021 at 12:34 PM Brett Cannon > wrote: > > I personally think it should be a Standards Track PEP. This PEP isn't > documenting some detail like PEP 13 or some release schedule, but is instead > p

[Python-Dev] Re: PEP 659: Specializing Adaptive Interpreter

On Tue, May 25, 2021 at 12:34 PM Brett Cannon wrote: > > I personally think it should be a Standards Track PEP. This PEP isn't > documenting some detail like PEP 13 or some release schedule, but is > instead proposing a rather major change to the interpreter which a lot of > us will need to under

[Python-Dev] Re: python-iterators mailing list on SourceForge

Hi, Le 5/25/21 à 9:18 PM, Brett Cannon a écrit : > Is there something to do here? The python-iterators mailing list is > already marked as public. Looks like Guido is faster than you and set it public already. But looks like the archives are corrupted or something, it's almost empty. I sent a ma

[Python-Dev] Re: python-iterators mailing list on SourceForge

Sorry, that was me. :-) On Tue, May 25, 2021 at 12:24 PM Brett Cannon wrote: > > > On Fri, May 21, 2021 at 9:25 AM Julien Palard via Python-Dev < > python-dev@python.org> wrote: > >> Le 5/11/21 à 8:39 PM, Guido van Rossum a écrit : >> > I doubt that anyone has the keys to the python project on s

[Python-Dev] Re: PEP 659: Specializing Adaptive Interpreter

On Thu, May 13, 2021 at 1:38 AM Mark Shannon wrote: > Hi Terry, > > On 13/05/2021 8:20 am, Terry Reedy wrote: > > On 5/12/2021 1:40 PM, Mark Shannon wrote: > > > >> This is an informational PEP about a key part of our plan to improve > >> CPython performance for 3.11 and beyond. > > > > What is t

[Python-Dev] Re: The repr of a sentinel

To add to the suggestions already given in this thread I dug into code I wrote some time ago. Offered as an inspiration. === missing.py === from typing import Any def MISSING(klass: Any) -> Any: """ create a sentinel to indicate a missing instance of a class :param klass: the class

[Python-Dev] Re: GDB not breaking at the right place

On 5/24/2021 9:38 PM, Guido van Rossum wrote: To the contrary, I think if you want the CI jobs to be faster you should add the CFLAGS to the configure call used to run the CI jobs. Big +1 We should have the most useful interactive development/debugging options set by default (or with an obvio

[Python-Dev] Re: python-iterators mailing list on SourceForge

On Fri, May 21, 2021 at 9:25 AM Julien Palard via Python-Dev < python-dev@python.org> wrote: > Le 5/11/21 à 8:39 PM, Guido van Rossum a écrit : > > I doubt that anyone has the keys to the python project on sourceforge > > any more... :-( We've abandoned that platform nearly two decades ago. > > T

[Python-Dev] Re: The repr of a sentinel

On Tue, May 25, 2021 at 1:08 PM Pascal Chambon wrote: > I feel like the 3-lines declaration of a new sentinel would discourage a > bit its adoption compared to just "sentinel = object()" How about one line? class Missing(Sentinel): pass And avoiding a lot of complications? https://github.com/f

[Python-Dev] Re: GDB not breaking at the right place

me> I'm having a hard time debugging some virtual machine code because GDB won't break where it's supposed to. Here's a quick follow-up. I tried a number of different values of OPT during configuration and compilation, but nothing changed the result. I could never (and still can't) get GDB to brea

[Python-Dev] Re: The repr of a sentinel

Hello, and thanks for the PEP, I feel like the 3-lines declaration of a new sentinel would discourage a bit its adoption compared to just "sentinel = object()" From what I understand from the PEP, if new classes are defined inside the closure of a factory function, some Python implementations w

[Python-Dev] Re: Implementing async enumerate

Hi, I suggest to put such function in a Python module and publish it on PyPI. I'm sure that the module will quickly grow with more async flavor of existing functions. Victor On Tue, May 25, 2021 at 4:22 AM Filipe Alves Caixeta wrote: > > Hello, > > Python 3.10 comes with the built-in anext() bu

[Python-Dev] Re: [python-committers] IMPORTANT: Python 3.10b2 release blockers

On 25/05/2021 00.45, Pablo Galindo Salgado wrote: > Hi, > > Tomorrow is the scheduled release of Python 3.10 beta 2 but > unfortunately we have several release blockers: > > https://bugs.python.org/issue44043 : > 3.10 b1 armhf Bus Error in hashlib test: test_gil