Re: [python-committers] Fwd: Trunk and 3.0 branch are now open

no place like 127.0.0.1. -- Cheers, Benjamin Peterson There's no place like 127.0.0.1. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers -- --Guido van Rossum (home page: http

Re: [python-committers] [Python-3000] Proposed Python 3.0 schedule

van Rossum (home page: http://www.python.org/~guido/) ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Luke Kenneth

On Sun, Jan 25, 2009 at 9:15 AM, Steve Holden st...@holdenweb.com wrote: Guido van Rossum wrote: Is anyone else frustrated by Luke Kenneth Casson Leighton's rants in python-dev? It seems he is living on another planet to me. Or am I seeing it all wrong? He seems rather misguided

Re: [python-committers] build dependency on the branches on sphinx trunk necessary?

___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ python

Re: [python-committers] Give Daniel Diniz Developer access on the tracker?

Let's do it! On Tue, Feb 10, 2009 at 11:01 AM, Brett Cannon br...@python.org wrote: Daniel seems to be plowing through issues on the tracker and apparently Antoine has suggested he be added to the Developer role on the tracker. Any objections? -- --Guido van Rossum (home page: http

Re: [python-committers] Survey about DVCSs compared to svn

, and I've heard that a negative attitude prevails in the Git community. -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] PEP checkin process

. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org http

Re: [python-committers] Eric Araujo (merwok) as Distutils commiter

Well like it or not Tarek is not going to do it. So who will? You, or a new volunteer? --Guido (on Android) On Jul 27, 2010 5:58 AM, Antoine Pitrou solip...@pitrou.net wrote: So long as Eric is prepared to commit to our standard procedures (discussion and patches on issues before commit and

Re: [python-committers] Quick survey for PyCon talk on core development

http://mail.python.org/mailman/listinfo/python-committers -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] SVN repository is now read-only

up and getting this done. +1 -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] [PSF-Members] [Fwd: Re: Push rights for Ross Lagerwall]

record which version of the form is agreed to. As a temporary solution for new contributors, if you trust them, give them their permissions and ask them to fill the paperwork later (soon, but not as a condition for the permissions). -- --Guido van Rossum (python.org/~guido

Re: [python-committers] Anatoly Techtonik's contribution

it because he likes disagreement. He just lacks social skills (English not being his first language may contribute here). And yes, he doesn't seem to be learning from the feedback he gets. -- --Guido van Rossum (python.org/~guido) ___ python-committers

Re: [python-committers] Anatoly Techtonik's contribution

: On Wed, Nov 7, 2012 at 9:26 AM, Dirkjan Ochtman dirk...@ochtman.nl wrote: On Wed, Nov 7, 2012 at 6:01 PM, Guido van Rossum gu...@python.org wrote: imagine it must be pretty lonely being the only geek with deep Python knowledge and interest in Minsk. I don't want to distract from your

Re: [python-committers] Anatoly Techtonik's contribution

python-committers@python.org javascript:; http://mail.python.org/mailman/listinfo/python-committers -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python

Re: [python-committers] PyCon US 2013 attendees

the end of the sprints). Me too. Us hard-core old-timers gotta stick together. -Barry ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers -- --Guido van Rossum (python.org

Re: [python-committers] PyCon US 2013 attendees

On Mon, Feb 25, 2013 at 12:21 PM, Ned Deily n...@acm.org wrote: Guido van Rossum gu...@python.org wrote: I'll try to attend 1-2 days of sprints (and the rest of the conference, of course, and the language summit if there is one). Is there uncertainty about having the language summit

Re: [python-committers] I will NOT be leading the core sprint at PyCon US this year

___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org http://mail.python.org

Re: [python-committers] PyCon US 2013 attendees

___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org http://mail.python.org

Re: [python-committers] Commit rights to Ethan Furman

for the typo -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] hg clone cpython newrepo aborts

to give the name a non-alphabetic prefix. Please just use README.txt. -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] hg clone cpython newrepo aborts

I think we have a zen rule about this: Special cases aren't special enough to break the rules. (And I know what the next rule is, but I don't think it applies here. :-) On Tue, May 28, 2013 at 4:56 PM, Terry Reedy tjre...@udel.edu wrote: On 5/28/2013 7:23 PM, Guido van Rossum wrote: On Tue

Re: [python-committers] Policy for committing to 2.7

. :-) -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Anatoly has been warned about his behaviour potentially leading to his loss of tracker privileges

