[python-committers] Re: Making it easier to track who is currently considered "active" for voting

How are you measuring "activity"? Just commits? On Tue, Oct 20, 2020 at 12:16 PM Brett Cannon wrote: > With the next SC election fast approaching, I did the final tweaks I > wanted to make to the voters repo to address visibility issues we had in > the last election. > > First, there is now a mo

[python-committers] Re: MSDN Subscription renewals

On Thu, Aug 13, 2020 at 11:04 AM Zachary Ware wrote: > > On Thu, Aug 13, 2020 at 12:29 PM Steve Dower wrote: > > While most of the tooling necessary for working on CPython is freely > > available (as Visual Studio Community), this will also include OS images > > and Azure credits. > > For referen

[python-committers] Re: Notification of a three-month ban from Python core development

On Thu, Jul 23, 2020, 05:46 Donald Stufft wrote: > > > On Jul 23, 2020, at 3:52 AM, Matthias Klose wrote: > > Apparently there was agreement to hide this kind of information, and that's > worse than the original behavior that was acted on. Who will be next? For > what > reason? I am not questio

[python-committers] Re: Notification of a three-month ban from Python core development

On Thu, Jul 23, 2020, 05:25 Jack Diederich wrote: > I'm sorry we had to ban Guido for three months but maybe he'll learn his > lesson and not merge commit messages that include screeds about "relics of > white supremacy". > I'm guessing there's some layers of irony or sarcasm in this message, bu

[python-committers] Re: Notification of a three-month ban from Python core development

Given that this is a response to behavior in public mailing list posts, the lack of specificity feels off to me. Whatever this person did is already public. What's being hidden isn't their behavior; it's the conduct-wg/steering-council's reasoning for banning them. The point of having a CoC is that

[python-committers] Re: The Night’s Watch is Fixing the CIs in the Darkness for You

On Fri, Apr 3, 2020 at 11:32 AM Victor Stinner wrote: > I had to update the OpenSSL version in the CI configuration which > lives in the same Git repository than Python code base. Since our CI > currently runs on unmodified PRs, maybe the 1090 pending pull requests > must now be rebased manually o

