[python-committers] Vote to promote Pradyun Gedam

I have just nominated Pradyun Gedam (@pradyunsg) to the core team. Please vote at https://discuss.python.org/t/vote-to-promote-pradyun-gedam/23001 ___ python-committers mailing list -- [email protected] To unsubscribe send an email to python-c

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

all the paths you want to _always_ be notified for globbing works as well. Then anytime someone sends a PR that touches that, the mention bot with @tiran you (unless we turned it off….). — Donald Stufft ___ python-committers mailing list python-committ

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

appening on GitHub because using Reitveld is/was more frustrating than a GitHub comment) and a lot of it happened in random back channels between individuals. Ultimately, it’s likely to be a Sisyphean battle to stop it from happening unless b.p.o gets updated to have a UX on par with Gi

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

ion (vs code review) because the friction of doing so is fairly high. I think if you want to encourage people to utilize bpo better, your best bet is to do everything you can to reduce that friction. — Donald Stufft ___ python-committers mailing list

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

> On May 2, 2017, at 3:42 PM, Donald Stufft wrote: > > >> On May 2, 2017, at 3:09 PM, M.-A. Lemburg > <mailto:[email protected]>> wrote: >> >> This doesn't have much to do with UX/UI. It's mainly a questions >> of culture. Github is more

Re: [python-committers] No Travis-CI on OS X?

elp detect platform issues at > PR time rather than later :-) > I think the only reason we don’t have them on is because the macOS builds on Travis are _Super_ slow and regularly get a large backlog. Fast Finish and Allowed Failures would

Re: [python-committers] Revert changes which break too many buildbots

lly, in most cases, the bug is trivial and I consider that the > fix doesn't require a review, so I push it directly. > > Victor > ___ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-com

Re: [python-committers] How does GitHub count contributors?

o match my commit > e-mail to my GitHub account? That’s interesting, have you used multiple email addresses with the Python VCS history by any chance? If so you can add them all to your Github account and it should associate all of them with you. — Donald Stufft ___

Re: [python-committers] OK to back-fill "awaiting" labels on open issues?

> On Oct 6, 2017, at 5:36 PM, Alex Gaynor wrote: > > Can we please use a phrase for re-triggering a review that makes more sense > like "I've updated the patch, please re-review", rather than magic inside > baseball language? > +1 ___ python-comm

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

> On Dec 11, 2017, at 7:03 AM, Paul Moore wrote: > > Um, I use https not ssh, as for at least some of the time I'm behind a > firewall that only allows https, not ssh traffic. (I know, I'm sorry - > I can probably be the worst possible corner case for *any* suggestion > that gets made :-)) htt

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

> On Dec 11, 2017, at 8:04 AM, Paul Moore wrote: > >> On 11 December 2017 at 12:29, Donald Stufft wrote: >> >> On Dec 11, 2017, at 7:03 AM, Paul Moore wrote: >> >> Um, I use https not ssh, as for at least some of the time I'm behind a >> firew

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

> On Dec 11, 2017, at 9:35 AM, Paul Moore wrote: > > Maybe I didn't understand it. Doesn't that leave me in precisely the > same situation as a username/password, in that I have a single set of > credentials I can use? Or is the fact that it's tied to the specific > machine the point here? If so

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

> On Dec 11, 2017, at 2:52 PM, R. David Murray wrote: > > If 2fa is required for contribution to CPython, I'll stop > contributing. I’m curious why? I have it on and 99% of the time you don’t even notice because you’re already logged into GitHub and pushes/pulls don’t require it._

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

> On May 22, 2018, at 5:50 PM, Victor Stinner wrote: > > IMHO the discussions on the PEP 572 became a mess because nobody > wanted to moderate the discussion. I asked on python-committers how to > calm down the discussion, but no action has been taken and the flow of > emails didn't stop. FWIW,

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

> On May 24, 2018, at 2:05 PM, Antoine Pitrou wrote: > > > Le 24/05/2018 à 20:02, Brett Cannon a écrit : >>> Just trying to >>> understand how Discourse would be different enough to solve the issue >>> you're having. >> >>Which issue exactly? Zulip is decent as a chat system. It wouldn'

Re: [python-committers] Marking issues as "Release Blocker" priority (was Re: FINAL WEEK FOR 3.7.0 CHANGES!)

