Re: [Python-Dev] Summary of Python tracker Issues

Thank you for fixing it.Weekly status give me motivation to look issues. -- Inada Naoki ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, Mar 1, 2019 at 8:05 AM Ezio Melotti wrote: > > On Fri, Mar 1, 2019 at 5:59 AM Terry Reedy wrote: > > > > On 2/28/2019 6:54 PM, Glenn Linderman wrote: > > > > > There seems to be enough evidence that something went wrong somewhere, > > > though, and whoever maintains that process should st

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, Mar 1, 2019 at 5:59 AM Terry Reedy wrote: > > On 2/28/2019 6:54 PM, Glenn Linderman wrote: > > > There seems to be enough evidence that something went wrong somewhere, > > though, and whoever maintains that process should start investigating, > > but it would still be nice to get confirmat

Re: [Python-Dev] Summary of Python tracker Issues

On 2/28/2019 6:54 PM, Glenn Linderman wrote: There seems to be enough evidence that something went wrong somewhere, though, and whoever maintains that process should start investigating, but it would still be nice to get confirmation from a non-Google email recipient whether they did or did no

Re: [Python-Dev] Summary of Python tracker Issues

On 2019-02-28 23:54, Glenn Linderman wrote: On 2/28/2019 2:52 PM, Terry Reedy wrote: On 2/28/2019 5:38 PM, Glenn Linderman wrote: On 2/28/2019 2:18 PM, Jonathan Goble wrote: On Thu, Feb 28, 2019, 5:11 PM Terry Reedy > wrote:     On 2/28/2019 8:07 AM, Jonathan Goble wr

Re: [Python-Dev] Summary of Python tracker Issues

> > It's also possible that the fault is not in sending (we have evidence here > that two entirely different protocols have not received it, and they are also > not in the archives [1]), but in the generation of the report. Could there > have been a subtle change to the bpo tracker itself, or so

Re: [Python-Dev] Summary of Python tracker Issues

On Thu, Feb 28, 2019 at 6:57 PM Glenn Linderman wrote: > On 2/28/2019 2:52 PM, Terry Reedy wrote: > > On 2/28/2019 5:38 PM, Glenn Linderman wrote: > > On 2/28/2019 2:18 PM, Jonathan Goble wrote: > > On Thu, Feb 28, 2019, 5:11 PM Terry Reedy > wrote: > > On 2/28/2019

Re: [Python-Dev] Summary of Python tracker Issues

On 2/28/2019 2:52 PM, Terry Reedy wrote: On 2/28/2019 5:38 PM, Glenn Linderman wrote: On 2/28/2019 2:18 PM, Jonathan Goble wrote: On Thu, Feb 28, 2019, 5:11 PM Terry Reedy > wrote:     On 2/28/2019 8:07 AM, Jonathan Goble wrote:     > On Thu, Feb 28, 2019, 8:02 AM INAD

Re: [Python-Dev] Summary of Python tracker Issues

On 2/28/2019 5:38 PM, Glenn Linderman wrote: On 2/28/2019 2:18 PM, Jonathan Goble wrote: On Thu, Feb 28, 2019, 5:11 PM Terry Reedy > wrote: On 2/28/2019 8:07 AM, Jonathan Goble wrote: > On Thu, Feb 28, 2019, 8:02 AM INADA Naoki mailto:songofaca...@gmail.com>

Re: [Python-Dev] Summary of Python tracker Issues

On 2/28/2019 2:18 PM, Jonathan Goble wrote: On Thu, Feb 28, 2019, 5:11 PM Terry Reedy > wrote: On 2/28/2019 8:07 AM, Jonathan Goble wrote: > On Thu, Feb 28, 2019, 8:02 AM INADA Naoki mailto:songofaca...@gmail.com> >

Re: [Python-Dev] Summary of Python tracker Issues

