[python-committers] Triage perms for Elvis

At Yuri's request I've given Elvis triage privileges on the tracker. I don't anticipate any objections, given the work he's done on What's New and other things. --David ___ python-committers mailing list python-committers@python.org

Re: [python-committers] 3.7.0b1 status

On Wed, 31 Jan 2018 03:17:47 -0500, Ned Deily wrote: > in not more than 24 hours from now. If you wish, feel free to merge > new commits into the master branch for release in 3.8, with the > understanding that any also destined for 3.7.0 will need to be > cherrypicked after the

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

On Mon, 11 Dec 2017 14:56:21 -0500, Donald Stufft <don...@stufft.io> wrote: > > > On Dec 11, 2017, at 2:52 PM, R. David Murray <rdmur...@bitdance.com> wrote: > > > > If 2fa is required for contribution to CPython, I'll stop > > contributing. >

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

On Mon, 11 Dec 2017 14:52:54 -0500, "R. David Murray" <rdmur...@bitdance.com> wrote: > Indeed. If 2fa is required for contribution to CPython, I'll stop > contributing. Granted, I haven't done many merges lately, but a few > is a bigger number than zero :) And in ca

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

On Mon, 11 Dec 2017 18:14:41 +, Paul Moore wrote: > On 11 December 2017 at 18:03, Donald Stufft wrote: > > So yea, it’s not as good as 2FA only everywhere, but the specific > > circumstances around these specific credentials makes it a reasonable > >

Re: [python-committers] Mentoring Julien Palard (core), Cheryl Sabella (bug) and Sanyam Khurana (bug)

On Sat, 09 Dec 2017 14:12:52 +0100, Victor Stinner wrote: > I asked them to ask me to double check before merging a pull request > (Julien) or closing a bug (Cheryl and Sanyam). When I have promoted people to triage in the past I have not had them check with me before

Re: [python-committers] Official python-dev docker images

On Thu, 07 Dec 2017 13:00:31 -0500, Barry Warsaw wrote: > Brett and I want to promote this more widely within the Python > community as the “official Python Docker image” that projects can use > in their own testing environments, or base their own images on it. We > wanted

Re: [python-committers] Requirements to get the "bug triage" permission?

On Wed, 06 Dec 2017 18:11:44 +0100, Victor Stinner wrote: > Ok, thanks Ezio and David. I completed my list: > https://github.com/vstinner/cpython_core_tutorial/blob/master/core_developer.rst#bug-tracker s/loose/lose/ I would say your list comprises the skills for the

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

On Wed, 06 Dec 2017 08:43:56 -0800, Guido van Rossum wrote: > I think I figured it out -- I invited him to the python org on GitHub. > Anything else? He needs to subscribe to this mailing list, and the developers.rst in the devguide repo should get an update. That's all I can

Re: [python-committers] Requirements to get the "bug triage" permission?

On Mon, 20 Nov 2017 18:54:50 +0100, Victor Stinner wrote: > I identified some active contributors and I would like to offer them > to get the "bug triage" permission. What's the requirements to give > such permissions to someone? Currently it is "someone with the power

Re: [python-committers] Enabling depreciation warnings feature code cutoff

On Mon, 06 Nov 2017 13:25:09 -0600, Neil Schemenauer <nas-pyt...@arctrix.com> wrote: > On 2017-11-06, R. David Murray wrote: > > I'm curious which ones you are seeing it in? It could be we are > > operating in different problem spaces :) > > In the last few months:

Re: [python-committers] Enabling depreciation warnings feature code cutoff

On Mon, 06 Nov 2017 12:51:45 -0600, Neil Schemenauer wrote: > Another idea is to have venv to turn them on by default or, based on > a command-line option, do it. Or, maybe the unit testing frameworks > should turn on the warnings when they run. Unit test frameworks,

