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

On 21. 05. 21 3:23, Eric V. Smith wrote: On 5/20/2021 3:24 PM, Ronald Oussoren via Python-Dev wrote: On 20 May 2021, at 19:10, Luciano Ramalho > wrote: I'd like to learn about use cases where `...` (a.k.a. `Ellipsis`) is not a good sentinel. It's a pickable

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

Christopher Barker writes: > I find this whole conversation confusing -- does anyone really think a > substantial performance boost to cPython is not a "good thing"? > [PyPy, Numba, Cython] are why Python is very useful today -- but > none of them make the case that making cPython run faster

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

I was attracted to Python in 1998 because it seemed designed to make the simple cases simple, and the hard cases possible. My personal takeaway from this discussion: I will continue to advocate for the use of Ellipsis as a sentinel in the *many* cases where it is suitable. For the hard cases, I

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

On 5/21/2021 9:36 AM, Petr Viktorin wrote: On 21. 05. 21 3:23, Eric V. Smith wrote: On 5/20/2021 3:24 PM, Ronald Oussoren via Python-Dev wrote: One example of this is the definition of dataclasses.field: |dataclasses.||field|(/*/, /default=MISSING/, /default_factory=MISSING/, /repr=True/,

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

I suspect that you're running into the issue where compiler optimizations are *forced* on for ceval.c. There's a comment near the top about this. Just comment out this line: #define PY_LOCAL_AGGRESSIVE We tried to define that macro conditionally, but something broke because the C stack frame

[Python-Dev] Summary of Python tracker Issues

ACTIVITY SUMMARY (2021-05-14 - 2021-05-21) Python tracker at https://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open7452 (+23) closed 48492 (+51) total 55944 (+74) Open issues

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

On Fri, May 21, 2021 at 2:48 PM Guido van Rossum wrote: > I suspect that you're running into the issue where compiler optimizations > are *forced* on for ceval.c. > > There's a comment near the top about this. Just comment out this line: > > #define PY_LOCAL_AGGRESSIVE > > We tried to define

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

Huh, you're right, I forgot that Py_LOCAL_AGGRESSIVE is specific to MSVC (maybe it wasn't always). I can think of nothing else apart from a gcc or gdb bug. Oh, hm, maybe computed gotos play havoc with the labels??? On Fri, May 21, 2021 at 2:01 PM Skip Montanaro wrote: > > > On Fri, May 21,

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

I'm having a hard time debugging some virtual machine code because GDB won't break where it's supposed to. Here's my breakpoint #2: 2 breakpoint keep y 0x556914fd ceval_reg.h:_PyEval_EvalFrameDefault:TARGET_JUMP_IF_FALSE_REG breakpoint already hit 1 time p/x oparg

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

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. That's right… Sourceforge staff mentionned there's the list of current admins here: =>