[Python-Dev] Re: Roundup to GitHub Issues migration

On 6/21/2021 2:31 PM, Christopher Barker wrote: By contrast, requiring a github account for reporting bugs also makes python an unwelcoming place for non-developers in general. Github is a developers' social network, "mere" users are much less likely to want to be part of it.

[Python-Dev] Re: Roundup to GitHub Issues migration

> By contrast, requiring a github account for reporting bugs also makes > python an unwelcoming place for non-developers in general. Github is a > developers' social network, "mere" users are much less likely to want to > be part of it. Many will just silently abandon their bug report. But you do

[Python-Dev] Re: Making PY_SSIZE_T_CLEAN not mandatory.

Okay, I think your evidence can then be discounted. Really, any app that relies on the publicly installed Python runs a serious risk of breaking when that Python gets updated, regardless of whether the ABI changes or not. On Mon, Jun 21, 2021 at 2:46 AM Baptiste Carvello < devel2...@baptiste-carve

[Python-Dev] Re: Roundup to GitHub Issues migration

Baptiste Carvello writes: > By contrast, requiring a github account for reporting bugs also makes > python an unwelcoming place for non-developers in general. Github is a > developers' social network, "mere" users are much less likely to want to > be part of it. Many will just silently abandon th

[Python-Dev] Re: Roundup to GitHub Issues migration

Hi, Le 21/06/2021 à 13:48, Victor Stinner a écrit : > Hi, > > As a bug triager, it's very frustrating when I ask for more > information about a bug, and I get no reply. Usually, such bug is > closed as "out of date" (lack enough information to be debugged). There seems to be an untold assumption

[Python-Dev] April Steering Council update

Hi everyone, The SC has just published the community update for April: https://github.com/python/steering-council/blob/main/updates /2021-04-steering-council-update.md As a reminder, we'll are trying to keep this up monthly. As you can see we are mainly focusing on clearing the PEP backlog and

[Python-Dev] Re: Roundup to GitHub Issues migration

Hi, As a bug triager, it's very frustrating when I ask for more information about a bug, and I get no reply. Usually, such bug is closed as "out of date" (lack enough information to be debugged). The requirement for a GitHub account was well known when PEP 581 was accepted. The PEP was approved.

[Python-Dev] Re: [RELEASE] Python 3.10.0b3 is available

On Thu, Jun 17, 2021 at 11:36 PM Pablo Galindo Salgado wrote: > #And now for something completely different > > There are no green stars. Why? Thank you! This addition was great. :D ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe sen

[Python-Dev] Re: Roundup to GitHub Issues migration

On Mon, 21 Jun 2021 11:27:27 +0200 Baptiste Carvello wrote: > Hi, > > Le 21/06/2021 à 04:20, Ezio Melotti a écrit : > > This effort is being tracked at > > : this board reflects > > the current status of the project. The PEPs (including PEP 588 --

[Python-Dev] Re: Making PY_SSIZE_T_CLEAN not mandatory.

Hi, Le 18/06/2021 à 21:00, Guido van Rossum a écrit : > Can you elaborate on that use case? Which two applications are you > thinking of, and what was your goal in driving them? This sounds > interesting but I haven’t encountered this myself. Well, I'm not sure the case I was thinking of is still

[Python-Dev] Re: Roundup to GitHub Issues migration

Hi, Le 21/06/2021 à 04:20, Ezio Melotti a écrit : > This effort is being tracked at > : this board reflects > the current status of the project. The PEPs (including PEP 588 -- > GitHub Issues Migration Plan) haven't been updated yet and might > cont