Re: [python-committers] [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

On Mon, May 20, 2019 at 9:05 PM Xiang Zhang wrote: > > Also, Github has just changed its export control. As an international team, > does it affect us and PEP581? Maybe better consult the lawyer first? > > http://help.github.com/en/articles/github-and-export-controls From a quick non-expert read

Re: [python-committers] Can we choose between mailing list and discuss.python.org?

On Thu, Feb 14, 2019, 09:39 Brett Cannon > > On Wed, Feb 13, 2019 at 12:17 PM Paul Moore wrote: > >> On Wed, 13 Feb 2019 at 19:56, Steve Dower wrote: >> > >> > On 13Feb2019 1112, Brett Cannon wrote: >> > > >> > > >> > > On Wed, Feb 13, 2019 at 2:55 AM Paul Moore > > >

Re: [python-committers] Draft ballot text

t get sent out right at midnight on the 1st, while still keeping the two week period? -n On Thu, Nov 29, 2018 at 8:03 PM Nathaniel Smith wrote: > > Hi all, > > Since the vote's supposed to be starting in a few days, I figured it > would be good to finish up the fiddly detai

[python-committers] Draft ballot text

Hi all, Since the vote's supposed to be starting in a few days, I figured it would be good to finish up the fiddly details and avoid any last-minute editing. So here's a draft proposal for the ballot instructions and options: https://github.com/python/peps/pull/844 I also set up a test vote on CI

Re: [python-committers] A plea to stop last-minute changes to governance PEPs

On Mon, Nov 19, 2018 at 5:30 AM Paul Moore wrote: > My feeling, however, is that the PEPs that are having the most trouble > with this are the ones that are trying to pin down too much detail. > Sure (to pick a random example), it's ultimately going to be important > that a council have a clear id

Re: [python-committers] A plea to stop last-minute changes to governance PEPs

On Sun, Nov 18, 2018 at 3:17 AM Antoine Pitrou wrote: > A couple days ago Nathaniel pushed significant changes to his governance > PEP (PEP 8016). This means some governance PEPs are apparently still > *not* finalized. This raises a problem: when can we consider that we > are reading the final v

[python-committers] Straw poll: Which governance proposals do you like best?

There's been a lot of clarification and critique for individual governance proposals, but not a lot of discussion of how they compare to each other or what different core devs think is important. And I know that for complicated issues like this, I often don't understand the trade-offs until I talk

Re: [python-committers] Timeline to vote for a governance PEP

On Sun, Nov 4, 2018 at 10:53 AM, Paul Moore wrote: > As one example of my confusion here, > https://www.python.org/dev/peps/pep-8016/ is currently a 404. Sorry about that – there's a thread here with background: https://discuss.python.org/t/working-discussion-for-pep-8016-the-boringest-possi

Re: [python-committers] Timeline to vote for a governance PEP

On Fri, Nov 2, 2018 at 8:40 PM, Victor Stinner wrote: > The PEP 8001 is not trivial, it expects a specific format: > > **DO NOT LEAVE ANY BRACKETS BLANK!** > **DO NOT REPEAT A RANKING/NUMBER!** > > Maybe it would help to have a script to validate my own vote? (Also > ensure that all choices are pr

Re: [python-committers] python-committers is dead, long live discuss.python.org

On Sat, Sep 29, 2018 at 1:53 AM, Nick Coghlan wrote: > This is exactly the kind of arbitrary decision making by an insufficiently > representative group that led to us banning making any binding decisions at > language summits: their in-person nature means that they're inherently > exclusive envir

Re: [python-committers] python-committers is dead, long live discuss.python.org

On Sat, Sep 29, 2018 at 1:51 AM, Serhiy Storchaka wrote: > 29.09.18 03:45, Łukasz Langa пише: >>> >>> On 28 Sep 2018, at 23:04, Serhiy Storchaka wrote: >> >> Do you use NNTP? Like with IRC, you won't find the next generation of core >> developers on it. And no, there is no support for it in Disco

Re: [python-committers] Python 4.0 or Python 3.10?

On Tue, Sep 25, 2018, 12:30 Yury Selivanov wrote: > The reason I'm asking this is because I frequently need to refer to > *that version* of Python in the documentation, especially when I'm > deprecating APIs or behavior. Right now I'm saying "Python 4.0" > implying that 4.0 will be released righ

Re: [python-committers] Fw: CoC violation (was: Retire or reword the "Beautiful is better than ugly" Zen clause)

On Thu, Sep 20, 2018 at 3:35 PM, Ethan Furman wrote: > And I have to argue against his use of the n-word* as being part of the > reason -- he wasn't calling anybody that, he was using the word as an > example of a taboo in one culture that is not in others. Using that as part > of the reason to b

Re: [python-committers] New core developers: Lisa Roach and Emily Morehouse-Valcarcel

Congratulations! On Fri, Sep 14, 2018, 12:29 Raymond Hettinger wrote: > At the developer sprints this week, we collectively decided to grant core > committer status to Emily and Lisa. > > Please join me in welcoming them to the team. > > > Raymond > > > --- > > Emily

Re: [python-committers] Organizing an informational PEP on project governance options (was Re: Transfer of power)

/wiki/Cookie_Licking [2] not to go into too many details, but basically I'm currently sick, unemployed, and broke, which isn't a crisis but sorting it out is sucking up a lot of energy. On Jul 13, 2018 04:31, "Nathaniel Smith" wrote: On Thu, Jul 12, 2018 at 6:35 PM, Łukasz La

Re: [python-committers] Reminder of BDFL succession timeline + CFP

On Wed, Aug 1, 2018 at 12:41 PM, Mariatta Wijaya wrote: > Since this is like a CFP I figured we should clarify what's expected the > proposal, and I also wanted to be more detailed in the timeline. > > Oct 1 00:00:00 UTC: Deadline of coming up with proposals of governance > model. > > To be includ

Re: [python-committers] An alternative governance model

On Fri, Jul 20, 2018 at 3:50 PM, Brett Cannon wrote: > > > On Fri, 20 Jul 2018 at 15:36 Nathaniel Smith wrote: >> >> On Fri, Jul 20, 2018, 08:58 Brett Cannon wrote: >> > While I'm purposefully staying out of this thread as my name is >> > currentl

Re: [python-committers] An alternative governance model

On Fri, Jul 20, 2018, 08:58 Brett Cannon wrote: > > > > On Fri, Jul 20, 2018, 07:51 Nick Coghlan, wrote: >> >> Guido was willing to do it for so long because Python was his >> creation, and he grew into the increasing demands of the BDFL role as >> time went by, but even he eventually reached the

[python-committers] Proposal: an explicit, time-limited moratorium on finalizing any governance decisions

[tl;dr: We need some ground rules, because uncertainty makes it hard to think straight. But if we get sucked into a complicated meta-debate about the ground rules then that defeats the purpose. My proposal for a Minimum Viable Ground Rule: let's all agree not to finalize any governance decisions be

Re: [python-committers] Transfer of power

On Fri, Jul 13, 2018 at 8:22 PM, Tim Peters wrote: > [Nathaniel Smith ] >> >> That's not really true -- life expectancy *at birth* was ~35 years, >> but mostly because so many people died as infants/children. If you >> survived long enough to get nominated for a

Re: [python-committers] Transfer of power

On Fri, Jul 13, 2018 at 6:54 PM, Tim Peters wrote: > [Larry Hastings] > ... >> >> However, once appointed, Elders are appointed is "for life". The only way >> to remove one would be for them to voluntarily step down--there would be no >> mechanism to remove one from office. (Perhaps this is too

[python-committers] Organizing an informational PEP on project governance options (was Re: Transfer of power)

On Thu, Jul 12, 2018 at 6:35 PM, Łukasz Langa wrote: > I'm +1 to an Informational PEP around the state of the art in project > governance. I think this is a great idea. There's a lot of experience out there on different governance models, but of course any given project only uses one of them, so

Re: [python-committers] Vote to promote Pablo Salingo Salgado as core developer

On Thu, Jun 14, 2018 at 4:40 AM, Berker Peksağ wrote: > This isn't about my or someone else's high standards. We keep saying > we need more triagers and reviewers, and we keep promoting people who > didn't do any issue triaging and code review. It's not fair to > contributors who have spent so muc

Re: [python-committers] Comments on moving issues to GitHub

On Sun, May 20, 2018, 03:18 Antoine Pitrou wrote: > > Le 19/05/2018 à 02:10, Victor Stinner a écrit : > > Hi, > > > > I failed to get the microphone after Mariatta's secret talk about > > moving Python issues from bugs.python.org (Roundup) to GitHub. > > A "secret talk"? What is that? > She gave

Re: [python-committers] Travis & AppVeyor hidden on Github, scroll the invisible region to see them.

On Fri, May 18, 2018 at 4:29 PM, Gregory P. Smith wrote: > What do people think about teaching miss-islington how to re-launch specific > CI runs a few times to deflake failures? ("1 out of n passes counts as a > pass") - That requires compute resources, but when it is what the human is > going to

Re: [python-committers] A different way to focus discussions

On Fri, May 18, 2018 at 4:51 PM, Ivan Levkivskyi wrote: > On 18 May 2018 at 19:46, Gregory P. Smith wrote: >> >> >> I'm all for picking a victom^Wvolunteer PEP to try dogfood it on. >> > > Can few related PEPs share the same repository? For example, I want to start > writing three PEPs about exte

Re: [python-committers] A different way to focus discussions

On Fri, May 18, 2018 at 3:25 PM, Guido van Rossum wrote: > Discussing PEPs on python-dev and python-ideas is clearly not scalable any > more. (Even python-committers probably doesn't scale too well. :-) PEP 572 seems like something of a perfect storm... it's simultaneously a bikeshed and a nuclea

Re: [python-committers] Visual Studio Team Services checks on pullrequests

On Thu, May 17, 2018 at 5:27 PM, Terry Reedy wrote: > Can VSTS run GUI tests on any of the systems? Right now, only Appveyor and > one or two of the Windows buildbots do so. It's certainly possible to use Xvfb to run headless GUI tests on Linux (or other Unixes that use X11). Any CI service shou

Re: [python-committers] Poll: Do you like the PEP 572 Assignment Expressions?

-1, I think, though I'm frustrated that in the parts of the list discussion I had energy to read, its proponents seemed to be saying that the most compelling examples aren't actually in the PEP (and I don't know what they are). On Wed, May 2, 2018 at 2:49 AM, Victor Stinner wrote: > Hi, > > I wou