On Thu, Feb 28, 2019, 5:11 PM Terry Reedy wrote: > On 2/28/2019 8:07 AM, Jonathan Goble wrote: > > On Thu, Feb 28, 2019, 8:02 AM INADA Naoki > > wrote: > > > > No stats for last week? > > > > > > Been missing for two weeks actually. I did not receive a summary

Re: [Python-Dev] Summary of Python tracker Issues

On 2/28/2019 8:07 AM, Jonathan Goble wrote: On Thu, Feb 28, 2019, 8:02 AM INADA Naoki > wrote: No stats for last week? Been missing for two weeks actually. I did not receive a summary on either the 15th or 22nd. Ditto for me. I get pydev via gmane. Anyon

Re: [Python-Dev] Summary of Python tracker Issues

On Thu, Feb 28, 2019, 8:02 AM INADA Naoki wrote: > No stats for last week? > Been missing for two weeks actually. I did not receive a summary on either the 15th or 22nd. > ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailm

Re: [Python-Dev] Summary of Python tracker Issues

No stats for last week? On Sat, Feb 9, 2019 at 3:11 AM Python tracker wrote: > > ACTIVITY SUMMARY (2019-02-01 - 2019-02-08) > Python tracker at https://bugs.python.org/ > > To view or respond to any of the issues listed below, click on the issue. > Do NOT respond to this message. > > Issues coun

Re: [Python-Dev] Summary of Python tracker Issues

Le 1 juil. 2017 10:18 AM, "Serhiy Storchaka" a écrit : Victor closed a half of hundred his issues. Let me elaborate :-) I am still learning the new GitHub workflow, and it's common that I forget to close issues after merging a change. I had many issues that I forgot to update since we moved to

Re: [Python-Dev] Summary of Python tracker Issues

23.06.17 19:09, Python tracker пише: ACTIVITY SUMMARY (2017-06-16 - 2017-06-23) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open6026 ( -8) Terry closed a t

Re: [Python-Dev] Summary of Python tracker Issues

30.06.17 19:09, Python tracker пише: ACTIVITY SUMMARY (2017-06-23 - 2017-06-30) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open6006 (-20) Victor closed a h

Re: [Python-Dev] Summary of Python tracker Issues

I guess I should have never changed the title - apparently the tracker loses track - there are more than 5 messages. On 2016-03-04 18:08, Python tracker wrote: #26439: ctypes.util.find_library fails when ldconfig/glibc not availab http://bugs.python.org/issue264395 msgs And, while I do not

Re: [Python-Dev] Summary of Python tracker Issues

Thank you, David, for all of your work. It's much appreciated. -- Eric. > On Apr 17, 2015, at 7:18 PM, R. David Murray wrote: > >> On Fri, 17 Apr 2015 18:08:24 +0200, Python tracker >> wrote: >> >> ACTIVITY SUMMARY (2015-04-10 - 2015-04-17) >> Python tracker at http://bugs.python.org/ >> >

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, 17 Apr 2015 18:08:24 +0200, Python tracker wrote: > > ACTIVITY SUMMARY (2015-04-10 - 2015-04-17) > Python tracker at http://bugs.python.org/ > > To view or respond to any of the issues listed below, click on the issue. > Do NOT respond to this message. > > Issues counts and deltas: >

Re: [Python-Dev] Summary of Python tracker Issues

T-Mobile. America's First Nationwide 4G Network. -- Original message--From: Python trackerDate: Fri, Sep 26, 2014 12:07 PMTo: python-dev@python.org;Subject:[Python-Dev] Summary of Python tracker IssuesACTIVITY SUMMARY (2014-09-19 - 2014-09-26)Python tracker at http://bugs.p

Re: [Python-Dev] Summary of Python tracker Issues

