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

That sounds great, thanks Mariatta. -Barry > On Jun 23, 2021, at 12:36, Mariatta wrote: > > My understanding is that Ezio is/will be working on updating PEP 588. > Last I heard from Ezio is that he would be co-author of PEP 588 and he would > be updating it/rewrite it to better match the

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

My understanding is that Ezio is/will be working on updating PEP 588. Last I heard from Ezio is that he would be co-author of PEP 588 and he would be updating it/rewrite it to better match the current migration plan. I will check with Ezio and the gh-migration group on the status. Thanks. On

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

On Jun 23, 2021, at 03:21, Paul Moore wrote: > PEP 588 has not been accepted, so it's not necessarily relevant to the > actual migration plan here, but I do think it's reasonable to ask for > some clarification. Either PEP 588 should be rejectected, noting that > the actual implementation plan

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

On Jun 22, 2021, at 15:52, Brett Cannon wrote: > > One thing I will remind people is I personally have led the work to move this > project from: > • SourceForge to our own infrastructure > • Mercurial to git > • Our own infrastructure to GitHub for code management > So if

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

On Tue, 22 Jun 2021 19:49:12 -0400 Ned Deily wrote: > > I think this points out a problem with our current bug system and one that it > would be good to try to resolve in migrating to a new system: that is, the > ambiguity of the "version" metadata in an issue. Today, that list of versions >

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

On Wed, 23 Jun 2021 at 01:21, Brett Cannon wrote: > Regardless, there are no plans to halt what was decided when we accepted PEP > 581. Most of the concerns which have been brought up in this thread were > already expressed back then (the account merge one I didn't remember, hence > why I

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

On Tue., Jun. 22, 2021, 14:50 Glenn Linderman, wrote: > On 6/22/2021 12:52 PM, Brett Cannon wrote: > > > > On Mon, Jun 21, 2021 at 4:09 PM Glenn Linderman > wrote: > >> On 6/21/2021 2:31 PM, Christopher Barker wrote: >> >> >> By contrast, requiring a github account for reporting bugs also makes

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

On Jun 22, 2021, at 18:35, Irit Katriel via Python-Dev wrote: > On Tue, Jun 22, 2021 at 11:22 PM Terry Reedy wrote: >> With 2.x gone and a backport flow, essentially all issues are for main, >> so leave version tags off the issue (and eliminate the need to update >> them!). > For enhancement

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

On Tue, Jun 22, 2021 at 11:22 PM Terry Reedy wrote: > > With 2.x gone and a backport flow, essentially all issues are for main, > so leave version tags off the issue (and eliminate the need to update > them!). For enhancement requests I agree we probably don't need to keep updating the version

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

On 6/22/2021 3:52 PM, Brett Cannon wrote: One thing I will remind people is I personally have led the work to move this project from: 1. SourceForge to our own infrastructure 2. Mercurial to git 3. Our own infrastructure to GitHub for code management At this point, I (once a skeptic)

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

On 6/22/2021 12:52 PM, Brett Cannon wrote: On Mon, Jun 21, 2021 at 4:09 PM Glenn Linderman > wrote: On 6/21/2021 2:31 PM, Christopher Barker wrote: By contrast, requiring a github account for reporting bugs also makes python an

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

On Mon, Jun 21, 2021 at 4:09 PM Glenn Linderman wrote: > 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"

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

This is perhaps a different issue, but perhaps not. PSF grants are also subject to absurd and convoluted (and difficult to interpret) "export control" rules. Also rules subject to change at any moment at the whims of the latest US government grandstanding. USA incorporation definitely has

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

On 6/22/2021 4:40 AM, Baptiste Carvello wrote: Le 21/06/2021 à 23:31, Christopher Barker a écrit : Also: cPython is a large, complex, and mature project. I don't think many non-developers can even identify a true bug, much less write a helpful big report. [...] There is a genuine question

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

On 6/22/2021 4:00 AM, Tiziano Zito wrote: Hi, On Mon 21 Jun, 13:48 +0200, Victor Stinner wrote: The requirement for a GitHub account was well known when PEP 581 was accepted. The PEP was approved. It's now time to move on! I think it is important to notice that GitHub actively blocks user

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

Hi, Le 21/06/2021 à 23:31, Christopher Barker a écrit : > > > [...] Github is a > > developers' social network, "mere" users are much less likely to want to > > be part of it. [...] > > > But you don’t need to be “part of it” in any meaningful way. One only > needs to create an

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

(For some weird reason, I didn't get this mail via the list, only the private copy, so I might break threading by replying via my private copy.) Am 22.06.21 um 14:01 schrieb Nathaniel Smith: As much as we might wish otherwise, the PSF is also a US entity and has to comply with US laws.

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

On Tue, 22 Jun 2021 05:01:17 -0700 Nathaniel Smith wrote: > > As much as we might wish otherwise, the PSF is also a US entity and > has to comply with US laws. GitHub's official policy at > >https://docs.github.com/en/github/site-policy/github-and-trade-controls > > gives the impression

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

On Tue, Jun 22, 2021 at 4:42 AM Sebastian Rittau wrote: > > Am 22.06.21 um 10:00 schrieb Tiziano Zito: > > I think it is important to notice that GitHub actively blocks user > > registration and activity from countries that are sanctioned by the US > > government. At least in 2019 GitHub was

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

Am 22.06.21 um 10:00 schrieb Tiziano Zito: I think it is important to notice that GitHub actively blocks user registration and activity from countries that are sanctioned by the US government. At least in 2019 GitHub was blocking users from IPs located in Cuba, North Corea, Syria, Crimea,

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

Hi, On Mon 21 Jun, 13:48 +0200, Victor Stinner wrote: The requirement for a GitHub account was well known when PEP 581 was accepted. The PEP was approved. It's now time to move on! I think it is important to notice that GitHub actively blocks user registration and activity from countries

[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

[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

[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

[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

[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: 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: 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 >