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
https://mail.python.o
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 3.7 branch is avai
On Mon, 11 Dec 2017 14:56:21 -0500, Donald Stufft wrote:
>
> > 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
On Mon, 11 Dec 2017 14:52:54 -0500, "R. David Murray"
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 case you think this me
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
> > usability trade off to allow them.
>
>
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 making changes, but instead
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 to give you guys a
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 "ideal triager" rather
than
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 think of, since ssh
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 to do it decides to give i
On Mon, 06 Nov 2017 13:25:09 -0600, Neil Schemenauer
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: Pillow, docutils, dateu
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, including at least unittest
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 major
> >> oversight/bug, though:
> >
> > There's no oversight. W
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 requested
by the person named
A link to a possibly-interesting-in-this-context project was just posted
to the pmem mailing list:
https://arrow.apache.org/
This is a standard for communicating data structures between processes
with zero-copy semantics, and is backed by the person who created Python
Pandas. I thought Davin
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 tr
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 not, to
> receive an a
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. At
> least, for my own revie
On Sat, 24 Jun 2017 00:33:13 -, Brett Cannon wrote:
> On Fri, 23 Jun 2017 at 09:28 R. David Murray wrote:
>
> > On Wed, 21 Jun 2017 13:37:22 -0700, Mariatta Wijaya <
> > mariatta.wij...@gmail.com> wrote:
> > > PR 2304 is merged. "View Details&
On Wed, 21 Jun 2017 13:37:22 -0700, Mariatta Wijaya
wrote:
> PR 2304 is merged. "View Details" still exists (scroll all the way down).
>
> When the PR is not yet merged (e.g.
> https://github.com/python/cpython/pull/2316), the UI looks different.
> Click 'Show all checks' to get the link back to
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 if the PR is still open (not
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
> > hours), I propose to revert the change.
>
> I'm
+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/
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
> `backport-bpo--` and `backp
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 doesn't
> make the swit
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 fine with
> >> having major decisions j
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 is
> especially im
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 with the action taken, ba
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 fetch origin 3.5" seems
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 a
> console is still much
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. Again
> waiting for CI chec
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 people who appreciate
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?
> >
> >
> > Mine aren't experiments, they're temporary branches f
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" operating systems, I alread
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 "since b4 is the last beta, we are now
On Tue, 22 Nov 2016 02:24:37 -0500, Ned Deily wrote:
> On Nov 22, 2016, at 02:02, Ned Deily wrote:
> > On behalf of the Python development community and the Python 3.6 release
> > team, I'm pleased to announce the availability of Python 3.6.0b4. 3.6.0b4
> > is the last planned beta release of Pyt
- 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 an rc2,
which then
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 you rebuilt since pulling? If a simple
> 'make' does
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 few hours after I sent
the
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 directory or something. Th
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 issues).
> >
> > Should non-core-devs be clos
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 m
On Tue, 24 May 2016 17:28:00 +0200, Victor Stinner
wrote:
> 2016-05-24 15:42 GMT+02:00 R. David Murray :
> > PS: with respect to Victor's script wish, one of the reasons I'm suggesting
> > paul.j3 is that very few of his patches have been committed, and they
> > sh
On Tue, 24 May 2016 00:22:07 -0400, Ned Deily wrote:
> In article <20160523174004.cb04eb14...@webabinitio.net>,
> "R. David Murray" wrote:
> > +1 from me as well. I'd just put him on my shortlist of people to
> > consider. I haven't gone over his
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
> Android support official, we need a buildbot,
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, but
> the maintenan
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 bugs.python.org under
> the CoC m
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 :)
> Now obviously I
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 community,
> > your words say "of course we ca
On Tue, 02 Feb 2016 15:33:58 +0200, Ezio Melotti wrote:
> On Sat, Jan 30, 2016 at 5:36 AM, Guido van Rossum wrote:
> > Following the lead of 2.7.10 and 2.7.11 we could continue with 3.10, 3.11,
> > etc.
> >
>
> I think we should continue with 3.10, 3.11, etc.
> Changing the major version should
On Tue, 05 Jan 2016 01:26:58 +, "Gregory P. Smith" wrote:
> On Mon, Jan 4, 2016 at 12:34 PM R. David Murray
> wrote:
>
> > to have to do some extra work to make the hash links work in the bug
> > tracker, since I don't think there's any a priori way
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 I
> > encourage you folks to find a
On Fri, 11 Dec 2015 22:50:12 +0100, Jesus Cea wrote:
> After sending my new SSH key I have recovered "push" abilities in the
> mercurial repository, but it looks like I am not present in the bug
> tracker "assigned to" field.
I see jcea there.
--David
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 6, 2015, at 17:05, Jesu
On Mon, 23 Nov 2015 19:11:15 +0200, Serhiy Storchaka
wrote:
> On 23.11.15 18:00, R. David Murray wrote:
> > On Mon, 23 Nov 2015 00:58:01 -0600, Zachary Ware
> > wrote:
> > I haven't looked at this, but unless the buildbot does *not* have write
> > access to th
On Mon, 23 Nov 2015 00:58:01 -0600, Zachary Ware
wrote:
> Hi,
>
> Inspired by a couple of issues about testing installed Python that
> popped up this morning (#25694 and #25696), I've set up a new set of
> builders[1] to build, install, and test the installed Python. They
> run on the same slav
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 cutoff so that ext
On Sun, 16 Aug 2015 11:24:32 -0400, "R. David Murray"
wrote:
> On Sun, 16 Aug 2015 00:13:10 -0700, Larry Hastings wrote:
> > 3. After your push request is merged, you pull from
> > bitbucket.com/larry/cpython350 into hg.python.org/cpython and merge
> >
The 3.5.0 patch flow question also brings up the question of how we
are managing NEWS for 3.5.0 vs 3.5.1. We have some commits that
are going in to both 3.5.0a2 and 3.5.1, and some that are only going
in to 3.5.1. Currently the 3.5.1 NEWS says things are going in to
3.5.0a2, but that's obviously
On Sun, 16 Aug 2015 00:13:10 -0700, Larry Hastings 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 in to 3.5, it
On Tue, 11 Aug 2015 14:58:45 +1200, Robert Collins
wrote:
> On 11 August 2015 at 10:38, Brett Cannon 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 merges
> > cleanly. You typically reve
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 wrote:
> > On Aug 9, 2015, at 14:19, Brett Cannon wrote:
> >
> > Anyone else seeing this?
>
FYI I just granted Developer privs on the tracker to eryksun (real name
unknown), after wondering why s/he hadn't just closed an issue s/he
commented on and thereby finding s/he didn't have them yet.
Someone to keep an eye on, IMO.
--David
___
python-co
On Thu, 30 Jul 2015 00:11:53 +0200, Jesus Cea 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 by Go
On Wed, 29 Jul 2015 13:41:09 -0400, Terry Reedy wrote:
> On 7/29/2015 1:01 PM, Robert Collins wrote:
> > On 30 July 2015 at 04: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 lea
I'm willing to volunteer for this. I understand how this stuff works,
and no, it doesn't take much time per request...
On Wed, 22 Jul 2015 17:29:25 -, Brett Cannon wrote:
> Maybe once a month, if that. But there have been times when people have
> sent in keys and it has taken a week or so to
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 mailing
On Thu, 14 May 2015 07:15:34 -0700, Larry Hastings wrote:
> I'll start experimenting with the workflow(s) and will add documentation
> to the Dev Guide.
>
> The fun starts next weekend,
By "next weekend" you mean "the weekend after this coming weekend",
right? (These calendar idioms always con
On Wed, 13 May 2015 15:43:17 -0400, Yury Selivanov
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
__
On Thu, 02 Apr 2015 09:31:08 -0700, Guido van Rossum 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
> complex fea
On Sat, 14 Mar 2015 20:23:03 -, 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 manage
On Sun, 05 Oct 2014 14:47:06 -0400, Benjamin Peterson
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 certainly not
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 final
On Mon, 22 Sep 2014 10:51:27 +0100, Michael Foord
wrote:
> Robert Collins is volunteering to help with maintenance and improvement
> of unittest. He's probably known to many of you, but Robert is the
> creator of subunit, testtools and many Python libraries particularly in
> the area of testin
(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
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
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 alr
On Wed, 16 Apr 2014 10:53:53 -0400, "R. David Murray"
wrote:
> On Tue, 15 Apr 2014 23:21:41 -0400, Terry Reedy wrote:
> > On 4/15/2014 9:45 PM, Ethan Furman wrote:
> > > On 04/15/2014 05:55 PM, R. David Murray wrote:
> > >>
> > >> [...
On Wed, 16 Apr 2014 18:02:31 -0400, Terry Reedy 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
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 is
On Tue, 15 Apr 2014 23:21:41 -0400, Terry Reedy 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 &#
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
On Tue, 11 Feb 2014 01:01:38 -0800, Ethan Furman 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, only criti
On Mon, 27 Jan 2014 14:52:16 -0500, Yury Selivanov
wrote:
> Hello,
>
> I'm having difficulty with replying to a message in rietveld.
>
> Here's a screenshot of the exception: http://goo.gl/70iQ5v
> (AttributeError at /review/20356/publish)
>
> Is this a known issue? Maybe I'm doing something w
On Sat, 25 Jan 2014 09:35:46 -0800, Eli Bendersky wrote:
> On Sat, Jan 25, 2014 at 7:13 AM, R. David Murray wrote:
>
> > On Sat, 25 Jan 2014 06:59:19 -0800, Eli Bendersky
> > wrote:
> > > workplace we had a similar process screwed on top of Jenkins - private
>
On Sat, 25 Jan 2014 06:59:19 -0800, Eli Bendersky wrote:
> On Sat, Jan 25, 2014 at 6:54 AM, Dirkjan Ochtman wrote:
>
> > On Sat, Jan 25, 2014 at 2:49 PM, Eli Bendersky wrote:
> > > Interesting. Chromium has something kind-of similar, named "commit
> > queue",
> > > for developers without actual
On Sat, 25 Jan 2014 06:35:59 -0800, Eli Bendersky wrote:
> On Sat, Jan 25, 2014 at 6:14 AM, R. David Murray wrote:
>
> > On Sat, 25 Jan 2014 05:49:56 -0800, Eli Bendersky
> > wrote:
> > > do the latter in Python, which carries a problem we'll probably need to
&
On Sat, 25 Jan 2014 05:49:56 -0800, Eli Bendersky 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 with the rema
So all the buildbots are red for the moment.
A mixture of red and green would have been more appropriate for
today, I think :)
--David
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-commit
On Mon, 02 Dec 2013 17:59:15 -0500, Terry Reedy 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:
> documena
On Sun, 01 Dec 2013 19:29:25 +0100, mar...@v.loewis.de wrote:
>
> Quoting "R. David Murray" :
>
> > You should have the necessary privileges on the tracker now, since I
> > think you ought to. (I don't have them on the meta-tracker, so Martin
> >
On Sun, 01 Dec 2013 18:11:47 +0100, mar...@v.loewis.de wrote:
>
> Quoting "R. David Murray" :
>
> > 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
> > tha
On Sun, 01 Dec 2013 12:12:08 +1000, Nick Coghlan 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 tracker now, since I
On Fri, 29 Nov 2013 14:41:22 -0800, Ned Deily wrote:
>
> On Nov 29, 2013, at 13:51 , Antoine Pitrou 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? There have been an
On Fri, 29 Nov 2013 13:16:32 -0800, Ned Deily wrote:
>
> On Nov 29, 2013, at 12:12 , Guido van Rossum 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 legitimate concern and
On Thu, 24 Oct 2013 17:08:11 +0200, Antoine Pitrou 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,
On Thu, 24 Oct 2013 10:12:07 -0400, Brett Cannon 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 tmp space,
sinc
On Mon, 09 Sep 2013 14:45:51 +0200, Antoine Pitrou wrote:
> Le Mon, 9 Sep 2013 14:30:50 +0200,
> Victor Stinner a écrit :
> > 2013/9/9 Larry Hastings :
> > > Python 3.4 includes a range of improvements of the 3.x series,
> > > including hundreds of small improvements and bug fixes. Major new
>
On Thu, 25 Jul 2013 13:07:59 -0700, Larry Hastings 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 stuff for the emai
On Mon, 15 Jul 2013 18:02:35 +0200, Antoine Pitrou wrote:
> On 2013-07-15 17:16, R. David Murray wrote:
> >
> >> I will make the password available to whoever is in charge, (Or they
> >> can just change the password themselves I don't care).
> >
> >
1 - 100 of 180 matches
Mail list logo