Hi, On Sat, Feb 8, 2014 at 1:37 PM, francis wrote: > On 02/07/2014 06:07 PM, Python tracker wrote: >> >> Open issues with patches: 2045 > > > Has somebody done a graphic of that data againsttime? > You can find some charts here (it's still a work in progress though): http://bugs.python.org/is

Re: [Python-Dev] Summary of Python tracker Issues

On 02/07/2014 06:07 PM, Python tracker wrote: Open issues with patches: 2045 Has somebody done a graphic of that data againsttime? Regards, francis ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev

Re: [Python-Dev] Summary of Python tracker Issues

Brett Cannon wrote: > Do we have a graph of the historical trend of the number of bugs (or at least > the historical details stored somewhere)? I think we have had a net decrease > in > open bugs the last couple of weeks and it would be neat to see an absolute and > relative graph of the overall t

Re: [Python-Dev] Summary of Python tracker Issues

Hi, On Fri, Nov 30, 2012 at 11:52 PM, Brett Cannon wrote: > On Fri, Nov 30, 2012 at 4:07 PM, R. David Murray wrote: > >> On Fri, 30 Nov 2012 14:38:12 -0500, Brett Cannon >> wrote: >> > Do we have a graph of the historical trend of the number of bugs (or at >> > least the historical details stor

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, Nov 30, 2012 at 4:07 PM, R. David Murray wrote: > On Fri, 30 Nov 2012 14:38:12 -0500, Brett Cannon wrote: > > Do we have a graph of the historical trend of the number of bugs (or at > > least the historical details stored somewhere)? I think we have had a net > > Not really. Ezio made on

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, 30 Nov 2012 14:38:12 -0500, Brett Cannon wrote: > Do we have a graph of the historical trend of the number of bugs (or at > least the historical details stored somewhere)? I think we have had a net Not really. Ezio made one by hand once, but there is nothing automated. The historical de

Re: [Python-Dev] Summary of Python tracker Issues

On 30.11.12 21:38, Brett Cannon wrote: Also might make a nice motivator to try to close issues faster. =) May be introduce the title of "Issue closer of the month"? ;) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/

Re: [Python-Dev] Summary of Python tracker Issues

Do we have a graph of the historical trend of the number of bugs (or at least the historical details stored somewhere)? I think we have had a net decrease in open bugs the last couple of weeks and it would be neat to see an absolute and relative graph of the overall trend since Python 3.3.0 was rel

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, Nov 2, 2012 at 10:05 PM, Eric Snow wrote: > > On Fri, Nov 2, 2012 at 11:07 AM, Python tracker wrote: > > > > ACTIVITY SUMMARY (2012-10-26 - 2012-11-02) > > Python tracker at http://bugs.python.org/ > > > > To view or respond to any of the issues listed below, click on the issue. > > Do NO

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, Nov 2, 2012 at 11:07 AM, Python tracker wrote: > > ACTIVITY SUMMARY (2012-10-26 - 2012-11-02) > Python tracker at http://bugs.python.org/ > > To view or respond to any of the issues listed below, click on the issue. > Do NOT respond to this message. > > Issues counts and deltas: > open

Re: [Python-Dev] Summary of Python tracker Issues