On Fri, Nov 29, 2013 at 11:34 AM, Brett Cannon br...@python.org wrote: On Fri, Nov 29, 2013 at 1:56 PM, Guido van Rossum gu...@python.orgwrote: On Fri, Nov 29, 2013 at 10:41 AM, Georg Brandl g.bra...@gmx.net wrote: Am 29.11.2013 19:22, schrieb Tim Peters: I pretty much ignore Anatoly

Re: [python-committers] Anatoly has been warned about his behaviour potentially leading to his loss of tracker privileges

reaction severely damaged its atmosphere and really did scare new people away. This led me to look up help vampire which led me to a wiki on the topic of community management. Here's a sample link: http://communitymgt.wikia.com/wiki/RTFM -- --Guido van Rossum (python.org/~guido

Re: [python-committers] Anatoly has been warned about his behaviour potentially leading to his loss of tracker privileges

will stand up to scrutiny. My offer to mediate (*after* he's been banned) stands, but it's up to you if and how you want to mention that to Anatoly. -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org

Re: [python-committers] Anatoly has been warned about his behaviour potentially leading to his loss of tracker privileges

. -- Nick Coghlan | ncogh...@gmail.com javascript:; | Brisbane, Australia -- --Guido van Rossum (on iPad) ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Status of the Derby, and request for another slip

stick to the plan. We've already slipped once. Perfection is not required. -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] PEP 450: Commit access for Steven D'Aprano?

, Australia ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers -- --Guido van Rossum (python.org/~guido) ___ python-committers

Re: [python-committers] Do people prefer pushing feature repos or one massive patch?

/listinfo/python-committers -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] How are we merging forward from the Bitbucket 3.5 repo?

* ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https

Re: [python-committers] Gratuitous? incompatibilities in the fix only releases

___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https

Re: [python-committers] Gratuitous? incompatibilities in the fix only releases

July 2015 at 05:20, Eric Snow ericsnowcurren...@gmail.com wrote: On Jul 29, 2015 11:08 AM, Robert Collins robe...@robertcollins.net wrote: On 30 July 2015 at 04:50, Guido van Rossum gu...@python.org wrote: The more recent Python 2.7 bugfix releases have specific exemptions from

Re: [python-committers] Can't merge into 3.6 (default) branch

Well, somehow I managed to fix it by switching directories... Not sure what happened. :-( On Mon, Sep 28, 2015 at 1:23 PM, Brett Cannon <br...@python.org> wrote: > > > On Mon, 28 Sep 2015 at 13:17 Guido van Rossum <gu...@python.org> wrote: > >> I've made some c

Re: [python-committers] Github accounts

On Sun, Jan 3, 2016 at 5:38 AM, M.-A. Lemburg <m...@egenix.com> wrote: > On 03.01.2016 05:19, Guido van Rossum wrote: > > This hardly seems like a real problem, so let's not worry more about it > > until someone actually needs help solving this. > > For Andrew, it wou

Re: [python-committers] We will be moving to GitHub (hopefully) in2016

han an Hg clone of an equivalent repo? I currently often rely on a single Hg clone containing all branches. +1 on not supporting ESR, for the stated reason. -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@p

Re: [python-committers] We will be moving to GitHub (hopefully) in 2016

rg > https://mail.python.org/mailman/listinfo/python-committers > -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Github accounts (was: formalising retirement as a Python committer)

This hardly seems like a real problem, so let's not worry more about it until someone actually needs help solving this. -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https://mail.python.org

Re: [python-committers] I broke the 3.5 branch, apparently

Dump, Core Dump" _/_/_/_/_/_/ _/_/ _/_/ > "El amor es poner tu felicidad en la felicidad de otro" - Leibniz > > > ___ > python-committers mailing list > python-committers@python.org > https

Re: [python-committers] Deprecation Policy PEP

Following the lead of 2.7.10 and 2.7.11 we could continue with 3.10, 3.11, etc. I also want the 3->4 transition to feel like a non-event for most users. How we'll do that I don't know yet, but I want it to be a lot smoother than 2->3. -- --Guido van Rossum (python.org/

Re: [python-committers] 2016 Python Language Summit: Can we get volunteers to talk about pathlib?

Wait for Brett. On Friday, April 29, 2016, Larry Hastings <la...@hastings.org> wrote: > > On 04/29/2016 03:53 PM, Guido van Rossum wrote: > > The primary debate should be about fspath or not. Inheriting from str is > off the table while I'm BDFL. Removing pathlib from

Re: [python-committers] 2016 Python Language Summit: Can we get volunteers to talk about pathlib?

> python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > -- --Guido van Rossum (python.org/~guido)

Re: [python-committers] PEP process with github

_ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] We are now live on GitHub!

t; efforts like this that reinforce to me why the Python community is the > best. > +1. Brett, you're the best. And thanks to everyone who helped out! -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.

Re: [python-committers] [RELEASE] Python 3.6.0b1 is now available

0rc1... > > Paul > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ -- --Guido van Ros

Re: [python-committers] commit privileges for INADA Naoki

t; my particular areas of interest, and even then, hitting a bug or API > limitation myself is often the main motivator for applying someone > else's patch) > > -- > Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia > ______________

Re: [python-committers] Greeting from INADA Naoki

s://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] [Core-mentorship] Regarding reviewing test cases written for tabnanny module

Thanks for the clarification. We should probably move this discussion to the python-committers list rather than core-mentorship. On Mon, Apr 10, 2017 at 12:12 PM, Terry Reedy <tjre...@udel.edu> wrote: > On 4/10/2017 12:54 PM, Guido van Rossum wrote: > >> So the response

Re: [python-committers] Regarding reviewing test cases written for tabnanny module

. We shouldn't need rebase any more, merge should be fine for all situations. (I can think of exceptions but they aren't worth mentioning.) -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https://mail

