Re: [Python-Dev] RFC: PEP 587 "Python Initialization Configuration": 3rd version

On 5/20/2019 4:09 AM, Victor Stinner wrote: > Hi Gregory, > > IMHO your remarks are not directly related to the PEP 587 and can be > addressed in parallel. > >> It sounds like PyOxidizer and Hermetic Python are on the same page and >> we're working towards a more official solution. But I want to

Re: [Python-Dev] Expected stability of PyCode_New() and types.CodeType() signatures

On Sat, Jun 1, 2019 at 12:29 AM Terry Reedy wrote: > We try not to. There is already too much work. > ... > That was removed from the PR before it was merged. > ... > That was merged. > ... > Another chunk was added to What's New. > Woot to all of these! :) _

Re: [Python-Dev] Expected stability of PyCode_New() and types.CodeType() signatures

On 5/31/2019 5:28 PM, Simon Cross wrote: As the maintainer of Genshi, one the libraries affected by the CodeType and similar changes, I thought I could add a users perspective to the discussion: Genshi is a templating engine that parses Python code from inside its templates. It supports Pytho

Re: [Python-Dev] PEP 590: vectorcall without tp_call

On 29May2019 1311, Petr Viktorin wrote: On 5/29/19 3:36 PM, Jeroen Demeyer wrote: On 2019-05-29 15:29, Petr Viktorin wrote: That sounds like a good idea for PyType_FromSpec. I don't think we're planning to support vectorcall in PyType_FromSpec for now. That's maybe for 3.9 when vectorcall is

Re: [Python-Dev] Expected stability of PyCode_New() and types.CodeType() signatures

As the maintainer of Genshi, one the libraries affected by the CodeType and similar changes, I thought I could add a users perspective to the discussion: Genshi is a templating engine that parses Python code from inside its templates. It supports Python 2.6+, 3.2+, pypy2 and pypy3. It parses Pytho

Re: [Python-Dev] Have a big machine and spare time? Here's a possible Python bug.

On Fri, May 31, 2019 at 11:12 AM Tim Peters wrote: > [Tim] > >> I'm keen to get feedback on this before merging the PR, because this > >> case is so very much larger than anything I've ever tried that I'm > >> wary that there may be more than one "surprise" lurking here. ... > > [Inada Naoki ] >

Re: [Python-Dev] PEP 595: Improving bugs.python.org

Nathaniel Smith wrote: On Fri, May 31, 2019 at 11:39 AM Barry Warsaw wrote: On May 31, 2019, at 01:22, Antoine Pitrou wrote: I second this. There are currently ~7000 bugs open on bugs.python.org.  The Web UI makes a good job of actually being able to navigate through these bugs, searc

Re: [Python-Dev] PEP 595: Improving bugs.python.org

On Fri, May 31, 2019 at 11:39 AM Barry Warsaw wrote: > > On May 31, 2019, at 01:22, Antoine Pitrou wrote: > > > I second this. > > > > There are currently ~7000 bugs open on bugs.python.org. The Web UI > > makes a good job of actually being able to navigate through these bugs, > > search through

Re: [Python-Dev] PEP 595: Improving bugs.python.org

On May 31, 2019, at 01:22, Antoine Pitrou wrote: > I second this. > > There are currently ~7000 bugs open on bugs.python.org. The Web UI > makes a good job of actually being able to navigate through these bugs, > search through them, etc. > > Did the Steering Council conduct a usability study

Re: [Python-Dev] PEP 595: Improving bugs.python.org

On Fri, May 31, 2019 at 1:23 AM Antoine Pitrou wrote: > > I second this. > > There are currently ~7000 bugs open on bugs.python.org. The Web UI > makes a good job of actually being able to navigate through these bugs, > search through them, etc. > > Did the Steering Council conduct a usability s

Re: [Python-Dev] Have a big machine and spare time? Here's a possible Python bug.

[Tim] >> I'm keen to get feedback on this before merging the PR, because this >> case is so very much larger than anything I've ever tried that I'm >> wary that there may be more than one "surprise" lurking here. ... [Inada Naoki ] > I started r5a.4xlarge EC2 instance and started arena.py. > I wil

[Python-Dev] Summary of Python tracker Issues

ACTIVITY SUMMARY (2019-05-24 - 2019-05-31) 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: open7028 (-39) closed 41839 (+118) total 48867 (+79) Open issues w

Re: [Python-Dev] Should I postpone PEP 558 (locals() semantics) to Python 3.9?

On 5/31/2019 6:20 AM, Nick Coghlan wrote: On Fri., 31 May 2019, 6:34 pm Nathaniel Smith, > wrote: I wouldn't mind having a little more breathing room. It's frustrating to miss the train, but these bugs are several decades old so I guess nothing terrible will ha

Re: [Python-Dev] Expected stability of PyCode_New() and types.CodeType() signatures

On 5/31/2019 4:46 AM, Petr Viktorin wrote: Hello, PEP 570 (Positional-Only Parameters) changed the signatures of PyCode_New() and types.CodeType(), adding a new argument for "posargcount". Our policy for such changes seems to be fragmented tribal knowledge. I'm writing to check if my understand

Re: [Python-Dev] Should I postpone PEP 558 (locals() semantics) to Python 3.9?

On Fri., 31 May 2019, 6:34 pm Nathaniel Smith, wrote: > I wouldn't mind having a little more breathing room. It's frustrating > to miss the train, but these bugs are several decades old so I guess > nothing terrible will happen if their fixes get delayed to 3.9. > And I could put that extra time

Re: [Python-Dev] Have a big machine and spare time? Here's a possible Python bug.

> I'm keen to get feedback on this before merging the PR, because this > case is so very much larger than anything I've ever tried that I'm > wary that there may be more than one "surprise" lurking here. The PR > certainly addresses "an obvious" (with hindsight) problem - but is > that the _only_

[Python-Dev] Expected stability of PyCode_New() and types.CodeType() signatures

Hello, PEP 570 (Positional-Only Parameters) changed the signatures of PyCode_New() and types.CodeType(), adding a new argument for "posargcount". Our policy for such changes seems to be fragmented tribal knowledge. I'm writing to check if my understanding is reasonable, so I can apply it and do

Re: [Python-Dev] Should I postpone PEP 558 (locals() semantics) to Python 3.9?

I wouldn't mind having a little more breathing room. It's frustrating to miss the train, but these bugs are several decades old so I guess nothing terrible will happen if their fixes get delayed to 3.9. On Thu, May 30, 2019 at 4:23 PM Nick Coghlan wrote: > > Hi folks, > > The reference implementa

Re: [Python-Dev] PEP 595: Improving bugs.python.org

I second this. There are currently ~7000 bugs open on bugs.python.org. The Web UI makes a good job of actually being able to navigate through these bugs, search through them, etc. Did the Steering Council conduct a usability study of Github Issues with those ~7000 bugs open? If not, then I th