Hi, On Sat, Aug 25, 2012 at 2:07 PM, wrote: > > Zitat von francis : > > >> Is there a easy way to automate this?: >> >> - Get a list the "waiting for review" issues > > > Not exactly this precise list; instead, a list of issues with a patch: > > s=xmlrpclib.ServerProxy("http://bugs.python.org",a

Re: [Python-Dev] Summary of Python tracker Issues

Zitat von francis : Is there a easy way to automate this?: - Get a list the "waiting for review" issues Not exactly this precise list; instead, a list of issues with a patch: s=xmlrpclib.ServerProxy("http://bugs.python.org",allow_none=True) s.filter('issue',dict(keywords=2,status=1}) The o

Re: [Python-Dev] Summary of Python tracker Issues

Most recent 15 issues waiting for review (15) = Just curious: How is a issue considered "waiting for review"? Issues that have the "patch" or "needs review" keyword or are in the "patch review" stage. Thank you! Is there a easy way to aut

Re: [Python-Dev] Summary of Python tracker Issues

Zitat von francis : Most recent 15 issues waiting for review (15) = Just curious: How is a issue considered "waiting for review"? Issues that have the "patch" or "needs review" keyword or are in the "patch review" stage. Regards, Martin

Re: [Python-Dev] Summary of Python tracker Issues

Most recent 15 issues waiting for review (15) = Just curious: How is a issue considered "waiting for review"? Thanks! francis ___ Python-Dev mailing list Python-Dev@python.org http://mail.python

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, Aug 24, 2012 at 12:07 PM, Python tracker wrote: > > ACTIVITY SUMMARY (2012-08-17 - 2012-08-24) > Python tracker at http://bugs.python.org/ > > To view or respond to any of the issues listed below, click on the issue. > Do NOT respond to this message. > > Issues counts and deltas: > open

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, May 4, 2012 at 10:07 AM, Python tracker wrote: > > ACTIVITY SUMMARY (2012-04-27 - 2012-05-04) > Python tracker at http://bugs.python.org/ > > To view or respond to any of the issues listed below, click on the issue. > Do NOT respond to this message. > > Issues counts and deltas: >  open  

Re: [Python-Dev] Summary of Python tracker Issues

The summary mails part 1 was declared as US-ASCII, 8bit, but it contained a UTF-8 character: > #12056: "???" (HORIZONTAL ELLIPSIS) should be an alternative syntax fo > http://bugs.python.org/issue12056 closed by benjamin.peterson This is handled without any problem by Python 3000 due to David Mu

Re: [Python-Dev] Summary of Python tracker Issues

On 07/01/2011 17:07, Python tracker wrote: ACTIVITY SUMMARY (2010-12-31 - 2011-01-07) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open2501 (-24) closed 201

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, Jan 7, 2011 at 1:17 PM, anatoly techtonik wrote: .. >>> Issues counts and deltas: >>>   open    2501 (-24) >>>   closed 20138 (+80) >>>   total  22639 (+56) .. > Less users -> less issues. It's always easy to speedup the process by > leaving the most irritating ones. ;) You should read th

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, Jan 7, 2011 at 7:55 PM, Michael Foord wrote: > On 07/01/2011 17:07, Python tracker wrote: >> >> ACTIVITY SUMMARY (2010-12-31 - 2011-01-07) >> Python tracker athttp://bugs.python.org/ >> >> To view or respond to any of the issues listed below, click on the issue. >> Do NOT respond to this m

Re: [Python-Dev] Summary of Python tracker Issues

On 07/01/2011 17:07, Python tracker wrote: ACTIVITY SUMMARY (2010-12-31 - 2011-01-07) Python tracker athttp://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open2501 (-24) closed 2013

Re: [Python-Dev] Summary of Python tracker Issues

Current status from the tracker... don't care: 22134 not closed: 2491 not selected: 1 open: 2451 languishing: 25 pending: 39 closed: 19604 That gives us... 2451 open 1 not selected 39 pending 25 languishing 2516 Total open 2451 open 39 languishing Should be 39 pending here, not la

Re: [Python-Dev] Summary of Python tracker Issues

On 11/06/2010 12:01 PM, Terry Reedy wrote: On 11/6/2010 11:42 AM, R. David Murray wrote: On Sat, 06 Nov 2010 15:38:22 +0100, Georg Brandl wrote: Am 06.11.2010 05:44, schrieb Ezio Melotti: Hi, On 05/11/2010 19.08, Python tracker wrote: ACTIVITY SUMMARY (2010-10-29 - 2010-11-05) Python track

Re: [Python-Dev] Summary of Python tracker Issues

On 06/11/2010 19.01, Terry Reedy wrote: On 11/6/2010 11:42 AM, R. David Murray wrote: On Sat, 06 Nov 2010 15:38:22 +0100, Georg Brandl wrote: Am 06.11.2010 05:44, schrieb Ezio Melotti: Hi, On 05/11/2010 19.08, Python tracker wrote: ACTIVITY SUMMARY (2010-10-29 - 2010-11-05) Python tracker a

Re: [Python-Dev] Summary of Python tracker Issues

On 11/6/2010 11:42 AM, R. David Murray wrote: On Sat, 06 Nov 2010 15:38:22 +0100, Georg Brandl wrote: Am 06.11.2010 05:44, schrieb Ezio Melotti: Hi, On 05/11/2010 19.08, Python tracker wrote: ACTIVITY SUMMARY (2010-10-29 - 2010-11-05) Python tracker at http://bugs.python.org/ To view or res

Re: [Python-Dev] Summary of Python tracker Issues

On Sat, 06 Nov 2010 15:38:22 +0100, Georg Brandl wrote: > Am 06.11.2010 05:44, schrieb Ezio Melotti: > > Hi, > > > > On 05/11/2010 19.08, Python tracker wrote: > >> ACTIVITY SUMMARY (2010-10-29 - 2010-11-05) > >> Python tracker at http://bugs.python.org/ > >> > >> To view or respond to any of the

Re: [Python-Dev] Summary of Python tracker Issues

Am 06.11.2010 05:44, schrieb Ezio Melotti: > Hi, > > On 05/11/2010 19.08, Python tracker wrote: >> ACTIVITY SUMMARY (2010-10-29 - 2010-11-05) >> Python tracker at http://bugs.python.org/ >> >> To view or respond to any of the issues listed below, click on the issue. >> Do NOT respond to this messa

Re: [Python-Dev] Summary of Python tracker Issues

Hi, On 05/11/2010 19.08, Python tracker wrote: ACTIVITY SUMMARY (2010-10-29 - 2010-11-05) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open2514 (+17) close

Re: [Python-Dev] Summary of Python tracker Issues

>> Issues stats: >> open2494 (+32) >> closed 19460 (+110) >> total 21954 (+56) > > The figures in parentheses look wrong. Last week, the stats said: No: they just mean something different that you think. +32 doesn't mean that there are now 32 more open issues than last week, but that

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, 22 Oct 2010 18:08:20 +0200 (CEST) Python tracker wrote: > > ACTIVITY SUMMARY (2010-10-15 - 2010-10-22) > Python tracker at http://bugs.python.org/ > > To view or respond to any of the issues listed below, click on the issue. > Do NOT respond to this message. > > Issues stats: > open

Re: [Python-Dev] Summary of Python tracker Issues

On 9/25/2010 1:08 PM, Antoine Pitrou wrote: On Sat, 25 Sep 2010 19:02:06 +0200 Georg Brandl wrote: Am 25.09.2010 18:53, schrieb Terry Reedy: On 9/25/2010 7:11 AM, Georg Brandl wrote: I'll bother Ezio when he's back. It just feels strange to me that the bit of statistic I feel is most inter

Re: [Python-Dev] Summary of Python tracker Issues

Am 25.09.2010 23:41, schrieb "Martin v. Löwis": > >> I guess a better example would be >> >> old: >> open #1 #2 >> closed #3 >> new: >> open #1 >> closed #2 #3 #4 #5 >> >> which results in +2 for open (since #4 and #5 were opened) and +3 for closed >> (since #2, #4 and #5 were closed), h

Re: [Python-Dev] Summary of Python tracker Issues

> I guess a better example would be > > old: > open #1 #2 > closed #3 > new: > open #1 > closed #2 #3 #4 #5 > > which results in +2 for open (since #4 and #5 were opened) and +3 for closed > (since #2, #4 and #5 were closed), however the total issue delta is +2. This > is why I think th

Re: [Python-Dev] Summary of Python tracker Issues

On Sat, 25 Sep 2010 14:22:06 +0200, Georg Brandl wrote: > Am 25.09.2010 14:10, schrieb "Martin v. L=F6wis": > > The total numbers reported are really the totals. Also, the delta > > reported for the totals is the difference to the last report. > > > The number reported with +/- for open/closed ar

Re: [Python-Dev] Summary of Python tracker Issues

On Sat, 25 Sep 2010 19:02:06 +0200 Georg Brandl wrote: > Am 25.09.2010 18:53, schrieb Terry Reedy: > > On 9/25/2010 7:11 AM, Georg Brandl wrote: > > > >> I'll bother Ezio when he's back. It just feels strange to me that the bit > >> of statistic I feel is most interesting -- whether there are l

Re: [Python-Dev] Summary of Python tracker Issues

Am 25.09.2010 18:53, schrieb Terry Reedy: > On 9/25/2010 7:11 AM, Georg Brandl wrote: > >> I'll bother Ezio when he's back. It just feels strange to me that the bit >> of statistic I feel is most interesting -- whether there are less open bugs >> at the end of the week than at the start -- is not

Re: [Python-Dev] Summary of Python tracker Issues

On 9/25/2010 7:11 AM, Georg Brandl wrote: I'll bother Ezio when he's back. It just feels strange to me that the bit of statistic I feel is most interesting -- whether there are less open bugs at the end of the week than at the start -- is not obvious from the report. As of just now, the defau

Re: [Python-Dev] Summary of Python tracker Issues

Am 25.09.2010 14:10, schrieb "Martin v. Löwis": >>> Guess the only way to settle this is look at the code, but I don't >>> care enough to bother. =) >> >> I'll bother Ezio when he's back. It just feels strange to me that the bit >> of statistic I feel is most interesting -- whether there are less

Re: [Python-Dev] Summary of Python tracker Issues

>> Guess the only way to settle this is look at the code, but I don't >> care enough to bother. =) > > I'll bother Ezio when he's back. It just feels strange to me that the bit > of statistic I feel is most interesting -- whether there are less open bugs > at the end of the week than at the start

Re: [Python-Dev] Summary of Python tracker Issues

Am 25.09.2010 03:45, schrieb Brett Cannon: > On Fri, Sep 24, 2010 at 13:04, Georg Brandl wrote: >> So by opening and closing a bug 5 times within a week, the "open" and >> "close" counters both go up by 5? That would be stupid. > > No, as in a bug was re-opened last week and then closed again th

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, Sep 24, 2010 at 13:04, Georg Brandl wrote: > So by opening and closing a bug 5 times within a week, the "open" and > "close" counters both go up by 5?  That would be stupid. No, as in a bug was re-opened last week and then closed again this week. > > Issues can't be open and closed at th

Re: [Python-Dev] Summary of Python tracker Issues

So by opening and closing a bug 5 times within a week, the "open" and "close" counters both go up by 5? That would be stupid. Issues can't be open and closed at the same time. There is a count of open issues at the start of the week, and one at the end of the week. There's a difference between t

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, Sep 24, 2010 at 12:57, Georg Brandl wrote: > Is it me, or is the "open" and "closed" count confusing to anyone else? > I.e., shouldn't the "total" delta equal the sum of the "open" delta and > the "closed" delta? The total delta is a complete count of bugs, while the open and closed delta

Re: [Python-Dev] Summary of Python tracker Issues

Is it me, or is the "open" and "closed" count confusing to anyone else? I.e., shouldn't the "total" delta equal the sum of the "open" delta and the "closed" delta? Georg Am 24.09.2010 20:00, schrieb Brett Cannon: > I think every week where more bugs are closed than opened should be > celebrated!

Re: [Python-Dev] Summary of Python tracker Issues

I think every week where more bugs are closed than opened should be celebrated! =) Thanks to everyone who closed something this week (and to those that filed good bug reports). On Fri, Sep 24, 2010 at 09:14, Python tracker wrote: > > ACTIVITY SUMMARY (2010-09-17 - 2010-09-24) > Python tracker at