Re: [python-committers] Please edit the commit message when merge a PR

___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > -- --Guido van Rossum (python.org/~guido) _

Re: [python-committers] GitHub blog post on managing email notifications

thub-notifications > > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > > -- --Guido van Rossum (python.org/~guido)

Re: [python-committers] Github reviews are cannibalizing BPO

part to >> make our culture be "discuss on BPO", but it will produce a much >> superior history to what github PRs produce, so I think it is worth it. >> > > I agree with David and MAL. github PR's should replace Rietveld for code > reviews, and should not repla

Re: [python-committers] Proposal for procedures regarding CoC actions

level > >> decision making is built into the PSF By-laws > >> 4. The Board membership list at any given point in time is public > >> information > >> 5. The Board is already set up to handle confidential discussion of > >> sensitive matters > >>

[python-committers] Reminder! Today's the last day for core sprint sign-ups!

___________ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > > -- --Guido van Rossum (python.org/~guido <http://python.org/%7Eguido>) ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Proposing Carol Willing to become a core developer

ng Carol about > the idea before I saw this thread) > > Cheers, > Nick. > > -- > Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia > ___ > python-committers mailing list > python-committers@python.org > ht

Re: [python-committers] Proposal for procedures regarding CoC actions

o I write to python-committers? > What if it was a core developer who was being rude, where can a non > core-dev contributor report such behavior? > > > > Mariatta Wijaya > > On Thu, May 4, 2017 at 6:53 AM, Nick Coghlan <ncogh...@gmail.com> wrote: > >> On 4 May

Re: [python-committers] Should I merge a PR that I approved if it was written by a different core developer?

n up some small nits, and then they can merge their own diff. Or you may be OK with the diff but want to wait for some other reviewer's OK. The good news is that it's no longer wrong, since the author is preserved regardless of who merges. -- --Guido van Rossum (python.org/~guido)

Re: [python-committers] Should I merge a PR that I approved if it was written by a different core developer?

nsensus that usually the author (if a core dev) wants to merge their own work on their own time. -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-commit

Re: [python-committers] Should I merge a PR that I approved if it was written by a different core developer?

t; > wait for some other reviewer's OK. > > Yeah, it's not uncommon that I prefer to get a second review. Usually, > I explicitly say it in a comment. > > > The good news is that it's no longer wrong, since the author is preserved > > regardless of who merge

Re: [python-committers] Hacktoberfest

>> Antoine. >> ___ >> python-committers mailing list >> python-committers@python.org >> https://mail.python.org/mailman/listinfo/python-committers >> Code of Conduct: https://www.python.org/psf/codeofconduct/ >

[python-committers] Adding Ivan Levkivskyi as a core committer

(557, 563). He is responsible for at least 16 commits in master. I have worked with him for a long time on typing.py and on mypy (where he is a core dev) and I can vouch for him completely. -- --Guido van Rossum (python.org/~guido) ___ python-committers

Re: [python-committers] Adding Ivan Levkivskyi as a core committer

est an approval by other > core developers if he wants to touch other parts of CPython. In my > experience, developers are already doing that naturally, but I would > prefer to clarify this point. > > Victor > > 2017-12-06 2:00 GMT+01:00 Guido van Rossum <gu...@python.org

Re: [python-committers] Security: please enable 2-factor authentication on GitHub and your email