Re: [python-committers] [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff

On Mon, 06 Nov 2017 11:46:48 +1000, Nick Coghlan wrote: > On 6 November 2017 at 02:02, Yury Selivanov wrote: > > On Fri, Nov 3, 2017 at 11:30 PM, Nick Coghlan wrote: > >> The current lack of DeprecationWarnings in 3.6 is a fairly

Re: [python-committers] Requesting reviews

On Fri, 06 Oct 2017 09:09:01 -0700, Mariatta Wijaya wrote: > The windows team is notified because the PR includes changes to PCBuild/* If you get a review request that says your review was requested "as a code owner", then it was an auto-request, it wasn't actually

[python-committers] I just gave Gareth Rees traige privileges on the tracker

I haven't actually heard back from him yet since I just emailed him, but I've never had anyone turn down triage privs :) The trigger was that I closed two issues this week that he comment on that it would have been nice if he had been able to just close himself. I've looked at some of his other

Re: [python-committers] Dismiss review if a PR is modified

On Tue, 18 Jul 2017 23:13:41 -, Brett Cannon wrote: > Do realize that setting is part of requiring a review for pull requests: > https://help.github.com/articles/enabling-required-reviews-for-pull-requests/. > So in order to get this we would require all PRs, core dev or

Re: [python-committers] My (positive) feedback on the new CPython workflow

On Tue, 18 Jul 2017 12:24:13 +0200, Victor Stinner wrote: > I'm just not unconfortable with the fact that an approval is kept even > if the PR is modified after the review :-/ I would expect a list a > notice "changed modified after the review" or something like that.

Re: [python-committers] link from github to bpo?

On Sat, 24 Jun 2017 00:33:13 -, Brett Cannon <br...@python.org> wrote: > On Fri, 23 Jun 2017 at 09:28 R. David Murray <rdmur...@bitdance.com> wrote: > > > On Wed, 21 Jun 2017 13:37:22 -0700, Mariatta Wijaya < > > mariatta.wij...@gmail.com> wrote: > >

Re: [python-committers] link from github to bpo?

On Wed, 21 Jun 2017 10:02:58 -0700, Mariatta Wijaya wrote: > Yes, for that PR, scroll down and click the "View Details" button. > Click the Details link next to bedevere/issue number status check. > It will take you to the issue in bpo. Note that this will only exist

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

On Thu, 15 Jun 2017 13:31:39 +1000, Nick Coghlan wrote: > On 15 June 2017 at 00:40, Victor Stinner wrote: > > So I would like to set a new rule: if I'm unable to fix buildbots > > failures caused by a recent change quickly (say, in less than 2 > >

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

+1 --David ___ 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] Feedback on the new CPython workflow

On Wed, 17 May 2017 11:35:29 -0700, Mariatta Wijaya wrote: > It's possible, but remember not all PRs have bpo-issue, eg those with > trivial label. > In that case, what should the backport branch be? > So we might end up with two backport branch name patterns, eg >

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

On Thu, 04 May 2017 17:44:46 -, Brett Cannon wrote: > (And just so I can claim I stated this publicly at some point; our Roundup > installation I think runs on Python 2.6 and Roundup itself has not been > ported to Python 3, so I don't know what we want to do if Roundup

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

On Tue, 02 May 2017 09:36:02 +0200, "M.-A. Lemburg" wrote: > On 02.05.2017 04:25, Nick Coghlan wrote: > > On 2 May 2017 at 08:32, Christian Heimes wrote: > >> This brings me to my questions > >> > >> 1) Should we try to move discussion back to BPO or are we

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

On Mon, 10 Apr 2017 21:53:44 -0700, Guido van Rossum wrote: > - When the contributor makes multiple local commits without pushing to the > PR, I recommend using --amend unless they have several commits that > actually are logically distinct and relevant to the reviewer. (--amend

Re: [python-committers] I have blocked Wes Turner from the Python org on GitHub

On Sat, 01 Apr 2017 15:08:27 -0400, Alex Gaynor wrote: > I'll be another voice saying that the CoC isn't the right mechanism -- the > CoC is for harassment and abuse (at least, most community's CoCs are, the > Python one is pretty vague). > > That said, I have no problem

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

On Fri, 24 Mar 2017 14:29:13 +0100, Antoine Pitrou wrote: > > By the way, how do I fetch remote changes for a branch without pulling > it into the working copy? e.g. I'd like to do "git fetch origin 3.5" or > "git fetch origin/3.5", but that doesn't seem to work... "git

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

On Wed, 15 Mar 2017 22:56:33 -0400, Yury Selivanov wrote: > It's not just long waiting times (although it's a huge factor), it's > that you have to create temporary branches for cherry-picks. With > scripts or without, it's a lot of bookkeeping. Also, interacting with

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

On Mon, 13 Mar 2017 12:48:30 -0400, Yury Selivanov wrote: > Yesterday I was working on a few asyncio PRs and a bug in async/await. > All PRs required cherry-picking. Again, I was spending significant > amount of time just creating branches/PRs for cherry-picking.

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

On Sun, 12 Mar 2017 11:37:21 -, Paul Moore wrote: > I don't have a problem with the new "PRs attached to this issue" field > - that's of course important to have. But is there any way to not have > them generate emails (probably on a per-user basis, as I'm sure > there's

Re: [python-committers] New ncoghlan-bpo-29537-NEWS branch?

On Thu, 09 Mar 2017 18:32:13 +, Brett Cannon wrote: > On Thu, 9 Mar 2017 at 04:07 Nick Coghlan wrote: > > > On 9 March 2017 at 19:30, Victor Stinner wrote: > > > > Do we need need a kind of sandbox repository for experiments?

Re: [python-committers] autoconf 2.70

On Thu, 24 Nov 2016 12:22:00 +0100, Victor Stinner wrote: > I know that tracking generated files is not pure, but it's very > convenient, so please keep them: configure, Python/importlib.h, > Python/importlib_external.h, etc.! > > When testing Python on some "custom"

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

On Tue, 22 Nov 2016 13:47:35 -0500, Ned Deily wrote: > On Nov 22, 2016, at 12:59, Brett Cannon wrote: > > I think for me what made everything click was realizing that we used > > to say "until rc1 is cut, treat it as the beta phase", while Ned is > > saying

Re: [python-committers] 3.6.0 Beta Phase Development

- python-dev On Mon, 12 Sep 2016 20:15:06 -0400, Ned Deily wrote: > 2016-12-04 3.6.0 release candidate 1 (3.6.0 code freeze) > > 2016-12-16 3.6.0 release (3.6.0rc1 plus, if necessary, any dire emergency > fixes) IMO, if any dire emergency fixes are necessary there should be

Re: [python-committers] Is it just me or is the tip broken at the moment?

On Thu, 07 Jul 2016 11:15:29 -0500, Zachary Ware wrote: > On Thu, Jul 7, 2016 at 11:03 AM, Steven D'Aprano wrote: > > I'm wondering if I've broken something at my end, or if everyone is > > seeing the same error. > > Works fine for me. Have

Re: [python-committers] [Python-Dev] [RELEASED] Python 3.4.5 andPython 3.5.2 are now available

On Mon, 27 Jun 2016 12:51:07 -0700, Steve Dower wrote: > I hoped by informing the lists we'll be able to address concerns as > they come up, but I'd rather not have a semi-permanent instruction to > ignore a virus scanner :) Good point. I actually thought about that a

Re: [python-committers] [Python-Dev] [RELEASED] Python 3.4.5 and Python 3.5.2 are now available

On Mon, 27 Jun 2016 08:25:40 -0700, Steve Dower wrote: > On 26Jun2016 1932, Larry Hastings wrote: > > https://www.python.org/downloads/release/python-352/ > > ... > > /p.s. There appears to be a small oops with the Windows installers for > > 3.5.2--uploaded to the wrong

Re: [python-committers] bugs.python.org, job status, and contributors (aka not core devs)

On Mon, 06 Jun 2016 20:25:22 +0300, =?UTF-8?Q?Berker_Peksa=C4=9F?= wrote: > On Mon, Jun 6, 2016 at 7:41 PM, Ethan Furman wrote: > > Question: I noticed a couple issues on b.p.o that were being closed by > > contributors (not core-devs, not their own

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

I don't understand how it happened, but apparently I got a merge commit backward and merged 3.6 into 3.5 and pushed it without realizing what had happened. If anyone has any clue how to reverse this cleanly, please let me know. (There are a couple people at the sprints looking in to it, but the

Re: [python-committers] Promote Xavier de Gaye as a core developer

On Tue, 24 May 2016 17:28:00 +0200, Victor Stinner <victor.stin...@gmail.com> wrote: > 2016-05-24 15:42 GMT+02:00 R. David Murray <rdmur...@bitdance.com>: > > PS: with respect to Victor's script wish, one of the reasons I'm suggesting > > paul.j3 is that very f

Re: [python-committers] Promote Xavier de Gaye as a core developer

On Tue, 24 May 2016 00:22:07 -0400, Ned Deily <n...@python.org> wrote: > In article <20160523174004.cb04eb14...@webabinitio.net>, > "R. David Murray" <rdmur...@bitdance.com> wrote: > > +1 from me as well. I'd just put him on my shortlist of people to >

Re: [python-committers] Promote Xavier de Gaye as a core developer

On Sun, 22 May 2016 14:23:08 +0200, Victor Stinner wrote: > 2016-05-22 11:42 GMT+02:00 Stefan Krah : > > +1. The Android patches are very good -- he would be the ideal maintainer. > > The Android work looks to become something serious. To make the

Re: [python-committers] Making the PSF CoC apply to core developers

On Fri, 04 Mar 2016 21:31:44 +, Brett Cannon wrote: > I guess I'm just worried about the health of this project. I'm doing what I > can through the migration to GitHub to make it easier for others to get > involved while making it easier for us to accept the work of others,

Re: [python-committers] Making the PSF CoC apply to core developers

On Fri, 04 Mar 2016 21:31:44 +, Brett Cannon wrote: > The discussion about the Code of Conduct has sputtered out, so I'm going to > assume those who care to speak up have at this point. It seems to me that > the general agreement is that putting python-dev and

Re: [python-committers] Making the PSF CoC apply to core developers

On Tue, 01 Mar 2016 19:00:21 +, Brett Cannon wrote: > I don't want this discussion to drag on forever as CoC discussions tend to, Agreed, I made my point and don't otherwise feel a need to engage in further discussion. Unless someone pushes one of my buttons, I suppose :)

Re: [python-committers] Making the PSF CoC apply to core developers

On Tue, 01 Mar 2016 04:10:08 +, Brett Cannon wrote: > On Mon, 29 Feb 2016 at 18:01 Steven D'Aprano wrote: > > So let me make it clear: Brett, and the other list maintainers, you're > > not listening. Even if I'm a minority of one out of the whole

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

On Mon, 04 Jan 2016 18:18:02 +, Brett Cannon wrote: > On Mon, 4 Jan 2016 at 09:50 Eli Bendersky wrote: > > > > I have to admit that I'm not a big expert on Mercurial --> Git converters > > and the way I maintain this mirror may not be the best approach, so

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

On Tue, 05 Jan 2016 01:26:58 +, "Gregory P. Smith" <g...@krypto.org> wrote: > On Mon, Jan 4, 2016 at 12:34 PM R. David Murray <rdmur...@bitdance.com> > wrote: > > > to have to do some extra work to make the hash links work in the bug > > tracker, s

Re: [python-committers] Committer missing :)

On the other hand, docs.python.org/devguide/developers.html still will (and does). On Sun, 06 Dec 2015 17:09:25 -0800, Benjamin Peterson wrote: > Indeed, if you have no keys around, the (automatically generated) > committers.txt file will not list you. > > > On Sun, Dec

Re: [python-committers] New installed Python builders

On Mon, 23 Nov 2015 19:11:15 +0200, Serhiy Storchaka <storch...@gmail.com> wrote: > On 23.11.15 18:00, R. David Murray wrote: > > On Mon, 23 Nov 2015 00:58:01 -0600, Zachary Ware > > <zachary.ware+py...@gmail.com> wrote: > > I haven't looked at this, but unless t

Re: [python-committers] Python 3.6 Release Schedule Details

On Thu, 01 Oct 2015 22:24:18 -0400, Ned Deily wrote: > Another change has been to add a fourth beta and drop the third > release candidate. My gut feeling from the past several releases is > that a lot of feature code does not get checked in until close to the > b1 feature code

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

On Sun, 16 Aug 2015 11:24:32 -0400, R. David Murray rdmur...@bitdance.com wrote: On Sun, 16 Aug 2015 00:13:10 -0700, Larry Hastings la...@hastings.org wrote: 3. After your push request is merged, you pull from bitbucket.com/larry/cpython350 into hg.python.org/cpython and merge

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

On Sun, 16 Aug 2015 00:13:10 -0700, Larry Hastings la...@hastings.org wrote: So far I've accepted two pull requests into bitbucket.com/larry/cpython350 in the 3.5 branch, what will become 3.5.0rc2. As usual, it's the contributor's responsibility to merge forward; if their checkin goes

Re: [python-committers] A possible solution to the Misc/NEWS merging problem

On Tue, 11 Aug 2015 14:58:45 +1200, Robert Collins robe...@robertcollins.net wrote: On 11 August 2015 at 10:38, Brett Cannon bcan...@gmail.com wrote: We have all been there: you fix something in some maintenance branch, do your `hg pull` into the default branch, and everything but Misc/NEWS

Re: [python-committers] Having issues updating a checkout

According to the infrastructure list/#python-infra, there is currently some instability in the load balancers. That is probably the source of these errors. On Sun, 09 Aug 2015 14:45:27 -0400, Ned Deily n...@acm.org wrote: On Aug 9, 2015, at 14:19, Brett Cannon bcan...@gmail.com wrote:

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

On Wed, 29 Jul 2015 13:41:09 -0400, Terry Reedy tjre...@udel.edu wrote: On 7/29/2015 1:01 PM, Robert Collins wrote: On 30 July 2015 at 04:50, Guido van Rossum gu...@python.org wrote: I believe that in this particular case, the bug was fixed (by tightening the requirements for headers)

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

On Thu, 30 Jul 2015 00:11:53 +0200, Jesus Cea j...@jcea.es wrote: On 29/07/15 18:50, Guido van Rossum wrote: I believe that in this particular case, the bug was fixed (by tightening the requirements for headers) because the bug can lead to security vulnerabilities. I think you can find more

[python-committers] Speaking of noticing tracker activity

In the recent thread on python-dev Nick mentioned our dependence on people noticing active contributors on the tracker. In that regard I'd like to recommend people take a look at the work of Martin Panter (vadmium). --David ___ python-committers

Re: [python-committers] Code review tool 500 error

On Wed, 13 May 2015 15:43:17 -0400, Yury Selivanov yselivanov...@gmail.com wrote: I can't post messages to the code review tool -- it shows me 500 error page. Are you doing it from the front page? I think that doesn't work. In-line comments plus publish comments does work. --David

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

On Thu, 02 Apr 2015 09:31:08 -0700, Guido van Rossum gu...@python.org wrote: Where I come from we always squash. More detailed history is preserved in the code review tool (which keeps a snapshot every time you bounce it back to the reviewer). Looking at my own sub-commits when I'm working on a

[python-committers] cherry picking after rc

Larry, saw your discussion on IRC with Georg about what to cherry pick into the release clone before issuing final. IMO you shouldn't cherry pick anything, since I believe there have been *zero* issues opened that said that the RC was broken. IMO the only differences between the last RC and

Re: [python-committers] Mark Lawrence

On Sun, 05 Oct 2014 14:47:06 -0400, Benjamin Peterson benja...@python.org wrote: On Sun, Oct 5, 2014, at 14:42, Serhiy Storchaka wrote: On 05.10.14 21:15, Benjamin Peterson wrote: BreamoreBoy is back on tracker touching hundreds of issues without adding any new information. This is

Re: [python-committers] [Python-Dev] [RELEASE] Python 3.4.2rc1 is now available

(Trimmed CC) I couldn't reproduce this, nor did I see it in any of the stable buildbots when Larry reported he had an issue with it. Now that he's pushed his branch, the buildbots are red with it. So...Larry broke it, but it is not obvious how. Could it be something wrong with the pydoc topics

Re: [python-committers] Proposing Berker Peksag for push privileges

I have emailed Berker to (among other things) send in his keys and introduce himself here after signing up. --David ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

[python-committers] Proposing Berker Peksag for push privileges

I'd like to propose that we give Berker Peksag push privileges. He's provided a number of good quality patches and done good review work on other issues, and has been an active contributor for quite some time. IMO we've reached the point where it will be easier to let him push patches. (We've

Re: [python-committers] Small change to tracker 'resolution'

On Tue, 15 Apr 2014 23:21:41 -0400, Terry Reedy tjre...@udel.edu wrote: On 4/15/2014 9:45 PM, Ethan Furman wrote: On 04/15/2014 05:55 PM, R. David Murray wrote: [...] I've changed the text associated with the 'invalid' resolution to read 'not a bug' [...] Nice. Any chance

[python-committers] New mailing list for workflow/workflow infrastructure discussion/tasks

Apologies for the cross post, but I want to make sure committers who aren't reading python-dev for one reason or another see this: Based on a number of conversations at PyCon, we've created a new mailing list: https://mail.python.org/mailman/listinfo/core-workflow The purpose of this list

Re: [python-committers] New mailing list for workflow/workflow infrastructure discussion/tasks

On Wed, 16 Apr 2014 18:02:31 -0400, Terry Reedy tjre...@udel.edu wrote: On 4/16/2014 4:49 PM, R. David Murray wrote: Apologies for the cross post, but I want to make sure committers who aren't reading python-dev for one reason or another see this: Based on a number of conversations

[python-committers] Small change to tracker 'resolution'

In a discussion at the sprints today Nick observed that 'invalid' was a resolution that carried a rather negative subtext (your bug report was invalid, ie: you made a mistake) , and that Red Hat used 'not a bug', which we all agreed was much more descriptive of the actual resolution. So, I've

Re: [python-committers] [RELEASED] Python 3.4.0 release candidate 1

On Tue, 11 Feb 2014 01:01:38 -0800, Ethan Furman et...@stoneleaf.us wrote: On 02/10/2014 11:43 PM, Larry Hastings wrote: On behalf of the Python development team, I'm delighted to announce the first release candidate of Python 3.4. Yay!! Question: Now that we are in the RC phases,

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

On Sat, 25 Jan 2014 09:35:46 -0800, Eli Bendersky eli...@gmail.com wrote: On Sat, Jan 25, 2014 at 7:13 AM, R. David Murray rdmur...@bitdance.comwrote: On Sat, 25 Jan 2014 06:59:19 -0800, Eli Bendersky eli...@gmail.com wrote: workplace we had a similar process screwed on top of Jenkins

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

On Sat, 25 Jan 2014 05:49:56 -0800, Eli Bendersky eli...@gmail.com wrote: do the latter in Python, which carries a problem we'll probably need to resolve first - how to know that the bots are green enough. That really needs human attention. By that needs human attention, do you mean: dealing

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

On Sat, 25 Jan 2014 06:35:59 -0800, Eli Bendersky eli...@gmail.com wrote: On Sat, Jan 25, 2014 at 6:14 AM, R. David Murray rdmur...@bitdance.comwrote: On Sat, 25 Jan 2014 05:49:56 -0800, Eli Bendersky eli...@gmail.com wrote: do the latter in Python, which carries a problem we'll probably

Re: [python-committers] 3.4 beta releases and the tracker

On Mon, 02 Dec 2013 17:59:15 -0500, Terry Reedy tjre...@udel.edu wrote: On 12/2/2013 5:54 PM, Ethan Furman wrote: Is there an easy way to focus on tracker issues that can be worked on now that feature-freeze is in effect? Search (default) Status: open for Type: behavior or Components:

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

On Sun, 01 Dec 2013 18:11:47 +0100, mar...@v.loewis.de wrote: Quoting R. David Murray rdmur...@bitdance.com: On the other hand, I'm not actually sure what kind of access is left when you remove all the roles from a user. I did notice the other day that email to the tracker still seems

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

On Sun, 01 Dec 2013 12:12:08 +1000, Nick Coghlan ncogh...@gmail.com wrote: I don't appear to have the necessary tracker access to actually move his account to read-only status, though (this change should be made on the meta-tracker as well). You should have the necessary privileges on the

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

On Fri, 29 Nov 2013 13:16:32 -0800, Ned Deily n...@acm.org wrote: On Nov 29, 2013, at 12:12 , Guido van Rossum gu...@python.org wrote: The question is, how effective will the alternative solution (banning him) be? I worry that it's just going to make things worse. I think that is a

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

On Fri, 29 Nov 2013 14:41:22 -0800, Ned Deily n...@acm.org wrote: On Nov 29, 2013, at 13:51 , Antoine Pitrou anto...@python.org wrote: On ven., 2013-11-29 at 13:16 -0800, Ned Deily wrote: Why is it that we find him so annoying, enough to advocate fairly drastic measures like banning?

Re: [python-committers] Your buildbots are out of memory

On Thu, 24 Oct 2013 10:12:07 -0400, Brett Cannon br...@yvrsfo.ca wrote: FYI if you didn't know You mean disk space? I don't get notified automatically when /tmp fills up with test detritus. I suppose I should set something up. However, it looks like someone has added some tests that use more

Re: [python-committers] Your buildbots are out of memory

On Thu, 24 Oct 2013 17:08:11 +0200, Antoine Pitrou anto...@python.org wrote: On 2013-10-24 16:59, R. David Murray wrote: However, it looks like someone has added some tests that use more tmp space, since the amount of /tmp that exist has been fine up until this point, and the runs

Re: [python-committers] Reminder: Python 3.4 alpha 1 release is Saturday August 3

On Thu, 25 Jul 2013 13:07:59 -0700, Larry Hastings la...@hastings.org wrote: It's about nine days from now. I expect to tag the release late next week. So if you're doing any major brain surgery, please finish it up in the next week or so. FYI I'm planning on working on some non-trivial

Re: [python-committers] [Infrastructure] [Pydotorg] XSS security issue

On Mon, 15 Jul 2013 11:09:08 +0300, Michael Foord mich...@voidspace.org.uk wrote: On 15 Jul 2013, at 11:05, M.-A. Lemburg m...@python.org wrote: Who would be the one to contact for issues like these ? The case is rather urgent, since the XSS can be used for stealing session cookies

Re: [python-committers] [Infrastructure] [Pydotorg] XSS security issue

On Mon, 15 Jul 2013 08:22:40 -0400, Donald Stufft don...@stufft.io wrote: So I was able to log in to the nobody account without a password (Why is this even possible?). It gave me powers to edit users and some other shit. I added a password to the nobody account since these lists are publicly

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

On Sat, 22 Jun 2013 15:35:41 -0400, Barry Warsaw ba...@python.org wrote: On Jun 22, 2013, at 12:02 PM, Eli Bendersky wrote: I may be missing something, but do we have a policy of what we're supposed to commit to the 2.7 branch at this point? I was under the impression that it's only bug

Re: [python-committers] what's going on with Misc/NEWS?

On Fri, 24 May 2013 18:39:16 +0200, Antoine Pitrou solip...@pitrou.net wrote: Brett wrote: Of course, we've talked about doing something like this before, it's just never irritated anyone enough for them to sit down and *write* the associated NEWS file generator, or the code to split the

Re: [python-committers] what's going on with Misc/NEWS?

On Fri, 24 May 2013 15:26:29 -0400, Brett Cannon br...@python.org wrote: On Fri, May 24, 2013 at 2:27 PM, Antoine Pitrou solip...@pitrou.net wrote: Le vendredi 24 mai 2013 à 14:23 -0400, Brett Cannon a écrit : You'll have to copy stuff by hand, though, if you don't want to rely on the

Re: [python-committers] what's going on with Misc/NEWS?

On Fri, 24 May 2013 15:16:24 -0600, Gregory P. Smith g...@krypto.org wrote: On May 24, 2013 2:55 PM, Antoine Pitrou solip...@pitrou.net wrote: Le vendredi 24 mai 2013 à 16:22 -0400, Brett Cannon a écrit : I don't understand why it's painful to backport. Can you explain? If I

Re: [python-committers] Please don't commit to 3.2 branch anymore

On Sat, 30 Mar 2013 13:41:39 +0100, Jesus Cea j...@jcea.es wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28/03/13 08:55, Georg Brandl wrote: with 3.2.4 being the last regular 3.2 maintenance release and the rc out of the door, the 3.2 branch should only be committed to for

Re: [python-committers] SSH fingerprint

Note that I believe ECDSA is now the default for host keys for OpenSSH. At the least, my systems (Gentoo) switched to them after an upgrade a a bit a go. --David On Mon, 25 Mar 2013 13:29:48 +0100, Christian Heimes christ...@python.org wrote: Am 25.03.2013 05:51, schrieb Jeffrey Yasskin: You

Re: [python-committers] [Infrastructure] test suite dependencies on www.python.org

On Wed, 20 Mar 2013 12:47:09 -0700, Noah Kantrowitz n...@coderanger.net wrote: +1 on let them break, but when they get fixed it should be against a dedicated testing endpoint if possible, preferably something internal to the test suite. Maybe spawn an HTTP server in a background thread/proc? I

Re: [python-committers] Commit privileges for Roger Serwy for IDLE

+1 ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] [Infrastructure] test suite dependencies on www.python.org

On Mon, 18 Mar 2013 15:17:23 -0700, Noah Kantrowitz n...@coderanger.net wrote: As part of the PyCon sprints I would like to move python.org off dinsdale to a VM at OSL. Due to the build system being tied to SVN, I'll also migrate that service on the same VM. Do any SVN repos other than www/

Re: [python-committers] Tracker settings for Peter Moody

On Sat, 16 Mar 2013 15:25:56 +0100, Georg Brandl g.bra...@gmx.net wrote: Am 16.03.2013 15:01, schrieb Nick Coghlan: Could someone with sufficient privileges please flip Peter Moody's commit bit in the tracker: http://bugs.python.org/user9293 Done. Reminder to everyone else: if you have

Re: [python-committers] echosign

On Mon, 04 Mar 2013 10:29:23 -0500, Jesse Noller jnol...@gmail.com wrote: On Monday, March 4, 2013 at 10:24 AM, R. David Murray wrote: I applaud the foundation for getting an electronic signature method in place. However, I have to say that to my mind echosign is nothing more than

Re: [python-committers] echosign

My apologies for sounding a sour note, by the way, I think I was unduly influenced by my previous (very poor, from a UI perspective) experience with a system like this, and had a knee-jerk reaction. I think it is great that this system has been put in place, and my thanks to all involved.

Re: [python-committers] echosign

On Mon, 04 Mar 2013 10:58:57 -0500, Jesse Noller jnol...@gmail.com wrote: On Monday, March 4, 2013 at 10:55 AM, Antoine Pitrou wrote: My apologies for sounding a sour note, by the way, I think I was unduly influenced by my previous (very poor, from a UI perspective) experience with a

Re: [python-committers] WANTED: leader for the core sprint at PyCon US (was: I will NOT be leading the core sprint at PyCon US this year)

On Tue, 26 Feb 2013 12:43:04 -0500, Brett Cannon br...@python.org wrote: On Tue, Feb 26, 2013 at 12:16 PM, Guido van Rossum gu...@python.org wrote: So we have nobody to lead the core sprint? ATM no. Maybe we should change the subject to WANTED: core dev sprint leader for PyCon ?

Re: [python-committers] PyCon US 2013 attendees

I'll be there the whole time (summit through the end of the sprints). --David ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Contributor Agreement - David Lam

On Mon, 28 Jan 2013 12:53:10 -0500, Kurt B. Kaiser k...@shore.net wrote: We received a contributor agreement by postal mail David Lam 211 E. Meadow Dr Palo Alto CA 94306 d...@dlam.me I've added it to the local paper files I've updated his tracker entry to reflect receiving the form as

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

On Wed, 26 Dec 2012 02:36:08 -0500, Terry Reedy tjre...@udel.edu wrote: This is a continuation of my answer to Christian On 12/25/2012 5:56 PM, Łukasz Langa wrote: 1. Communicate what happened clearly and openly to our community. I am not sure how broadly you mean 'our community', but

  1   2   >