Re: [Python-Dev] Summary of Python tracker Issues

On 3 September 2010 17:41, Paul Moore wrote: > On 3 September 2010 17:30, Victor Stinner > wrote: >> Remember also the buildbot report: >> http://code.google.com/p/bbreport/wiki/PythonBuildbotReport >> >> Eg. there are some "no space left on device" on "x86 XP-5 *" build slaves. > > Thanks, I wa

Re: [Python-Dev] Summary of Python tracker Issues

On 3 September 2010 17:30, Victor Stinner wrote: > Remember also the buildbot report: > http://code.google.com/p/bbreport/wiki/PythonBuildbotReport > > Eg. there are some "no space left on device" on "x86 XP-5 *" build slaves. Thanks, I wasn't aware of that. I'll look into those issues. Paul. ___

Re: [Python-Dev] Summary of Python tracker Issues

Le vendredi 03 septembre 2010 18:07:45, Python tracker a écrit : > ACTIVITY SUMMARY (2010-08-27 - 2010-09-03) > Python tracker at http://bugs.python.org/ Remember also the buildbot report: http://code.google.com/p/bbreport/wiki/PythonBuildbotReport Eg. there are some "no space left on device" on

Re: [Python-Dev] Summary of Python tracker Issues

On 8/27/2010 12:07 PM, Python tracker wrote: Issues stats: open2560 (+41) closed 18924 (+114) I believe this is at least the 4th consecutive report in which closures outnumber opens. Total open is, at the moment, 2493, down from about 2700, or maybe more, a couple of months ago. Th