u’re already logged into GitHub and pushes/pulls don’t require it. > > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://ww

Re: [python-committers] Adding Ivan Levkivskyi as a core committer

I first had an idea to give Ivan commit privileges when I > was merging his PEP 526 implementation, so I think it's long overdue. > > Yury > > On Tue, Dec 5, 2017 at 8:00 PM, Guido van Rossum <gu...@python.org> wrote: > > I'd like to propose Ivan Levkivskyi as a new core c

Re: [python-committers] Adding Ivan Levkivskyi as a core committer

I think I figured it out -- I invited him to the python org on GitHub. Anything else? On Wed, Dec 6, 2017 at 8:37 AM, Guido van Rossum <gu...@python.org> wrote: > OK, let's make it so. It's been a long time since I initiated a new > committer -- what has to happen next? I just

Re: [python-committers] PEP 572 at the Language Summit next week

trip > is cancelled. Oh oh. > > Victor > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Proposing Mark Shannon to be a core developer

re developer yet?" replies. > > Wait. Mark is already a core dev, right? I don't understand your email :-) > > +1, obvisouly. > > Victor > ___ > python-committers mailing list > python-committers@python.org

Re: [python-committers] AppVeyor and Travis-CI

n the devguide, but if I missed it please let me know. >> >> Thanks. >> Eric >> ___ >> python-committers mailing list >> python-committers@python.org <mailto:python-committers@python.or

Re: [python-committers] Proposing Mark Shannon to be a core developer

hon Core Developer?" https://youtu.be/hhj7eb6TrtI > > On Tue, May 15, 2018, 11:35 AM Guido van Rossum <gu...@python.org> wrote: > >> Let's stop the email barrage, Mark is in. Can someone tell Mark what to >> do? >> >> -- --Guido van Rossum (python.org/~guid

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