> On May 30, 2018, at 1:15 PM, Larry Hastings wrote: > > ISTM that opinions vary on what constitutes a "release blocker", and maybe > empowering only the release managers to make that call would be a good way > forward--which is what ISTM is what the Dev Guide already says anyway. But I > gu

Re: [python-committers] Marking issues as "Release Blocker" priority (was Re: FINAL WEEK FOR 3.7.0 CHANGES!)

> On May 30, 2018, at 3:03 PM, Larry Hastings wrote: > > Yes, ISTM that the Dev Guide covers this. The section on priority says: > Triagers may recommend this priority and should add the release manager to > the nosy list. > In other words: if a dev thinks an issue should be a release blocker

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

Is that a 50% reduction or is that just 50% of the people who could be active are? Sent from my iPhone > On Jun 2, 2018, at 8:33 PM, Ethan Furman wrote: > >> On 06/02/2018 12:46 PM, Mariatta Wijaya wrote: >> >> And perhaps this is to be discussed in a separate thread: even though in the >>

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

I’d also add that it is generally a good thing that people with power and a voice (e.g. the core devs) are having a similar experience that an external contributor would. This is our best line of defense against the external contributor experience degrading to a bad place. By having core devs sh

Re: [python-committers] Changing commiter status

> On Jun 19, 2018, at 1:35 PM, Victor Stinner wrote: > > My intent is to maintain a list of active core developers. If an > inactive core dev becomes active again, they should be able to > retrieve quickly the "active" status. Is "emeritus" still a good name > with such constraint? Yes. Dropp

Re: [python-committers] Proposal on how to vote (was: An alternative governance model)

> On Jul 18, 2018, at 6:18 PM, Łukasz Langa wrote: > > >> On Jul 18, 2018, at 4:56 PM, Brett Cannon wrote: >> >> While I am totally fine with a super-majority of votes for something to be >> accepted, I don't think the minimum participation requirement will work. If >> people simply choose

Re: [python-committers] An alternative governance model

> On Jul 18, 2018, at 7:06 PM, Fred Drake wrote: > > PEP 2 is (currently) the "Procedure for Adding New Modules". Though > superseded, recycling the PEP number seems out of character with the > RFC process from which we derived the PEP process. Let's be cautious > about recycling like that; in

Re: [python-committers] And Now for Something Completely Different