Re: [Python-Dev] Summary of Python tracker Issues

Le vendredi 20 août 2010 19:49:10, vous avez écrit : > And Now For Something Completely Different... > > http://code.google.com/p/bbreport/wiki/PythonBuildbotReport Thanks to Florent and Ezio for their great work on bbreport project! > - *New failures* : failures which are not associated with

Re: [Python-Dev] Summary of Python tracker Issues

And Now For Something Completely Different... http://code.google.com/p/bbreport/wiki/PythonBuildbotReport The buildbot failures and tracker issues are listed in 3 tables:  - *New failures* : failures which are not associated with an issue in the tracker  - *Known issues* : failures which are

Re: [Python-Dev] Summary of Python tracker Issues

On 8/10/2010 10:28 AM, Ezio Melotti wrote: This is the list of *all* the issues created or reopened during the last week *that are still open*. Thank you for removing the duplication of listing issues opened and closed twice. I otherwise pretty much agree with RDM's comments. -- Terry Jan R

Re: [Python-Dev] Summary of Python tracker Issues

On Tue, 10 Aug 2010 17:28:18 +0300, Ezio Melotti wrote: > Hi, > lately I've been working on the new summary of Python tracker issues. > This is the result. Thanks for working on this, Ezio! > > Issues stats: > >open2640 (+35) > >closed 18679 (+194) > >total 21319 (+57) > > T