On Tue, May 22, 2018 at 2:50 PM, Victor Stinner <vstin...@redhat.com> wrote: > 2018-05-19 0:25 GMT+02:00 Guido van Rossum <gu...@python.org>: > > Discussing PEPs on python-dev and python-ideas is clearly not scalable > any > > more. (Even python-committers p

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

On Tue, May 22, 2018 at 11:58 AM, Barry Warsaw <ba...@python.org> wrote: > [I think my other response got dropped, so apologies for any duplicates] > > Guido van Rossum wrote: > > I wonder if it would make sense to require that for each PEP a new GitHub > > *repo* be c

[python-committers] A different way to focus discussions

to all peps traffic. Thoughts? (We can dogfood this proposal too, if there's interest. :-) -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

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

PEPs to a subdirectory have also failed, due to perpetual lack of resources to complete the task (and e.g. the need to update scripts on python.org whenever the peps repo structure changes). > > -- > Ivan > > > > On 18 May 2018 at 18:25, Guido van Rossum <gu...@python.org>

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

Yes, you can do that. On Fri, May 18, 2018, 16:51 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?

Re: [python-committers] Changing commiter status (was: Missing In Action)

and posted it to all friends, YES! :-) > > That said: I would fully understand if my status was changed to “dormant > core dev” or “retired core dev” and I wouldn’t have any problems with that. > > Jack > > > On 18-Jun-2018, at 21:07 , Guido van Rossum wrote: > > Hm, unle

Re: [python-committers] Changing commiter status (was: Missing In Action)

_________ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Changing commiter status

isappears? There > is value in having the logo show up when commenting. > > —Chris > > On Mon, Jun 18, 2018 at 1:52 PM Paul Moore wrote: > >> On 18 June 2018 at 20:41, M.-A. Lemburg wrote: >> > On 18.06.2018 21:07, Guido van Rossum wrote: >> >> Hm, unless I mi

Re: [python-committers] Changing commiter status

at 11:23 AM Brett Cannon wrote: > > > On Mon, 18 Jun 2018 at 17:56 Guido van Rossum wrote: > >> I'd do it as follows. This basically makes withdrawal voluntary unless >> they don't respond at all. >> >> 1. Make a list of people who've not shown any sign of

Re: [python-committers] Changing commiter status

t; On Mon, 18 Jun 2018 at 17:56 Guido van Rossum wrote: > > >> I'd do it as follows. This basically makes withdrawal voluntary unless > >> they don't respond at all. > >> > >> 1. Make a list of people who've not shown any sign of activity (on the > >>

Re: [python-committers] Results of Pablo's promotion votes: Pablo ispromoted as a core dev!

; > * Serhiy Storchaka ("-0") > > > > Victor > > ___ > > python-committers mailing list > > python-committers@python.org > > https://mail.python.org/mailman/listinfo/python-committers > > Code of Conduct: h

Re: [python-committers] Changing commiter status

On Mon, Jun 18, 2018 at 10:12 PM Tal Einat wrote: > On Tue, Jun 19, 2018 at 3:54 AM, Guido van Rossum > wrote: > > > > If we currently have a list of core devs we should by default change > people's status to emeritus core dev when they choose (c). They may also > c

Re: [python-committers] Wrongly stopping merges discourages merging.

; python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-com

Re: [python-committers] number of active core devs [was: Comments on moving issues to GitHub]

@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Introduction - Pablo Galindo Salgado

> ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > -- --Guido van Rossum (python.org/~guido

Re: [python-committers] Let's give commit privileges to Nathaniel J. Smith

t;> python-committers mailing list > >> python-committers@python.org > >> https://mail.python.org/mailman/listinfo/python-committers > >> Code of Conduct: https://www.python.org/psf/codeofconduct/ > >> > > ___________ &

Re: [python-committers] Welcome the 3.8 and 3.9 Release Manager - Łukasz Langa!

rs@python.org >> https://mail.python.org/mailman/listinfo/python-committers >> Code of Conduct: https://www.python.org/psf/codeofconduct/ >> >> > ___________ > python-committers mailing list > python-committers@python.org > http

[python-committers] Issues with hundreds of commits being opened and closed -- what's going on?

s such PRs to be created? -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Issues with hundreds of commits being opened and closed -- what's going on?

Ah. Makes sense. UI design is hard... Thanks! On Thu, Feb 15, 2018 at 4:35 PM, Zachary Ware <zachary.ware+py...@gmail.com> wrote: > On Thu, Feb 15, 2018 at 6:21 PM, Guido van Rossum <gu...@python.org> > wrote: > > Occasionally I receive a sequence of email

Re: [python-committers] Transfer of power

I’m still here, but I would like to be out of the debate and out of the decision loop. I’m also still President of the PSF. But this is not for the PSF to decide. You all are doing fine. —Guido On Sun, Jul 15, 2018 at 1:37 PM Brett Cannon wrote: > > > On Sun, Jul 15, 2018, 13:01 Thomas

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

t of Zulip, as well as incentive for folks > to join. > > -- > ~Ethan~ > > > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Cod

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

oesn't work at all. So if you don't want to go to python-ideas, you have my blessing. > Mariatta > > > On Wed, Jul 11, 2018 at 10:38 AM Guido van Rossum > wrote: > >> I like the Zulip idea, though it'll be hard to get permalinks to past >> discussions. >> >

[python-committers] Please be patient

or the week after. There are also several minor TODOs in the PEP that need to be resolved. I will sort it all out, just please be patient. -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https

[python-committers] Transfer of power

, but I'm trying to let you all figure something out for yourselves. I'm tired, and need a very long break. -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo

Re: [python-committers] How to calm down the discussion on the PEP 572?

ers because I now fear that I would > get too many replies on python-dev ... > > Victor > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Cod

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

visor you also can’t see how people have voted at > all until > > after the voting ends. You can only see how many people voted. This > makes it > > harder to meaningfully influence the election because you won’t be able > to > > make targeted, strategic puppet votes without either

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

this community, you'll have to do that work. Getting to know a new online tool isn't going to kill you. -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python

[python-committers] Fwd: [Python-ideas] JS’ governance model is worth inspecting

van Rossum (python.org/~guido) ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] 1 week to Oct 1

ssions and attendee registrations tend to happen immediately before the deadline. I propose not to move the deadline *unless* the PEP authors ask for an extension on the eve of Oct 1st. -- --Guido van Rossum (python.org/~guido) ___ python-committers mailing list

Re: [python-committers] Council / board (Was: 1 week to Oct 1)

l documented that diverse group make better decisions. And given that there is a historical bias, often unconscious, towards white men I think it's good to try to counter this bias explicitly. I should also think that "merit-based" criteria tend to reinforce the existing unconscious bi

Re: [python-committers] *Important*: Python governance vote (December 2018): Ballots Sent

> >> python-committers mailing list > >> python-committers@python.org > >> https://mail.python.org/mailman/listinfo/python-committers > >> Code of Conduct: https://www.python.org/psf/codeofconduct/ > > > >

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

ps://www.youtube.com/watch?v=hKxbO4rRlpg and > https://www.youtube.com/watch?v=ww1UsGZV8fQ > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers &

  1   2   >