> On Jul 19, 2018, at 7:47 PM, Victor Stinner wrote: > > It seems that the main question for a new governance is how to take a > decision on PEPs (accept or reject them with some variants like > Deferred). I read that core developers are unable to make a decision > themselves (fail to reach a co

Re: [python-committers] And Now for Something Completely Different

> On Jul 25, 2018, at 2:01 PM, Brett Cannon wrote: > > Right, and your proposal means I now have to judge proposed core developers > on which side of popular opinion they will come down on in hopes that they > vote in ways I agree with and thus help take the language in a direction I > think

Re: [python-committers] List of all core developers

We should probably have a single source of truth for what a core developer is, and all other systems pull from that. > On Aug 3, 2018, at 3:43 AM, M.-A. Lemburg wrote: > > Please note that the motivation for having a list similar to the > one we have for PSF Fellows is not to determine voting e

Re: [python-committers] List of all core developers

> On Aug 3, 2018, at 1:52 PM, Brett Cannon wrote: > > > > On Fri, 3 Aug 2018 at 00:44 Donald Stufft <mailto:[email protected]>> wrote: > We should probably have a single source of truth for what a core developer > is, and all other systems pull from that. >

Re: [python-committers] List of all core developers

have a cronjob that syncs github permissions with that list. Sent from my iPhone > On Aug 4, 2018, at 12:51 PM, Brett Cannon wrote: > > > >> On Fri, Aug 3, 2018, 21:59 Donald Stufft, wrote: >> >> >>> On Aug 3, 2018, at 1:52 PM, Brett Cannon wrote: &

Re: [python-committers] Automerge bot deployed

Maybe the merge bot should render the description and then extract plaintext out of that?On Sep 13, 2018, at 2:16 PM, Victor Stinner wrote:Ah yes, it works and I agree that it's OK in plain text. But we have careful if a contributor uses "\_" or something like that in a descri

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

> On Sep 20, 2018, at 4:25 PM, Antoine Pitrou wrote: > > I think the action taken by Brett (apparently decided with Titus and a > mysterious "conduct working group") is not the right one: Just FTR, the conduct working group is the PSFs CoC Working Group, which I believe had an open call for

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

> On Sep 21, 2018, at 6:55 AM, Christian Heimes wrote: > > I don't understand why you are drawing the reverse conclusion here. Can > you give me one concrete example, in which a French, German, or any > other non-US American taboo was violated and not counteracted with swift > reaction? Right,

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

> On Sep 21, 2018, at 8:01 AM, Paul Moore wrote: > > On Fri, 21 Sep 2018 at 12:38, Carol Willing wrote: > >> Much of the discussion here has focused on the use of a few words. >> >> IMHO, discussing violence, assault, and implying that its okay to accept and >> trivialize this violence do n

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

> On Sep 21, 2018, at 8:59 AM, Paul Moore wrote: > > On Fri, 21 Sep 2018 at 13:30, Donald Stufft wrote: >> So part of being and open and welcoming community, is knowing and >> understanding that words, images, etc like that can make people feel like >> we’

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

> On Sep 25, 2018, at 12:24 PM, Antoine Pitrou wrote: > > > Le 25/09/2018 à 18:10, Guido van Rossum a écrit : >>To save us all trouble of discussing this particular issue, for >>those of you who disagree completely, and have other ideas about how >>you'd like Python to be governed

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

> On Sep 25, 2018, at 6:39 PM, Yury Selivanov wrote: > > I think we all have seen code like that; it's a common pattern. So by > just bumping the version to 4.0 you would break the compatibility for > some libraries and frameworks. And maybe breaking it is fine if > there's a very strong tech

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

Log into your account, go into preferences, enable Mailing List Mode. > On Sep 29, 2018, at 3:51 AM, Robert Collins wrote: > > +1 > > If someone can tell me how to configure discourse to work like a > mailing list; specifically: > > - email me messsages rather than 'X new messages" nuisance-ma

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

> On Sep 29, 2018, at 6:03 AM, Paul Moore wrote: > > 1. Pull technology rather than push. The fact that email is > *delivered* to me is a critical benefit for certain types of > interaction, and one that's far too easily dismissed by people who > promote pull solutions. It's baffling to me that

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

> On Sep 29, 2018, at 6:00 AM, Łukasz Langa wrote: > > >> On Sep 29, 2018, at 10:44, Stefan Krah wrote: >> >> Sorry if I misunderstand this, but is the plan to moderate *core developers* >> on python-committers? > > If you label it with an abstract term like this, it sounds like we just >

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

> On Sep 29, 2018, at 6:24 AM, Paul Moore wrote: > > But at least it was *possible*. Personally I do a Google search rather > than using my MUA, but the point is that while it's clumsy, it's known > technology. I don't even know how I'd find a link to an old message in > Discourse, but I assume

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

> On Sep 29, 2018, at 1:31 PM, Brett Cannon wrote: > > Another way to think about this is if we wait until after our governance > discussions and try this experiment the volume quite possibly won't be at a > level to stress test how the interaction on Discourse works. And while I > personally

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

On a specific category page, in the top right you can select a watch level for the whole category, the two relevant ones for you will be either “Watching” which will default all new topics in a category to watching or “first post”, which won’t set them to watching, but will email you for *only*

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

> On Oct 9, 2018, at 8:30 AM, M.-A. Lemburg wrote: > > On 09.10.2018 08:24, Donald Stufft wrote: >> On a specific category page, in the top right you can select a watch level >> for the whole category, the two relevant ones for you will be either >> “Watching”

Re: [python-committers] Moderation of the Python community

> On Oct 17, 2018, at 10:03 AM, Victor Stinner wrote: > > Handling conflicts between core developers is the most difficult > question. I don't think that it's the role of the conduct working > group to handle that. Moreover, the Code of Conduct should be seen as > a way to evict a core develope

Re: [python-committers] Moderation of the Python community

> On Oct 17, 2018, at 11:34 AM, Brian Curtin wrote: > > I think this type of issue is better solved internally to our team, perhaps > via some form of mediator(s) I mentioned earlier, rather than involving a > wholly external group. Time is of course a finite resource in open source, > and p

Re: [python-committers] Vote on governance will happen between Nov 16 - Nov 30

> On Oct 23, 2018, at 7:06 AM, Nick Coghlan wrote: > > On Tue, 23 Oct 2018 at 06:38, Łukasz Langa wrote: >> >> The voting procedure is described in PEP 8001. I flipped it from "Draft" to >> "Active" without further changes a few minutes ago. That's in the interest >> of giving everybody eno

Re: [python-committers] Vote on governance will happen between Nov 16 - Nov 30

> On Oct 23, 2018, at 7:56 AM, Antoine Pitrou wrote: > > > Le 23/10/2018 à 13:55, Donald Stufft a écrit : >> >> We’re using IRV and I accept that, but I just want to point out that IRV >> still has a form vote splitting (in electoral parlance, vote splittin

Re: [python-committers] Vote on governance will happen between Nov 16 - Nov 30

> On Oct 23, 2018, at 1:14 PM, Tim Peters wrote: > > [Alex Martelli mailto:[email protected]>>] > While I suspect most participants are aware of this, just in care some don't > I thought I'd just point out that it's futile to look for a "perfect" voting > system -- Kenneth Arrow proved that lo

Re: [python-committers] If you care about the voting method, please vote ; -)

> On Nov 2, 2018, at 8:22 PM, Chris Jerdonek wrote: > > On Fri, Nov 2, 2018 at 5:09 PM Tim Peters wrote: >> >> [Chris Jerdonek ] >>> It would have been nice to know beforehand if the results of the poll >>> were going to change the PEP. >> >> Don't look at me ;-) Like I said, "I'm not in ch

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

> On Nov 3, 2018, at 12:20 AM, Tim Peters wrote: > > [Tim] >>> Nevertheless, I probably won't vote - I object to public ballots on >>> principle. That's been raised by others, so I won't repeat the >>> arguments, and I appear to be very much in a minority here. > > [Eric Snow ] >> Would it he

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

> On Nov 3, 2018, at 12:38 AM, Donald Stufft wrote: > > > >> On Nov 3, 2018, at 12:20 AM, Tim Peters > <mailto:[email protected]>> wrote: >> >> [Tim] >>>> Nevertheless, I probably won't vote - I object to public ballots on >&

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

> On Nov 3, 2018, at 11:22 AM, Antoine Pitrou wrote: > > > Le 03/11/2018 à 16:19, Stefan Krah a écrit : >> On Sat, Nov 03, 2018 at 07:22:21AM -0700, Ethan Furman wrote: >>> On 11/03/2018 03:55 AM, Paul Moore wrote: >>> Frankly, I feel pretty disenfranchised by the process at the mom

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

> On Nov 3, 2018, at 1:24 PM, Donald Stufft wrote: > > > >> On Nov 3, 2018, at 11:22 AM, Antoine Pitrou wrote: >> >> >> Le 03/11/2018 à 16:19, Stefan Krah a écrit : >>> On Sat, Nov 03, 2018 at 07:22:21AM -0700, Ethan Furman wrote:

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

> On Nov 3, 2018, at 1:42 PM, Antoine Pitrou wrote: > >> Perhaps the difference is in that every mail client I’ve ever used >> presents mailing list threads (or any thread) as a singular flat stream >> anyways? > > Er, really? Generally they give you an option to turn on or off > threaded dis

Re: [python-committers] [OT] email clients

> On Nov 3, 2018, at 1:57 PM, Antoine Pitrou wrote: > > I find it interesting that you are so disturbed by threaded discussion > views, while for some other people it's the reverse. That advocates for > a system that allows both kinds of presentation, and Discourse isn't that. I would agree *

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

> On Nov 3, 2018, at 2:06 PM, Barry Warsaw wrote: > > I also prefer private ballots on principle, but I’ll still vote if they are > public. I don’t completely buy into the rationale in PEP 8001 on why they > must be public. So to avoid just complaining without an actionable suggestion, her

Re: [python-committers] [OT] email clients

> On Nov 3, 2018, at 3:04 PM, Ethan Furman wrote: > > On 11/03/2018 11:45 AM, Donald Stufft wrote: > >> I would agree *if* that was the only axis that the two tools differed on. > > It's enough for me. My participation on Discourse is going to be so low you

Re: [python-committers] [OT] email clients

> On Nov 3, 2018, at 3:17 PM, Antoine Pitrou wrote: > > > Le 03/11/2018 à 20:15, Donald Stufft a écrit : >> >> I’m the other way. I basically don’t participate in python-dev or >> python-ideas anymore because of the issues mailing lists have. > > Just

Re: [python-committers] [OT] email clients

> On Nov 3, 2018, at 3:19 PM, Donald Stufft wrote: > > > >> On Nov 3, 2018, at 3:17 PM, Antoine Pitrou > <mailto:[email protected]>> wrote: >> >> >> Le 03/11/2018 à 20:15, Donald Stufft a écrit : >>> >>> I’m the other way

Re: [python-committers] [OT] email clients

> On Nov 3, 2018, at 3:27 PM, Donald Stufft wrote: > > > >> On Nov 3, 2018, at 3:19 PM, Donald Stufft > <mailto:[email protected]>> wrote: >> >> >> >>> On Nov 3, 2018, at 3:17 PM, Antoine Pitrou >> <mailto:anto...@python

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

> On Nov 3, 2018, at 3:09 PM, Donald Stufft wrote: > > > >> On Nov 3, 2018, at 2:06 PM, Barry Warsaw > <mailto:[email protected]>> wrote: >> >> I also prefer private ballots on principle, but I’ll still vote if they are >> public. I don’t

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

> On Nov 3, 2018, at 4:45 PM, Donald Stufft wrote: > > > > > One thing we need if we do go this route, is a single person to act as the > election supervisor. Their powers are limited basically they configure the > election, adding a description, the choices, et

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

> On Nov 3, 2018, at 8:21 PM, Steven D'Aprano wrote: > > >> how can I trust that the decision will be one I can be comfortable >> with - and how do I influence the direction except by participating in >> the discussions I've been unable to locate? > > That's a reasonable question. I wish I h

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

> On Nov 3, 2018, at 8:41 PM, Donald Stufft wrote: > > As far as I am aware there is a topic per PEP on discourse that has had > discussion mostly related to the specific PEP. I’m not aware of any general > “weighing the options” topic on any discussion forum. I think so far

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

> On Nov 3, 2018, at 11:56 PM, Tim Peters wrote: > > [Donald Stufft ] >> So to avoid just complaining without an actionable suggestion, here’s a >> suggestion: >> >> Use https://civs.cs.cornell.edu with the following settings (x in the ones >> turned o

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

> On Nov 4, 2018, at 1:52 AM, Donald Stufft wrote: > >> >> On Nov 3, 2018, at 11:56 PM, Tim Peters > <mailto:[email protected]>> wrote: >> >> [Donald Stufft mailto:[email protected]>>] >>> So to avoid just complaining without an acti

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

> On Nov 5, 2018, at 2:29 PM, Paul Moore wrote: > > Hmm, so voting opens immediately after the PEPs are finalised? No > discussion/debate period before that? Maybe I misunderstood, I'd > assumed that this would be more similar to an election process, with a > period of canvassing support and/or

[python-committers] IMPORTANT: Missing Email Addresses for Governance Election Voter Roll

We need a list of core developers email addresses to send ballot emails to. Since PEP 8001 states that we’re using inclusion in the ``python-core`` team on GitHub as the list of “registered voters”, I wrote up a quick script that compiled a list of GitHub usernames in that team *today* and any p

Re: [python-committers] IMPORTANT: Missing Email Addresses for Governance Election Voter Roll

> On Nov 6, 2018, at 5:14 AM, Nick Coghlan wrote: > > On Tue, 6 Nov 2018 at 08:17, Donald Stufft <mailto:[email protected]>> wrote: >> >> We need a list of core developers email addresses to send ballot emails to. >> Since PEP 8001 states that we’re

Re: [python-committers] 2019 Steering Council Election Results

Did voting require you to select 5 candidates? Or was it up to 5? I don’t recall, but if it was the latter that could explain it. > On Feb 4, 2019, at 11:28 AM, Tim Peters wrote: > > [Ernest W. Durbin III ] >> Of 96 eligible voters, 69 cast ballots. > > FYI, the total number of votes Helios sh

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

> 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 questioning the decision, at least we voted for our > delega

[python-committers] Re: Please make sure you're following good security practices with your GitHub account

> On Jun 14, 2021, at 5:02 PM, Tim Peters wrote: > > [Brett] >> ... >> Please make sure you have a unique password for your GitHub account >> and that you have 2FA/MFA turned on (I honestly think we should start >> requiring this ... > > I use 2FA on sites that cater to my reality ;-) That is,

[python-committers] Re: Please make sure you're following good security practices with your GitHub account

> On Jun 14, 2021, at 5:27 PM, Tim Peters wrote: > > [Donald Stufft ] >> You can a Yubikey for like $15? or so and use that for best in class 2fa. >> >> You can also get an app for your desktop PC that can do TOTP codes >> (1Password has it built in, I’ve nev

Re: [python-committers] Upgrade Donald Stufft to full committer status

dstufft On Oct 24, 2013, at 9:21 AM, Brett Cannon wrote: > > > > On Thu, Oct 24, 2013 at 6:39 AM, Nick Coghlan wrote: > With PEP 453 accepted, could Donald please be upgraded to full > committer access for ensurepip maintenance (the initial PEP 453 > commits will still

Re: [python-committers] PEP 462: Workflow automation for CPython

ommitters mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers Flaky tests have bugs assigned, if a test fails due to a bug you make a comment on the review saying to reverify with the bug number. It let’s t

Re: [python-committers] PEP 462: Workflow automation for CPython

t read past the first part of that, where it said "closes, > throttles and opens the tree" and "tracks down people responsible > for breakage". This is emphatically *not* the Zuul model, from > what Nick has said. In Zull, patches don't get *in* to the tre

Re: [python-committers] new hg.python.org server

e host keys changed, so you'll probably have to futz with >> known_hosts to quiet ssh down. I apologize, but I noticed that that the >> current RSA host key is 1024 bits, so I decided to upgrade it to 2048 >> during the transition. >> >> Thanks to Donald Stufft for helpi

Re: [python-committers] new hg.python.org server

> On Sep 18, 2014, at 4:53 PM, Donald Stufft wrote: > >> >> On Sep 18, 2014, at 10:58 AM, Jesus Cea mailto:[email protected]>> >> wrote: >> >> On 13/09/14 02:34, Benjamin Peterson wrote: >>> I just switched hg.python.org <http://hg.python.org/

Re: [python-committers] Hook error when pushing (5.7.0 Message limit reached)

son it looks like our mailgun account is disabled. It says because we’ve exceded the limit of the plan.. however that limit is 50k and I’m not sure how we’ve managed to exceed that. I’ve filed a ticket with Mailgun and will await further information. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers

[python-committers] Possible "REMOTE HOST IDENTIFICATION HAS CHANGED!" Error.

of those keys are: $ ssh-keygen -lf /etc/ssh/ssh_host_rsa_key.pub 2048 a0:12:52:50:4a:4b:db:43:ac:65:26:b6:6f:0a:f7:b8 /etc/ssh/ssh_host_rsa_key.pub (RSA) $ ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub 256 1d:02:d1:d2:7b:a1:cb:e0:51:65:25:d7:19:dd:4e:74 /etc/ssh/ssh_host_ed25519_key.pub (ED25519) Sorry

Re: [python-committers] Possible "REMOTE HOST IDENTIFICATION HAS CHANGED!" Error.

; how long do I need to wait? > > >> On Tue Jan 20 2015 at 11:55:08 AM Donald Stufft wrote: >> Sending this to python-committers as well for anyone who doesn't keep up with >> python-dev. If you've gotten this message twice now I'm sorry! >> >>

Re: [python-committers] Proposing Paul Moore for commit privileges

+1 > On Mar 14, 2015, at 4:23 PM, Brett Cannon wrote: > > Paul has been participating on python-dev for quite a while, he is a > committer on pip, and (co-)author on 5 PEPs. At this point I think it would > be prudent for Paul to have commit privileges if for any other reason than to > help

Re: [python-committers] [Python-Dev] Do we need to sign Windows files with GnuPG?

ww.egenix.com/ >>>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>>>> mxODBC, mxDateTime, mxTextTools ...http://python.egenix.com/ >> ___

Re: [python-committers] Alternative to SSH port 22?

_ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers It doesn’t currently have another port number available but we could easily add one, we’ll just need to set it up the LBs. --- Donald Stufft PGP: 7C6B 7C5D

Re: [python-committers] PSA: replace your DSA keys for SSH

g access to > send an RSA (min. 1024 bits) or ED25519 key to [email protected]. > > Can we bump up the minimum on RSA keys? 1024 isn’t really enough anymore, ideally they’d be at least 4096 but 2048 is also OK. - Donald Stufft PGP: 0x6E3CBCE93372DCF

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

ogynistic garbage. I’m sure we can figure out how to successfully migrate from Hg to git. I’ve already done it once on the demo repo, if that’s not good enough I’ll work on it some more if need be. ----- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E

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

-worker handed to > me when he went off to Australia for an extended holiday. ;) > It’s pretty easy to migrate the entire history (at least what’s in Hg) including all branches and tags. - Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9

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

I'm not sure that you'd see much savings. You'd only get deltas that were never merged to master excluded. Point taken though. Sent from my iPhone > On Jan 4, 2016, at 4:18 PM, Brett Cannon wrote: > > > >> On Mon, 4 Jan 2016 at 13:14 Donald Stufft wrote: &

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

the end of this year! > >> ___ >> python-committers mailing list >> [email protected] >> https://mail.python.org/mailman/listinfo/python-committers > > ___ > python-committers mail

Re: [python-committers] The peps repo is now on GitHub!

eventing people from pushing directly to the PEP repository, in https://github.com/python/peps/issues/5 there’s talk of setting up Travis to ensure the PEPs are always building and if the flag is set to require a +1 from Travis, then all changes will need to go through PRs. — Donald Stufft ___

Re: [python-committers] The peps repo is now on GitHub!

> On Jun 16, 2016, at 1:38 AM, Barry Warsaw wrote: > > On Jun 15, 2016, at 06:59 PM, Donald Stufft wrote: > >> Currently there’s nothing preventing people from pushing directly to >> the PEP repository, in https://github.com/python/peps/issues/5 there’s >> talk

Re: [python-committers] Temporary moderator needed for Distutils SIG

I can do this. Sent from my iPhone > On Nov 12, 2016, at 5:04 PM, A.M. Kuchling wrote: > > I'm going on vacation starting this Tuesday November 15th, and won't > have much Internet access, and perhaps none at all, until I get back > on November 30th. Could someone please take over moderating

Re: [python-committers] 3.6 branch now open only for 3.6.0 release critical fixes and doc updates!

If we want the version to be PEP 440 compliant it'd be like 3.6rc1.dev0 or so if I remember correctly. Sent from my iPhone > On Nov 22, 2016, at 3:40 PM, Steve Dower wrote: > >> On 22Nov2016 1150, R. David Murray wrote: >> Being who we are (precisionist programmers), the inconsistency between

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

t an FYI, I was talking to a friend in Travis and he suggests in the next few weeks they’re going to get a lot more macOS capacity. We might want to try this again in a few weeks and see if their new capacity is enough that the lead time is good enough.

Re: [python-committers] Discussions on PRs

enting on the issue tracker. — Donald Stufft ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Disable Codecov on GitHub pull requests?

good idea to make deterministic anyways. As with Alex, most projects I’ve been involved in turn off the comments and rely on the status checker. — Donald Stufft ___ python-committers mailing list [email protected] https://mail.python.or

[python-committers] Please Publicize your Github Membership for Python

l see either the word “Private” or “Public”, if it says “Private”, click on it and select “Public” (https://s.caremad.io/MLlxY1W5r0/ <https://s.caremad.io/MLlxY1W5r0/>). That’s all you need to do. Thanks a lot! — Donald Stufft ___ python-commit

Re: [python-committers] Please Publicize your Github Membership for Python

> On Mar 3, 2017, at 2:03 AM, Nick Coghlan wrote: > > On 2 March 2017 at 23:20, Donald Stufft <mailto:[email protected]>> wrote: > Hello! > > Some of our automation needs to be able to determine who is a member of the > Python organization on Github to effe

Re: [python-committers] Please Publicize your Github Membership for Python

e list of the already existing keys. — Donald Stufft ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] 4 weeks with the new workflow: what needs changing?

issue613>. I'm sure Ezio and > Maciej would appreciate any help people may be able to volunteer to help in > solving the problem. > > Fifth, anything I missed? :) > ___ > python-committers mailing list > python-committers@pyt

Re: [python-committers] 4 weeks with the new workflow: what needs changing?

cebook/mention-bot) > > On 11 March 2017 at 00:32, Donald Stufft wrote: >> I’ve found it helpful thus far. It’s poked me on a few issues and I jumped >> in and gave a review on them. There is too much churn in python/cpython for >> me to get notified of every issue. I sus

Re: [python-committers] 4 weeks with the new workflow: what needs changing?

ys basis, or on a “if you couldn’t find enough people through your heuristics” basis). — Donald Stufft ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

  1   2   >