Re: [Python-Dev] Summary of Python tracker Issues

Hi, lately I've been working on the new summary of Python tracker issues. This is the result. On 10/08/2010 16.39, Python tracker wrote: ACTIVITY SUMMARY (2010-08-01 - 2010-08-07) This is the period that is considered for the following stats. By default it shows the activity of the last we

Re: [Python-Dev] Summary of Python tracker Issues

Mark Dickinson wrote: On Fri, Apr 24, 2009 at 9:25 PM, Terry Reedy wrote: In going through this, I notice a lot of effort by Mark Dickenson and others Many others, but Eric Smith's name needs to be in big lights here. There's no way the short float repr would have been ready for 3.1 if Eric h

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, Apr 24, 2009 at 9:25 PM, Terry Reedy wrote: > In going through this, I notice a lot of effort by Mark Dickenson and others Many others, but Eric Smith's name needs to be in big lights here. There's no way the short float repr would have been ready for 3.1 if Eric hadn't shown an interest

Re: [Python-Dev] Summary of Python tracker Issues

Python tracker wrote: [snip] In going through this, I notice a lot of effort by Mark Dickenson and others to get some details of numbers computation and display right in time for 3.1. As a certain-to-be beneficiary, I want to thank all who contributed. Terry Jan Reedy _

Re: [Python-Dev] Summary of Python tracker Issues

Python tracker wrote: > > ACTIVITY SUMMARY (02/13/09 - 02/20/09) > Python tracker at http://bugs.python.org/ [...] > 2341 open (+55) / 14813 closed (+27) / 17154 total (+82) I was about to cry foul, +27 closed? We closed so many issues last week, how come? Then, I realized the headings tell anot

Re: [Python-Dev] Summary of Python tracker Issues

On Fri, 30 Jan 2009 18:06:48 +0100 (CET), Python tracker wrote: [snip] Average duration of open issues: 697 days. Median duration of open issues: 6 days. It seems there's a bug in the summary tool. I thought it odd a few weeks ago when I noticed the median duration of open issues was one

Re: [Python-Dev] Summary of Python tracker Issues

>> Correct. > > If a bug exists and is fixed in a later release -- I would call it 'out > of date' instead. Hmm. You have a point, but it should be "Fixed" then, and we have indeed closed bug reports as "fixed" if later releases fixed the bug. It probably doesn't really matter - if the complaint

Re: [Python-Dev] Summary of Python tracker Issues

Martin v. Löwis wrote: Jeremy Hylton wrote: I wanted to ask a policy question on the bug tracker. What are we doing with bugs filed against Python 2.4? This bug http://bugs.python.org/issue1208304 reports a fd leak in Python 2.4, which doesn't exist in the head. Since Python 2.4 is in security

Re: [Python-Dev] Summary of Python tracker Issues

Jeremy Hylton wrote: > I wanted to ask a policy question on the bug tracker. What are we > doing with bugs filed against Python 2.4? > This bug http://bugs.python.org/issue1208304 reports a fd leak in > Python 2.4, which doesn't exist in the head. Since Python 2.4 is in > security-fix only mode,

Re: [Python-Dev] Summary of Python tracker Issues

On Mon, Nov 24, 2008 at 10:02, Jeremy Hylton <[EMAIL PROTECTED]> wrote: > On Mon, Nov 24, 2008 at 12:54 PM, Brett Cannon <[EMAIL PROTECTED]> wrote: >> On Mon, Nov 24, 2008 at 08:58, Jeremy Hylton <[EMAIL PROTECTED]> wrote: >>> I wanted to ask a policy question on the bug tracker. What are we >>> d

Re: [Python-Dev] Summary of Python tracker Issues

On Mon, Nov 24, 2008 at 12:54 PM, Brett Cannon <[EMAIL PROTECTED]> wrote: > On Mon, Nov 24, 2008 at 08:58, Jeremy Hylton <[EMAIL PROTECTED]> wrote: >> I wanted to ask a policy question on the bug tracker. What are we >> doing with bugs filed against Python 2.4? >> This bug http://bugs.python.org/i

Re: [Python-Dev] Summary of Python tracker Issues

On Mon, Nov 24, 2008 at 08:58, Jeremy Hylton <[EMAIL PROTECTED]> wrote: > I wanted to ask a policy question on the bug tracker. What are we > doing with bugs filed against Python 2.4? > This bug http://bugs.python.org/issue1208304 reports a fd leak in > Python 2.4, which doesn't exist in the head.

Re: [Python-Dev] Summary of Python tracker Issues

I wanted to ask a policy question on the bug tracker. What are we doing with bugs filed against Python 2.4? This bug http://bugs.python.org/issue1208304 reports a fd leak in Python 2.4, which doesn't exist in the head. Since Python 2.4 is in security-fix only mode, is it fair to close this with a