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

2019-03-05 Thread Inada Naoki
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-dev/archive%40mail-archive.com


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

2019-03-05 Thread Ezio Melotti
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 start investigating,
> > > but it would still be nice to get confirmation from a non-Google email
> > > recipient whether they did or did not get the Summary messages.
> > >
> > > I wonder if there is a way to manually send them, and if the missing two
> > > weeks of activity can be reported... once the sending problem is
> > > understood and resolved.
> >
> > I posted a note to the core-workflow list, but I don't know if anyone
> > with power or knowledge still reads it.
> >
>
> The tracker got migrated recently, and that's the most likely cause of
> the missing reports.
> We'll look into it and get them back :)
>

Ernest promptly fixed the issue so last week report was sent out correctly.
I just generated and sent out the two reports that were missing and
updated the tracker stats at
https://bugs.python.org/issue?@template=stats
Note that some values in the report might be a bit off (for example,
the list of issues waiting for review doesn't include issues that were
closed after the selected period, and the patch count includes issues
created before or during the selected period even if a patch was
uploaded after the selected period).
The issues counts and deltas at the top of the summary should be correct.
Let me know if you notice any other problem (and thanks Ned for
bringing this to my attention!).

Best Regards,
Ezio Melotti

> > To get a listing, go to the tracker search page, put
> > 2019-02-09 to 2019-03-01
> > in the date box, and change status to don't care.  At the moment, this
> > returns 204 issues.
> >
> > --
> > Terry Jan Reedy
> >
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2019-02-28 Thread Ezio Melotti
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 confirmation from a non-Google email
> > recipient whether they did or did not get the Summary messages.
> >
> > I wonder if there is a way to manually send them, and if the missing two
> > weeks of activity can be reported... once the sending problem is
> > understood and resolved.
>
> I posted a note to the core-workflow list, but I don't know if anyone
> with power or knowledge still reads it.
>

The tracker got migrated recently, and that's the most likely cause of
the missing reports.
We'll look into it and get them back :)

> To get a listing, go to the tracker search page, put
> 2019-02-09 to 2019-03-01
> in the date box, and change status to don't care.  At the moment, this
> returns 204 issues.
>
> --
> Terry Jan Reedy
>
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2019-02-28 Thread Terry Reedy

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 not get the Summary messages.


I wonder if there is a way to manually send them, and if the missing two 
weeks of activity can be reported... once the sending problem is 
understood and resolved.


I posted a note to the core-workflow list, but I don't know if anyone 
with power or knowledge still reads it.


To get a listing, go to the tracker search page, put
2019-02-09 to 2019-03-01
in the date box, and change status to don't care.  At the moment, this 
returns 204 issues.


--
Terry Jan Reedy

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2019-02-28 Thread MRAB

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 wrote:
    > On Thu, Feb 28, 2019, 8:02 AM INADA Naoki
    mailto:songofaca...@gmail.com>
    > >>
    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.  Anyone missing the same 
issues

    get pydev directly by email?


I get direct emails only and stated my observation above. :-)


I confirm and concur with Jonathan's observation, by searching my 
email archive for this group list. So it is not just something about 
his particular email address... except we both do use Google Mail 
services.  I do check my Google SPAM box for the account, and it 
wasn't there either, by recollection (I don't archive the SPAM, but 
delete it ASAP).


Can someone not using a Google email address also confirm?


I effectively did when I said I access via gmane -- as a newsgroup via 
NNTP.  I am sure that the mail server sends directly to news.gmane.org 
rather than through google.


That's a whole different protocol. I don't know all the configurations 
for the server that sends the Summary messages, or how it is handled, 
but you confirm it didn't get to gnane via NNTP, and Jonathan and I 
confirm it didn't get to Google email servers, but neither one really 
confirms that it didn't get to other email servers. Google email is 
definitely different than other email servers.


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 not get the Summary messages.


I wonder if there is a way to manually send them, and if the missing two 
weeks of activity can be reported... once the sending problem is 
understood and resolved.


I subscribed at https://mail.python.org/mailman/listinfo/python-dev and 
I don't use Google for email. I didn't receive them either.

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2019-02-28 Thread INADA Naoki
>
> 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 something else along 
> those lines, that is causing the script to fail silently before it ever 
> reaches the point of attempting to send? Or perhaps a disk ran out of space 
> somewhere?
>
> [1] https://mail.python.org/pipermail/python-dev/2019-February/date.html

I suspect so.  See "Open issues deltas (weekly)" graph in this page.
It is ended by 2/8.

https://bugs.python.org/issue?@template=stats

-- 
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-dev/archive%40mail-archive.com


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

2019-02-28 Thread Jonathan Goble
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 8:07 AM, Jonathan Goble wrote:
> > On Thu, Feb 28, 2019, 8:02 AM INADA Naoki
> mailto:songofaca...@gmail.com>
> 
> >   >>
> 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.  Anyone missing the same issues
> get pydev directly by email?
>
>
> I get direct emails only and stated my observation above. :-)
>
>
> I confirm and concur with Jonathan's observation, by searching my email
> archive for this group list. So it is not just something about his
> particular email address... except we both do use Google Mail services.  I
> do check my Google SPAM box for the account, and it wasn't there either, by
> recollection (I don't archive the SPAM, but delete it ASAP).
>
> Can someone not using a Google email address also confirm?
>
>
> I effectively did when I said I access via gmane -- as a newsgroup via
> NNTP.  I am sure that the mail server sends directly to news.gmane.org
> rather than through google.
>
>
> That's a whole different protocol. I don't know all the configurations for
> the server that sends the Summary messages, or how it is handled, but you
> confirm it didn't get to gnane via NNTP, and Jonathan and I confirm it
> didn't get to Google email servers, but neither one really confirms that it
> didn't get to other email servers. Google email is definitely different
> than other email servers.
>
> 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 not get the Summary messages.
>
> I wonder if there is a way to manually send them, and if the missing two
> weeks of activity can be reported... once the sending problem is understood
> and resolved.
>

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 something
else along those lines, that is causing the script to fail silently before
it ever reaches the point of attempting to send? Or perhaps a disk ran out
of space somewhere?

[1] https://mail.python.org/pipermail/python-dev/2019-February/date.html
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2019-02-28 Thread Glenn Linderman

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 INADA Naoki
    mailto:songofaca...@gmail.com>
    > >>
    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.  Anyone missing the same 
issues

    get pydev directly by email?


I get direct emails only and stated my observation above. :-)


I confirm and concur with Jonathan's observation, by searching my 
email archive for this group list. So it is not just something about 
his particular email address... except we both do use Google Mail 
services.  I do check my Google SPAM box for the account, and it 
wasn't there either, by recollection (I don't archive the SPAM, but 
delete it ASAP).


Can someone not using a Google email address also confirm?


I effectively did when I said I access via gmane -- as a newsgroup via 
NNTP.  I am sure that the mail server sends directly to news.gmane.org 
rather than through google.


That's a whole different protocol. I don't know all the configurations 
for the server that sends the Summary messages, or how it is handled, 
but you confirm it didn't get to gnane via NNTP, and Jonathan and I 
confirm it didn't get to Google email servers, but neither one really 
confirms that it didn't get to other email servers. Google email is 
definitely different than other email servers.


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 not get the Summary messages.


I wonder if there is a way to manually send them, and if the missing two 
weeks of activity can be reported... once the sending problem is 
understood and resolved.
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2019-02-28 Thread Terry Reedy

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>
> >>
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.  Anyone missing the same issues
get pydev directly by email?


I get direct emails only and stated my observation above. :-)


I confirm and concur with Jonathan's observation, by searching my email 
archive for this group list. So it is not just something about his 
particular email address... except we both do use Google Mail services.  
I do check my Google SPAM box for the account, and it wasn't there 
either, by recollection (I don't archive the SPAM, but delete it ASAP).


Can someone not using a Google email address also confirm?


I effectively did when I said I access via gmane -- as a newsgroup via 
NNTP.  I am sure that the mail server sends directly to news.gmane.org 
rather than through google.



--
Terry Jan Reedy


___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2019-02-28 Thread Glenn Linderman

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>
> >>
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.  Anyone missing the same issues
get pydev directly by email?


I get direct emails only and stated my observation above. :-)


I confirm and concur with Jonathan's observation, by searching my email 
archive for this group list. So it is not just something about his 
particular email address... except we both do use Google Mail services.  
I do check my Google SPAM box for the account, and it wasn't there 
either, by recollection (I don't archive the SPAM, but delete it ASAP).


Can someone not using a Google email address also confirm?

Glenn
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2019-02-28 Thread Jonathan Goble
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 on
> > either the 15th or 22nd.
>
> Ditto for me.  I get pydev via gmane.  Anyone missing the same issues
> get pydev directly by email?
>

I get direct emails only and stated my observation above. :-)

>
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2019-02-28 Thread Terry Reedy

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.  Anyone missing the same issues 
get pydev directly by email?



--
Terry Jan Reedy

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2019-02-28 Thread Jonathan Goble
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/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2019-02-28 Thread INADA Naoki
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 counts and deltas:
>   open6998 (+13)
>   closed 40696 (+47)
>   total  47694 (+60)
>
> Open issues with patches: 2783
>
> --
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-dev/archive%40mail-archive.com


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

2017-07-01 Thread Victor Stinner
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 GitHub.

I had also complex bugs splitted into small issues and it took time to fix
all branches and to wait for buildots to confirm that it's really fixed.

To finish, I closed a lot of issues that were older than 2 years because
the bug was fixed in the meanwhile in another issue, or just because I lost
track of the issue and also lost interest and I don't consider that the bug
or feature was worth it.

Victor
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2017-07-01 Thread Serhiy Storchaka

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 third of hundred outdated IDLE issues.

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2017-07-01 Thread Serhiy Storchaka

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 half of hundred his issues.

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2016-03-11 Thread Michael Felt
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 want to ping the list in a rude way, I submitted a 
patch - not perfect of course (seems to work as expected stand-alone, 
but not in a 'build' attempt (a previous 'half' patch that was the 'work 
in progress' did build) - so as I hope to have time in the coming days 
to dig further - some hints on how to debug the failed 'build moment 
during 'make install' would be greatly appreciated.


Basically, the make install ends with:

...

Compiling 
/var/aixtools/aixtools/python/2.7.11.2/opt/lib/python2.7/xml/sax/xmlreader.py 
...
Compiling /var/aixtools/aixtools/python/2.7.11.2/opt/lib/python2.7/xmllib.py ...
Compiling /var/aixtools/aixtools/python/2.7.11.2/opt/lib/python2.7/xmlrpclib.py 
...
Compiling /var/aixtools/aixtools/python/2.7.11.2/opt/lib/python2.7/zipfile.py 
...
make: 1254-004 The error code from the last command is 1.


Stop.
root@x064:[/data/prj/aixtools/python/python-2.7.11.2]


So, my question: how do I make the 'compile' of 
/var/aixtools/aixtools/python/2.7.11.2/opt/lib/python2.7/zipfile.py more 
verbose?

I tried "make V=1 DESTDIR=/var/aixtools/aixtools/python/2.7.11.2 install". but 
the output was identical.

Thanks,
Michael
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2015-04-17 Thread R. David Murray
On Fri, 17 Apr 2015 18:08:24 +0200, Python tracker sta...@bugs.python.org 
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:
   open4792 (-31)
   closed 30957 (+113)
   total  35749 (+82)

That's a successful sprint week :)

Thanks everyone!

--David
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2015-04-17 Thread Eric V. Smith
Thank you, David, for all of your work. It's much appreciated. 

--
Eric.

 On Apr 17, 2015, at 7:18 PM, R. David Murray rdmur...@bitdance.com wrote:
 
 On Fri, 17 Apr 2015 18:08:24 +0200, Python tracker sta...@bugs.python.org 
 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:
  open4792 (-31)
  closed 30957 (+113)
  total  35749 (+82)
 
 That's a successful sprint week :)
 
 Thanks everyone!
 
 --David
 ___
 Python-Dev mailing list
 Python-Dev@python.org
 https://mail.python.org/mailman/listinfo/python-dev
 Unsubscribe: 
 https://mail.python.org/mailman/options/python-dev/eric%2Ba-python-dev%40trueblade.com
 
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2014-09-26 Thread dario670








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.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:  
open4677 (+15)  closed 29587 (+43)  total  34264 (+58)Open issues with 
patches: 2197 Issues opened (39)==#22444: Floor divide should 
return inthttp://bugs.python.org/issue22444  opened by belopolsky#22445: 
Memoryviews require more strict contiguous checks then 
necessahttp://bugs.python.org/issue22445  opened by seberg#22449: 
SSLContext.load_verify_locations behavior on Windows and 
OSXhttp://bugs.python.org/issue22449  opened by christian.heimes#22450: urllib 
doesn't put Accept: */* in the headershttp://bugs.python.org/issue22450  opened 
by rhettinger#22452: addTypeEqualityFunc is not used in 
assertListEqualhttp://bugs.python.org/issue22452  opened by simonzack#22453: 
PyObject_REPR macro causes refcount leakhttp://bugs.python.org/issue22453  
opened by Chris.Colbert#22454: Adding the opposite function of 
shlex.split()http://bugs.python.org/issue22454  opened by Sworddragon#22455: 
idna/punycode give wrong results on narrow 
buildshttp://bugs.python.org/issue22455  opened by bukzor#22456: __base__ 
undocumentedhttp://bugs.python.org/issue22456  opened by Arfrever#22457: 
load_tests not invoked in root __init__.py when start=package 
http://bugs.python.org/issue22457  opened by rbcollins#22458: Add fractions 
benchmarkhttp://bugs.python.org/issue22458  opened by scoder#22460: idle 
editor: replace all in selectionhttp://bugs.python.org/issue22460  opened by 
bagratte#22462: Modules/pyexpat.c violates PEP 
384http://bugs.python.org/issue22462  opened by Mark.Shannon#22463: Warnings 
when building on AIXhttp://bugs.python.org/issue22463  opened by jelie#22465: 
Number agreement error in section 3.2 of web 
docshttp://bugs.python.org/issue22465  opened by pauamma#22466: problem with 
installing python 2.7.8http://bugs.python.org/issue22466  opened by 
elctr0#22468: Tarfile using fstat on GZip file 
objecthttp://bugs.python.org/issue22468  opened by bartolsthoorn#22470: 
Possible integer overflow in error handlershttp://bugs.python.org/issue22470  
opened by serhiy.storchaka#22472: OSErrors should use str and not repr on 
pathshttp://bugs.python.org/issue22472  opened by r.david.murray#22473: The 
gloss on asyncio future with run_forever example is 
confhttp://bugs.python.org/issue22473  opened by r.david.murray#22474: No 
explanation of how a task gets destroyed in asyncio 'task' 
http://bugs.python.org/issue22474  opened by r.david.murray#22475: asyncio task 
get_stack documentation seems to contradict 
itselhttp://bugs.python.org/issue22475  opened by r.david.murray#22476: asyncio 
task chapter confusion about 'task', 'future', and 
'schttp://bugs.python.org/issue22476  opened by r.david.murray#22477: GCD in 
Fractionshttp://bugs.python.org/issue22477  opened by 
b...@gladman.plus.com#22480: SystemExit out of run_until_complete causes 
AttributeError whehttp://bugs.python.org/issue22480  opened by chrysn#22482: 
logging: fileConfig doesn't support formatter 
styleshttp://bugs.python.org/issue22482  opened by domzippilli#22486: Add 
math.gcd()http://bugs.python.org/issue22486  opened by scoder#22489: .gitignore 
filehttp://bugs.python.org/issue22489  opened by rbcollins#22490: Using 
realpath for __PYVENV_LAUNCHER__ makes Homebrew 
installshttp://bugs.python.org/issue22490  opened by tdsmith#22491: Support 
Unicode line boundaries in regular expressionhttp://bugs.python.org/issue22491  
opened by serhiy.storchaka#22492: small addition to print() docs: no binary 
streams.http://bugs.python.org/issue22492  opened by georg.brandl#22493: 
Deprecate the use of flags not at the start of regular 
expresshttp://bugs.python.org/issue22493  opened by serhiy.storchaka#22494: 
default logging time string is not localizedhttp://bugs.python.org/issue22494  
opened by sdague#22495: merge large parts of test_binop.py and 
test_fractions.pyhttp://bugs.python.org/issue22495  opened by wolma#22496: 
urllib2 fails against IIS (urllib2 can't parse 401 reply 
www-ahttp://bugs.python.org/issue22496  opened by deronnax#22497: msiexec not 
creating msvcr90.dll with python -2.7.6.msihttp://bugs.python.org/issue22497  
opened by dykesk#22499: [SSL: BAD_WRITE_RETRY] bad write retry in 
_ssl.c:1636http://bugs.python.org/issue22499  opened by nikratio#22500: 
Argparse always stores True for positional 
argumentshttp://bugs.python.org/issue22500  opened by Tristan.Fisher#22501: 
Optimise PyLong division by 1 or -1http://bugs.python.org/issue22501  opened by 
scoderMost recent 15 issues with no replies 
(15)==#22495: merge large parts of 

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

2014-05-15 Thread Ezio Melotti
Hi,

On Sat, Feb 8, 2014 at 1:37 PM, francis franci...@email.de 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/issue?@template=stats

Best Regards,
Ezio Melotti

 Regards,
 francis

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2014-02-08 Thread francis

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
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2012-12-03 Thread Petri Lehtinen
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 trend since Python 3.3.0 was released. Also 
 might
 make a nice motivator to try to close issues faster. =)
 
 Otherwise is the code public for this somewhere? I assume it's making an
 XML-RPC call or something every week to get the results, but if I decide to do
 a little App Engine app to store historical data and do a graph I would rather
 not have to figure all of this out from scratch. =) Although I could I guess
 also parse the email if I wanted to ignore all other emails.

A few months ago I made a script that downloads all python-dev mailman
archives, scans them to find the summary messages, parses the messages
and creates a graph using matplotlib. The script is available at
https://gist.github.com/2723809.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2012-11-30 Thread Brett Cannon
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
released. Also might make a nice motivator to try to close issues faster. =)

Otherwise is the code public for this somewhere? I assume it's making an
XML-RPC call or something every week to get the results, but if I decide to
do a little App Engine app to store historical data and do a graph I would
rather not have to figure all of this out from scratch. =) Although I could
I guess also parse the email if I wanted to ignore all other emails.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2012-11-30 Thread Serhiy Storchaka

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/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2012-11-30 Thread R. David Murray
On Fri, 30 Nov 2012 14:38:12 -0500, Brett Cannon br...@python.org 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 details are stored only in the mailing list archives, as
far as I know.  In theory I think you could re-calculate them from the
Roundup DB, but for various reasons the numbers would probably come out
slightly different.  Still, getting the data from the DB would be better
than parsing the emails, since for one reason and another there are
missing Friday reports, and reports that were issued on non-Friday
dates.

 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
 released. Also might make a nice motivator to try to close issues faster. =)
 
 Otherwise is the code public for this somewhere? I assume it's making an

Yes.  It is in the software repository for our roundup instances:

http://hg.python.org/tracker/python-dev/file/default/scripts/roundup-summary

(Be warned that that isn't the location from which the script is
executed, so it is possible for what is actually running to get out of
sync with what is checked in at that location.)

 XML-RPC call or something every week to get the results, but if I decide to

Nope, it talks directly to the DB.  And as you will see, it is more
than a bit gnarly.

 do a little App Engine app to store historical data and do a graph I would
 rather not have to figure all of this out from scratch. =) Although I could
 I guess also parse the email if I wanted to ignore all other emails.

I'm not sure how one would go about integrating the above with an App
Engine app.  I suspect that not quite enough information is available
through the XML-RPC interface to replicate that script, but maybe you
could manage just the open-close counting part of it.  I haven't
looked at what it would take.

--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2012-11-30 Thread Brett Cannon
On Fri, Nov 30, 2012 at 4:07 PM, R. David Murray rdmur...@bitdance.comwrote:

 On Fri, 30 Nov 2012 14:38:12 -0500, Brett Cannon br...@python.org 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 details are stored only in the mailing list archives, as
 far as I know.  In theory I think you could re-calculate them from the
 Roundup DB, but for various reasons the numbers would probably come out
 slightly different.  Still, getting the data from the DB would be better
 than parsing the emails, since for one reason and another there are
 missing Friday reports, and reports that were issued on non-Friday
 dates.

  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
  released. Also might make a nice motivator to try to close issues
 faster. =)
 
  Otherwise is the code public for this somewhere? I assume it's making an

 Yes.  It is in the software repository for our roundup instances:


 http://hg.python.org/tracker/python-dev/file/default/scripts/roundup-summary

 (Be warned that that isn't the location from which the script is
 executed, so it is possible for what is actually running to get out of
 sync with what is checked in at that location.)

  XML-RPC call or something every week to get the results, but if I decide
 to

 Nope, it talks directly to the DB.  And as you will see, it is more
 than a bit gnarly.


I think I could also download the csv file and parse that to get whatever
data I wanted.


   do a little App Engine app to store historical data and do a graph I
 would
  rather not have to figure all of this out from scratch. =) Although I
 could
  I guess also parse the email if I wanted to ignore all other emails.

 I'm not sure how one would go about integrating the above with an App
 Engine app.  I suspect that not quite enough information is available
 through the XML-RPC interface to replicate that script, but maybe you
 could manage just the open-close counting part of it.  I haven't
 looked at what it would take.


It really depends on what statistics I cared about (e.g. there are less
than 4000 bugs while there are less than 25,000 closed bugs). If I just did
high-level statistics it wouldn't be bad, but if I try to track every issue
independently that might be annoying (and actually cost money for me,
although I already personally pay for py3ksupport.appspot.com so I can
probably piggyback off of that app's quota). We will see if this ever goes
anywhere. =)
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2012-11-30 Thread Ezio Melotti
Hi,

On Fri, Nov 30, 2012 at 11:52 PM, Brett Cannon br...@python.org wrote:

 On Fri, Nov 30, 2012 at 4:07 PM, R. David Murray rdmur...@bitdance.comwrote:

 On Fri, 30 Nov 2012 14:38:12 -0500, Brett Cannon br...@python.org
 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 one I made can be found here:
https://docs.google.com/spreadsheet/ccc?key=0AplyAWXqkvHUdFF0SkVrT3VKcnRBZXNrR1hleHowWnc
I now updated it with the latest data.
On the Sheet 2 you can find additional graphs that show the releases of
Python together with the data.  Only final releases are included, alphas,
betas and rcs are not included.
The spreadsheet is a bit messy because I was experimenting with different
kind of graphs and trying to work around some limitations of Google Docs,
but it should be good enough.



 The historical details are stored only in the mailing list archives, as
 far as I know.  In theory I think you could re-calculate them from the
 Roundup DB, but for various reasons the numbers would probably come out
 slightly different.  Still, getting the data from the DB would be better
 than parsing the emails, since for one reason and another there are
 missing Friday reports, and reports that were issued on non-Friday
 dates.


One option I was considering is having the weekly report script append the
result on a file and make it available on bugs.python.org, or even use it
to generate graphs directly.  This is something I considered and planned to
implement for a long time, but haven't done it yet.


  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
  released. Also might make a nice motivator to try to close issues
 faster. =)
 
  Otherwise is the code public for this somewhere? I assume it's making an

 Yes.  It is in the software repository for our roundup instances:


 http://hg.python.org/tracker/python-dev/file/default/scripts/roundup-summary

 (Be warned that that isn't the location from which the script is
 executed, so it is possible for what is actually running to get out of
 sync with what is checked in at that location.)

  XML-RPC call or something every week to get the results, but if I
 decide to

 Nope, it talks directly to the DB.  And as you will see, it is more
 than a bit gnarly.


 I think I could also download the csv file and parse that to get whatever
 data I wanted.


To figure out when an issue was closed you need to access its history, and
that's not available through XML-RPC/csv IIRC.  You should be able to
figure out when the issue got created though.
Anyway, it's probably easier to implement something like what I mentioned
earlier.



   do a little App Engine app to store historical data and do a graph I
 would
  rather not have to figure all of this out from scratch. =) Although I
 could
  I guess also parse the email if I wanted to ignore all other emails.

 I'm not sure how one would go about integrating the above with an App
 Engine app.  I suspect that not quite enough information is available
 through the XML-RPC interface to replicate that script, but maybe you
 could manage just the open-close counting part of it.  I haven't
 looked at what it would take.


 It really depends on what statistics I cared about (e.g. there are less
 than 4000 bugs while there are less than 25,000 closed bugs). If I just did
 high-level statistics it wouldn't be bad, but if I try to track every issue
 independently that might be annoying (and actually cost money for me,
 although I already personally pay for py3ksupport.appspot.com so I can
 probably piggyback off of that app's quota). We will see if this ever goes
 anywhere. =)


Another somehow related project/experiment I've been working on is
collecting stats about the patches available on the tracker.  I put
together a temporary page that allows you to enter the name of a module (or
any file/path) and get a list of issues with patches that affect the
specified module(s):  http://wolfprojects.altervista.org/issues.html
FTR this is based on the word done by anatoly (see links on the page).
I'm planning to eventually integrate this in the tracker too, but lately I
don't have too much time, so there's no ETA.

Best Regards,
Ezio Melotti
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2012-11-02 Thread Eric Snow
On Fri, Nov 2, 2012 at 11:07 AM, Python tracker sta...@bugs.python.org 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:
   open3804 (-19)

wow!

   closed 24361 (+77)
   total  28165 (+58)

 Open issues with patches: 1714
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2012-11-02 Thread Andrew Svetlov
On Fri, Nov 2, 2012 at 10:05 PM, Eric Snow ericsnowcurren...@gmail.com
wrote:

 On Fri, Nov 2, 2012 at 11:07 AM, Python tracker sta...@bugs.python.org
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:
open3804 (-19)

 wow!

Aha!

closed 24361 (+77)
total  28165 (+58)
 
  Open issues with patches: 1714
 ___
 Python-Dev mailing list
 Python-Dev@python.org
 http://mail.python.org/mailman/listinfo/python-dev
 Unsubscribe:
http://mail.python.org/mailman/options/python-dev/andrew.svetlov%40gmail.com




--
Thanks,
Andrew Svetlov
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2012-08-25 Thread 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.


Thank you!

Is there a easy way to automate this?:

- Get a list the waiting for review issues
- Get the last patch
- Try to apply that patch to the version(s) to check if that patch 
already applies?


Regards,

francis

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2012-08-25 Thread martin


Zitat von francis franci...@email.de:


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 other conditions need to be queried separately (although you
could search for both keywords in a single query).


- Get the last patch


s.display('issue12201','files')

The latest patch will be the one with the highest ID.

To then download the patch, just download

http://bugs.python.org/fileid/arbitrary-name.diff

Alternatively, do

s.display('file22163', 'content')

- Try to apply that patch to the version(s) to check if that patch  
already applies?


This should be possible by just running patch(1) through the subprocess
module (and hg revert afterwards). You may have to do some patch parsing
to find out whether to pass -p0 or -p1.

Regards,
Martin




___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2012-08-25 Thread Ezio Melotti
Hi,

On Sat, Aug 25, 2012 at 2:07 PM,  mar...@v.loewis.de wrote:

 Zitat von francis franci...@email.de:


 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 other conditions need to be queried separately (although you
 could search for both keywords in a single query).

 [...]

In addition, you might want to check the Roundup XML-RPC docs:
http://roundup.sourceforge.net/docs/xmlrpc.html
and the source of the script that generates the summary:
http://hg.python.org/tracker/python-dev/file/default/scripts/roundup-summary

Best Regards,
Ezio Melotti
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2012-08-24 Thread Brett Cannon
On Fri, Aug 24, 2012 at 12:07 PM, Python tracker sta...@bugs.python.orgwrote:


 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:
   open3640 ( +0)
   closed 23914 (+58)
   total  27554 (+58)


Have we ever had a flat month of open bugs?!? Pretty great regardless.

-Brett



 Open issues with patches: 1603


 Issues opened (36)
 ==

 #15316: runpy swallows ImportError information with relative imports
 http://bugs.python.org/issue15316  reopened by cjerdonek

 #15720: move __import__() out of the default lookup chain
 http://bugs.python.org/issue15720  opened by eric.snow

 #15721: PEP 3121, 384 Refactoring applied to tkinter module
 http://bugs.python.org/issue15721  opened by Robin.Schreiber

 #15722: PEP 3121, 384 Refactoring applied to decimal module
 http://bugs.python.org/issue15722  opened by Robin.Schreiber

 #15723: Python breaks OS' append guarantee on file writes
 http://bugs.python.org/issue15723  opened by bsdphk

 #15724: Add versionchanged to memoryview docs
 http://bugs.python.org/issue15724  opened by skrah

 #15725: PyType_FromSpecWithBases bugfix
 http://bugs.python.org/issue15725  opened by Robin.Schreiber

 #15727: PyType_FromSpecWithBases tp_new bugfix
 http://bugs.python.org/issue15727  opened by Robin.Schreiber

 #15729: PyStructSequence_NewType enhancement
 http://bugs.python.org/issue15729  opened by Robin.Schreiber

 #15730: Silence unused value warnings under Mac OS X 10.8/clang
 http://bugs.python.org/issue15730  opened by Benno.Rice

 #15731: Mechanism for inheriting docstrings and signatures
 http://bugs.python.org/issue15731  opened by ncoghlan

 #15733: PEP 3121, 384 Refactoring applied to winapi module
 http://bugs.python.org/issue15733  opened by Robin.Schreiber

 #15734: PEP 3121, 384 Refactoring applied to spwd module
 http://bugs.python.org/issue15734  opened by Robin.Schreiber

 #15735: PEP 3121, 384 Refactoring applied to ossaudio module
 http://bugs.python.org/issue15735  opened by Robin.Schreiber

 #15743: test_urllib2/test_urllib use deprecated urllib.Request methods
 http://bugs.python.org/issue15743  opened by Jeff.Knupp

 #15744: missing tests for {RawIO,BufferedIO,TextIO}.writelines
 http://bugs.python.org/issue15744  opened by pitrou

 #15745: Numerous utime ns tests fail on FreeBSD w/ ZFS
 http://bugs.python.org/issue15745  opened by trent

 #15746: test_winsound bombing out on 2003 buildslave
 http://bugs.python.org/issue15746  opened by trent

 #15748: Various symlink test failures in test_shutil on FreeBSD
 http://bugs.python.org/issue15748  opened by trent

 #15749: cgitb prints html for text when display disabled.
 http://bugs.python.org/issue15749  opened by aliles

 #15750: test_localtime_daylight_false_dst_true raises OverflowError: m
 http://bugs.python.org/issue15750  opened by trent

 #15751: Support subinterpreters in the GIL state API
 http://bugs.python.org/issue15751  opened by ncoghlan

 #15753: No-argument super in method with variable arguments raises Sys
 http://bugs.python.org/issue15753  opened by james.sanders

 #15756: subprocess.poll() does not handle errno.ECHILD No child proce
 http://bugs.python.org/issue15756  opened by twhitema

 #15757: ./configure --with-pydebug on FreeBSD results in -O2 -pipe eve
 http://bugs.python.org/issue15757  opened by trent

 #15758: FileIO.readall() has worst case O(n^2) complexity
 http://bugs.python.org/issue15758  opened by sbt

 #15759: make suspicious doesn't display instructions in case of fail
 http://bugs.python.org/issue15759  opened by ezio.melotti

 #15761: Setting PYTHONEXECUTABLE can cause segfaults on OS X
 http://bugs.python.org/issue15761  opened by ned.deily

 #15765: test_getcwd_long_pathnames (in test_posix) kills NetBSD
 http://bugs.python.org/issue15765  opened by trent

 #15766: _imp.load_dynamic() does crash with non-ASCII path and uses th
 http://bugs.python.org/issue15766  opened by haypo

 #15767: add ModuleNotFoundError
 http://bugs.python.org/issue15767  opened by eric.snow

 #15769: urllib.request.urlopen with cafile or capath set overrides any
 http://bugs.python.org/issue15769  opened by caligatio

 #15772: Unresolved symbols in Windows 64-bit python
 http://bugs.python.org/issue15772  opened by spatz123

 #15775: Add StopParser() to expat
 http://bugs.python.org/issue15775  opened by nemeskeyd

 #15776: Allow pyvenv to work in existing directory
 http://bugs.python.org/issue15776  opened by stefanholek

 #15777: test_capi refleak
 http://bugs.python.org/issue15777  opened by rosslagerwall



 Most recent 15 issues with no replies (15)
 ==

 #15775: Add StopParser() to expat
 http://bugs.python.org/issue15775

 #15772: Unresolved symbols in Windows 64-bit python
 http://bugs.python.org/issue15772

 #15767: add ModuleNotFoundError
 

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

2012-05-04 Thread Eric Snow
On Fri, May 4, 2012 at 10:07 AM, Python tracker sta...@bugs.python.org 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    3399 ( -6)
  closed 23101 (+45)
  total  26500 (+39)

Negative delta for open, FTW!
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2011-05-13 Thread Steffen Daode Nurpmeso
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 Murrays patch of issue 11605 for 3.2 and 3.3.
(It however broke my obviously insufficient non-postman thing :(,
and it's of course not a valid mail, strictly speaking.
So i report this just in case your stricken MUAs simply do the
right thing and noone recognizes it at all.)

May the juice be with you

--
Steffen, sdaoden(*)(gmail.com)

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2011-01-09 Thread Michael Foord

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 20138 (+80)
   total  22639 (+56)



Nice work everyone. :-)

At this rate we'll be down to zero open issues in only 2 years. ;-)

Michael


Open issues with patches: 1045


Issues opened (40)
==

#4188: test_threading hang when running as verbose
http://bugs.python.org/issue4188  reopened by r.david.murray

#8109: Server-side support for TLS Server Name Indication extension
http://bugs.python.org/issue8109  reopened by pitrou

#10789: Lock.acquire documentation is misleading
http://bugs.python.org/issue10789  reopened by terry.reedy

#10803: ctypes: better support of bytearray objects
http://bugs.python.org/issue10803  opened by mfxmfx

#10805: traceback.print_exception throws AttributeError when exception
http://bugs.python.org/issue10805  opened by abingham

#10808: ssl unwrap fails with Error 0
http://bugs.python.org/issue10808  opened by apollo13

#10811: sqlite segfault with generators
http://bugs.python.org/issue10811  opened by Erick.Tryzelaar

#10812: Add some posix functions
http://bugs.python.org/issue10812  opened by rosslagerwall

#10813: Suppress adding decimal point for places=0 in moneyfmt()
http://bugs.python.org/issue10813  opened by cgrohmann

#10817: urllib.request.urlretrieve never raises ContentTooShortError i
http://bugs.python.org/issue10817  opened by RC

#10818: pydoc: Remove old server and tk panel
http://bugs.python.org/issue10818  opened by haypo

#10820: 3.2 Makefile changes for versioned scripts break OS X framewor
http://bugs.python.org/issue10820  opened by ned.deily

#10822: test_getgroups failure under Solaris
http://bugs.python.org/issue10822  opened by pitrou

#10826: pass_fds sometimes fails
http://bugs.python.org/issue10826  opened by pitrou

#10827: Functions in time module should support year  1900 when accep
http://bugs.python.org/issue10827  opened by belopolsky

#10829: PyUnicode_FromFormatV() bugs with % and %% format strings
http://bugs.python.org/issue10829  opened by haypo

#10830: PyUnicode_FromFormatV(%c) doesn't support non-BMP characters
http://bugs.python.org/issue10830  opened by haypo

#10831: PyUnicode_FromFormatV() doesn't support %li, %lli, %zi
http://bugs.python.org/issue10831  opened by haypo

#10832: Add support of bytes objects in PyBytes_FromFormatV()
http://bugs.python.org/issue10832  opened by haypo

#10833: Replace %.100s by %s in PyErr_Format(): the arbitrary limit of
http://bugs.python.org/issue10833  opened by haypo

#10834: Python 2.7 x86 fails to run in Windows 7
http://bugs.python.org/issue10834  opened by excubated

#10835: sys.executable default and altinstall
http://bugs.python.org/issue10835  opened by allan

#10836: TypeError during exception handling in urllib.request.urlretri
http://bugs.python.org/issue10836  opened by Alexandru.MoÈ^(TM)oi

#10837: Issue catching KeyboardInterrupt while reading stdin
http://bugs.python.org/issue10837  opened by Josh.Hanson

#10838: subprocess __all__ is incomplete
http://bugs.python.org/issue10838  opened by a.badger

#10839: email module should not allow some header field repetitions
http://bugs.python.org/issue10839  opened by adrien-saladin

#10841: binary stdio
http://bugs.python.org/issue10841  opened by v+python

#10842: Update third-party libraries for OS X installer builds
http://bugs.python.org/issue10842  opened by ned.deily

#10843: OS X installer: install the Tools source directory
http://bugs.python.org/issue10843  opened by ned.deily

#10845: test_multiprocessing failure under Windows
http://bugs.python.org/issue10845  opened by pitrou

#10847: Distutils drops -fno-strict-aliasing when CFLAGS are set
http://bugs.python.org/issue10847  opened by skrah

#10848: Move test.regrtest from getopt to argparse
http://bugs.python.org/issue10848  opened by brett.cannon

#10849: Backport test/__main__
http://bugs.python.org/issue10849  opened by belopolsky

#10850: inconsistent behavior concerning multiprocessing.manager.BaseM
http://bugs.python.org/issue10850  opened by chrysn

#10851: further extend ssl SNI and ciphers API
http://bugs.python.org/issue10851  opened by grooverdan

#10852: SSL/TLS sni use in smtp,pop,imap,nntp,ftp client libs by defau
http://bugs.python.org/issue10852  opened by grooverdan

#10854: Output DLL name in error message of ImportError when DLL is mi
http://bugs.python.org/issue10854  opened by techtonik

#10855: wave.Wave_read.close() doesn't release file
http://bugs.python.org/issue10855  opened by pjcreath

#10856: documentation for ImportError parameters and attributes
http://bugs.python.org/issue10856  opened by techtonik

#10828: Cannot use nonascii utf8 in names of files imported from
http://bugs.python.org/issue10828  opened by ingemar



Most recent 

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

2011-01-07 Thread Michael Foord

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 20138 (+80)
   total  22639 (+56)



Nice work everyone. :-)

At this rate we'll be down to zero open issues in only 2 years. ;-)

Michael

--
http://www.voidspace.org.uk/

May you do good and not evil
May you find forgiveness for yourself and forgive others
May you share freely, never taking more than you give.
-- the sqlite blessinghttp://www.sqlite.org/different.html

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2011-01-07 Thread anatoly techtonik
On Fri, Jan 7, 2011 at 7:55 PM, Michael Foord fuzzy...@voidspace.org.uk 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 message.

 Issues counts and deltas:
   open    2501 (-24)
   closed 20138 (+80)
   total  22639 (+56)


 Nice work everyone. :-)

 At this rate we'll be down to zero open issues in only 2 years. ;-)

Less users - less issues. It's always easy to speedup the process by
leaving the most irritating ones. ;)
--
anatoly t.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2011-01-07 Thread Alexander Belopolsky
On Fri, Jan 7, 2011 at 1:17 PM, anatoly techtonik techto...@gmail.com 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 the summary more carefully before leaving a witty
comment like this.  Hint: total  22639 (+56).
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-11-06 Thread Georg Brandl
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 message.

 Issues counts and deltas:
open2514 (+17)
closed 19597 (+78)
total  22111 (+95)
 
 as suggested in recent mails[0][1] I changed these values to represent 
 the deltas with the previous week.
 Now let's try to keep the open delta negative ;)

That is a worthy goal, however the difference between the open and closed
deltas is already quite an achievement and shows that our triage works.

Georg

-- 
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-11-06 Thread R. David Murray
On Sat, 06 Nov 2010 15:38:22 +0100, Georg Brandl g.bra...@gmx.net 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 issues listed below, click on the issue.
  Do NOT respond to this message.
 
  Issues counts and deltas:
 open2514 (+17)
 closed 19597 (+78)
 total  22111 (+95)
  
  as suggested in recent mails[0][1] I changed these values to represent 
  the deltas with the previous week.
  Now let's try to keep the open delta negative ;)
 
 That is a worthy goal, however the difference between the open and closed
 deltas is already quite an achievement and shows that our triage works.

Agreed.

We did have negative open deltas for several weeks running in October.
Kudos to everyone involved, and lets do it some more :)  I'm looking
forward to making a non-trivial dent in the open count during the bug
weekend on the 20th/21st.

--
R. David Murray  www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-11-06 Thread Terry Reedy

On 11/6/2010 11:42 AM, R. David Murray wrote:

On Sat, 06 Nov 2010 15:38:22 +0100, Georg Brandlg.bra...@gmx.net  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 issues listed below, click on the issue.
Do NOT respond to this message.

Issues counts and deltas:
open2514 (+17)


This seems wrong. A default search for open issues returns 2452 and it 
was about the same yesterday just a few hours after the report.



closed 19597 (+78)
total  22111 (+95)


as suggested in recent mails[0][1] I changed these values to represent
the deltas with the previous week.
Now let's try to keep the open delta negative ;)


Since there were more issues closed than opened I think it really was. 
Anyway, we are down 300 from the 2750 peak.



That is a worthy goal, however the difference between the open and closed
deltas is already quite an achievement and shows that our triage works.


Agreed.

We did have negative open deltas for several weeks running in October.
Kudos to everyone involved, and lets do it some more :)  I'm looking
forward to making a non-trivial dent in the open count during the bug
weekend on the 20th/21st.



--
Terry Jan Reedy

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-11-06 Thread Ezio Melotti

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 Brandlg.bra...@gmx.net  
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 issues listed below, click on the 
issue.

Do NOT respond to this message.

Issues counts and deltas:
open2514 (+17)


This seems wrong. A default search for open issues returns 2452 and it 
was about the same yesterday just a few hours after the report.




That's because the open count includes about 25 languishing and 39 
pending issues (technically they are still open).



closed 19597 (+78)
total  22111 (+95)


as suggested in recent mails[0][1] I changed these values to represent
the deltas with the previous week.
Now let's try to keep the open delta negative ;)


Since there were more issues closed than opened I think it really was. 
Anyway, we are down 300 from the 2750 peak.


That is a worthy goal, however the difference between the open and 
closed

deltas is already quite an achievement and shows that our triage works.


Yes, even if having a negative delta would be best, having the closed 
delta higher than then open one is still very good.

So congrats to everyone who worked and works to make this possible.



Agreed.

We did have negative open deltas for several weeks running in October.
Kudos to everyone involved, and lets do it some more :)  I'm looking
forward to making a non-trivial dent in the open count during the bug
weekend on the 20th/21st.



Best Regards,
Ezio Melotti
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-11-06 Thread Ron Adam



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 Brandlg.bra...@gmx.net 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 issues listed below, click on the
issue.
Do NOT respond to this message.

Issues counts and deltas:
open 2514 (+17)


This seems wrong. A default search for open issues returns 2452 and it
was about the same yesterday just a few hours after the report.


closed 19597 (+78)
total 22111 (+95)


as suggested in recent mails[0][1] I changed these values to represent
the deltas with the previous week.
Now let's try to keep the open delta negative ;)


Since there were more issues closed than opened I think it really was.
Anyway, we are down 300 from the 2750 peak.


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
1 not selected
 
 2491 total not closed


 19604 closed
  2491 not closed
39 pending
 -
 22134 Total issues



My guess as to how this got this way, is that different fields were merged 
at some time where the meanings didn't quite match up. shrug



It would be nicer if...

   closed + not_closed = total issues

   closed + open + not_selected = total issues


Pending and languishing should be keywords or sub categories of open.

Cheers,
   Ron





___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-11-06 Thread Ron Adam




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 languishing.

--Ron


1 not selected

2491 total not closed


19604 closed
2491 not closed
39 pending
-
22134 Total issues


___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-11-05 Thread 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 message.

Issues counts and deltas:
   open2514 (+17)
   closed 19597 (+78)
   total  22111 (+95)


as suggested in recent mails[0][1] I changed these values to represent 
the deltas with the previous week.

Now let's try to keep the open delta negative ;)

Best Regards,
Ezio Melotti

[0]: http://mail.python.org/pipermail/python-dev/2010-October/104840.html
[1]: http://mail.python.org/pipermail/python-dev/2010-September/104054.html
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-10-23 Thread Martin v. Löwis
 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 32 issue have been opened-and-not-closed
in the week.

You can see these 32 issues further down in the message.

Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-10-22 Thread Antoine Pitrou
On Fri, 22 Oct 2010 18:08:20 +0200 (CEST)
Python tracker sta...@bugs.python.org 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:
   open2494 (+32)
   closed 19460 (+110)
   total  21954 (+56)

The figures in parentheses look wrong. Last week, the stats said:

 Issues stats:
   open2557 (+37)
   closed 19276 (+30)
   total  21833 (+44)

So, logically, this week's stats should say:

  open2494 (-63)
  closed 19460 (+184)
  total  21954 (+121)

Regards

Antoine.


___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-25 Thread Georg Brandl
Am 25.09.2010 03:45, schrieb Brett Cannon:
 On Fri, Sep 24, 2010 at 13:04, Georg Brandl g.bra...@gmx.net 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 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 those two counts which in total must sum
 up to the total difference in issues.

 If I understand correctly how the counters work, they at least need to
 be renamed -- they do *not* count open/closed issues, they count
 openings/closings.
 
 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 -- is not obvious from the report.

Georg

-- 
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-25 Thread 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 open bugs
 at the end of the week than at the start -- is not obvious from the report.

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 are *not* deltas, but the
number of issues opened since last week. As some open issues were closed
and some closed issues were opened, they don't sum up the way you
expect. An example:

old:
  open:   #1 #2
  closed: #3 #4
new:
  open:   #1 #3 #5
  closed: #2 #4

The report would be

  open: 3 (+2, namely #3 and #5); delta would be +1
  closed: 2 (+1, namely #4); delta would be 0

IOW, the numbers after +/- match the counts in the lists shown below,
not the delta since last week.

HTH,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-25 Thread Georg Brandl
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 open bugs
 at the end of the week than at the start -- is not obvious from the report.
 
 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 are *not* deltas, but the
 number of issues opened since last week. As some open issues were closed
 and some closed issues were opened, they don't sum up the way you
 expect. An example:
 
 old:
   open:   #1 #2
   closed: #3 #4
 new:
   open:   #1 #3 #5
   closed: #2 #4
 
 The report would be
 
   open: 3 (+2, namely #3 and #5); delta would be +1
   closed: 2 (+1, namely #4); delta would be 0
 
 IOW, the numbers after +/- match the counts in the lists shown below,
 not the delta since last week.

Yes, and that's what I complained about. However, your example doesn't
demonstrate my problem, since its deltas *are* real deltas, and
+1 + +0 == +1.

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 these numbers should be labeled openings and closings.

Georg

-- 
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-25 Thread 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 obvious from the report.


As of just now, the default search for all open issues returns 2475. 
That is down steadily over the last 8 or so weeks from a peak of about 
2750 in early June. About 30 people have closed at least one issue in 
this period.


The current figure is up from about 1200 a few years ago. Part of the 
increase is due to the 2.x to 3.x transition and the bulge from 2 to 4 
active issues. I would roughly guess that there are perhap a couple 
hundred 2.7-only issue. You just closed one today.


--
Terry Jan Reedy

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-25 Thread Georg Brandl
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 obvious from the report.
 
 As of just now, the default search for all open issues returns 2475. 
 That is down steadily over the last 8 or so weeks from a peak of about 
 2750 in early June. About 30 people have closed at least one issue in 
 this period.

That's really promising.  (And that's also why I want to see a negative delta
for the open count.)  Thanks for these numbers!

Georg

-- 
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-25 Thread R. David Murray
On Sat, 25 Sep 2010 14:22:06 +0200, Georg Brandl g.bra...@gmx.net 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 are *not* deltas, but the
  number of issues opened since last week. As some open issues were closed
  and some closed issues were opened, they don't sum up the way you
  expect. An example:
 
  old:
open:   #1 #2
closed: #3 #4
  new:
open:   #1 #3 #5
closed: #2 #4
 
  The report would be
 
open: 3 (+2, namely #3 and #5); delta would be +1
closed: 2 (+1, namely #4); delta would be 0
 
  IOW, the numbers after +/- match the counts in the lists shown below,
  not the delta since last week.
 
 Yes, and that's what I complained about. However, your example doesn't
 demonstrate my problem, since its deltas *are* real deltas, and
 +1 + +0 = +1.
 
 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.  Th=
 is why I think these numbers should be labeled openings and closings.

I haven't looked at the code, so I don't know the details of the
algorithm that is actually used, but from what Ezio said your example
is *not* correct.  The numbers in parenthesis are the number of issues
opened/closed in the past week that are *still* open or closed.  So open
would certainly not be +2.  I'm not sure if it would be +0 or -1 without
looking at the code.

I agree that having the delta against open from the previous week would
be the most helpful.

--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-25 Thread 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), however the total issue delta is +2.  This
 is why I think these numbers should be labeled openings and closings.

I *have* looked at the code, any I'm certain that this is not how the
computation goes.

Instead, I'm also certain that it goes as in the message I sent.
Notice that it prints the numbers I put into parentheses (+2, +1),
and they do *not* sum up to +1. The numbers I posted as delta would
be are not currently included in the report.

Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-25 Thread Georg Brandl
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), however the total issue delta is +2.  This
 is why I think these numbers should be labeled openings and closings.
 
 I *have* looked at the code, any I'm certain that this is not how the
 computation goes.
 
 Instead, I'm also certain that it goes as in the message I sent.
 Notice that it prints the numbers I put into parentheses (+2, +1),
 and they do *not* sum up to +1. The numbers I posted as delta would
 be are not currently included in the report.

Ah. I misunderstood, sorry.  Well, let's bury this thread then and I will
put it on my todo list to modify it to work as expected.

Georg

-- 
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-25 Thread Terry Reedy

On 9/25/2010 1:08 PM, Antoine Pitrou wrote:

On Sat, 25 Sep 2010 19:02:06 +0200
Georg Brandlg.bra...@gmx.net  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 less open bugs
at the end of the week than at the start -- is not obvious from the report.


As of just now, the default search for all open issues returns 2475.
That is down steadily over the last 8 or so weeks from a peak of about
2750 in early June. About 30 people have closed at least one issue in
this period.


That's really promising.  (And that's also why I want to see a negative delta
for the open count.)  Thanks for these numbers!


Without any precision on how and why these bugs were closed, these
numbers don't mean anything. We would need a breakdown of bug closings
according to the resolution field, at the minimum.


Doing some hand-counting because I do not have proper (as in sql query) 
access to the database, closed issues so far for Activity: 2010-09


174 fixed
 36 invalid
 31 out of date
  1 postponed
 18 reject
 18 won't fix
  7 works for me
---
285

--
Terry Jan Reedy

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-24 Thread Brett Cannon
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 sta...@bugs.python.org wrote:

 ACTIVITY SUMMARY (2010-09-17 - 2010-09-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 stats:
  open    2533 (+42)
  closed 19189 (+57)
  total  21722 (+53)

 Open issues with patches: 1061


 Issues opened (42)
 ==

 #1763: Winpath module - easy access to Windows directories like My Do
 http://bugs.python.org/issue1763  reopened by r.david.murray

 #6627: threading.local() does not work with C-created threads
 http://bugs.python.org/issue6627  reopened by Nikratio

 #9441: increase logging handlers test coverage
 http://bugs.python.org/issue9441  reopened by r.david.murray

 #9552: ssl build under Windows always rebuilds OpenSSL
 http://bugs.python.org/issue9552  reopened by ocean-city

 #9877: Expose sysconfig._get_makefile_filename() in public API
 http://bugs.python.org/issue9877  reopened by eric.araujo

 #9889: PyUnicode_FormatV and Py_UNICODE*?
 http://bugs.python.org/issue9889  opened by mkleehammer

 #9890: Visual C++ Runtime Library Error is there a fix?
 http://bugs.python.org/issue9890  opened by Hydro56

 #9891: Minor doc typo at datamodel.rst: list - alist
 http://bugs.python.org/issue9891  opened by rbp

 #9893: Usefulness of the Misc/Vim/ files?
 http://bugs.python.org/issue9893  opened by pitrou

 #9896: Introspectable range objects
 http://bugs.python.org/issue9896  opened by durban

 #9897: multiprocessing problems
 http://bugs.python.org/issue9897  opened by hume

 #9903: test_concurrent_futures writes on stderr
 http://bugs.python.org/issue9903  opened by pitrou

 #9904: Cosmetic issues that may warrant a fix in symtable.h/c
 http://bugs.python.org/issue9904  opened by eli.bendersky

 #9905: subprocess.Popen fails with stdout=PIPE, stderr=PIPE if standa
 http://bugs.python.org/issue9905  opened by Thomas.Claveirole

 #9907: interactive mode TAB does not insert on OS X built with editli
 http://bugs.python.org/issue9907  opened by ned.deily

 #9909: request for calendar.dayofyear() function
 http://bugs.python.org/issue9909  opened by jfinkels

 #9910: Add Py_SetPath API for embeddint python
 http://bugs.python.org/issue9910  opened by krisvale

 #9912: Fail when vsvarsall.bat produces stderr
 http://bugs.python.org/issue9912  opened by flub

 #9913: Misc/SpecialBuilds.txt  is out of date
 http://bugs.python.org/issue9913  opened by belopolsky

 #9914: trace/profile conflict with the use of sys.modules[__name__]
 http://bugs.python.org/issue9914  opened by belopolsky

 #9915: speeding up sorting with a key
 http://bugs.python.org/issue9915  opened by stutzbach

 #9917: resource max value represented as signed when should be unsign
 http://bugs.python.org/issue9917  opened by r.david.murray

 #9919: gdbinit lineno result is one line in excess
 http://bugs.python.org/issue9919  opened by qpatata

 #9920: test_cmath on atan fails on AIX
 http://bugs.python.org/issue9920  opened by sable

 #9921: os.path.join('x','') behavior
 http://bugs.python.org/issue9921  opened by rgrig

 #9922: subprocess.getstatusoutput can fail with utf8 UnicodeDecodeErr
 http://bugs.python.org/issue9922  opened by debatem1

 #9923: mailcap module may not work on non-POSIX platforms if MAILCAPS
 http://bugs.python.org/issue9923  opened by gnofi

 #9924: sqlite3 SELECT does not BEGIN a transaction, but should accord
 http://bugs.python.org/issue9924  opened by zzzeek

 #9925: Idle doesn't launch
 http://bugs.python.org/issue9925  opened by Stephan.Bellegy

 #9926: Wrapped TestSuite subclass does not get __call__ executed
 http://bugs.python.org/issue9926  opened by loewis

 #9927: Leak around GetFinalPathNameByHandle (Windows)
 http://bugs.python.org/issue9927  opened by ocean-city

 #9929: subprocess.Popen unbuffered not work
 http://bugs.python.org/issue9929  opened by ocean-city

 #9931: test_ttk_guionly hangs on XP5
 http://bugs.python.org/issue9931  opened by ocean-city

 #9934: Python Docs Typo
 http://bugs.python.org/issue9934  opened by Retro

 #9935: Faster pickling of instances
 http://bugs.python.org/issue9935  opened by pitrou

 #9936: trace misreports missing lines
 http://bugs.python.org/issue9936  opened by belopolsky

 #9937: _winreg.EnumValue causes MemoryError
 http://bugs.python.org/issue9937  opened by kzmi

 #9938: Documentation for argparse interactive use
 http://bugs.python.org/issue9938  opened by jayt

 #9939: Add a pipe type (FIFO) to the io module
 http://bugs.python.org/issue9939  opened by pitrou

 #9940: Strange error reporting with with statement
 http://bugs.python.org/issue9940  opened by pitrou

 #1724822: provide a shlex.split alternative for Windows shell syntax
 

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

2010-09-24 Thread Georg Brandl
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! =) 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 sta...@bugs.python.org wrote:

 ACTIVITY SUMMARY (2010-09-17 - 2010-09-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 stats:
  open2533 (+42)
  closed 19189 (+57)
  total  21722 (+53)

 Open issues with patches: 1061

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-24 Thread Brett Cannon
On Fri, Sep 24, 2010 at 12:57, Georg Brandl g.bra...@gmx.net 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
deltas can apply to pre-existing bugs, e.g., a bug that was re-opened.

-Brett


 Georg

 Am 24.09.2010 20:00, schrieb Brett Cannon:
 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 sta...@bugs.python.org wrote:

 ACTIVITY SUMMARY (2010-09-17 - 2010-09-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 stats:
  open    2533 (+42)
  closed 19189 (+57)
  total  21722 (+53)

 Open issues with patches: 1061

 ___
 Python-Dev mailing list
 Python-Dev@python.org
 http://mail.python.org/mailman/listinfo/python-dev
 Unsubscribe: 
 http://mail.python.org/mailman/options/python-dev/brett%40python.org

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-24 Thread Georg Brandl
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 those two counts which in total must sum
up to the total difference in issues.

If I understand correctly how the counters work, they at least need to
be renamed -- they do *not* count open/closed issues, they count
openings/closings.

Georg

Am 24.09.2010 22:00, schrieb Brett Cannon:
 On Fri, Sep 24, 2010 at 12:57, Georg Brandl g.bra...@gmx.net 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
 deltas can apply to pre-existing bugs, e.g., a bug that was re-opened.
 
 -Brett
 

 Georg

 Am 24.09.2010 20:00, schrieb Brett Cannon:
 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 sta...@bugs.python.org 
 wrote:

 ACTIVITY SUMMARY (2010-09-17 - 2010-09-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 stats:
  open2533 (+42)
  closed 19189 (+57)
  total  21722 (+53)

 Open issues with patches: 1061

 ___
 Python-Dev mailing list
 Python-Dev@python.org
 http://mail.python.org/mailman/listinfo/python-dev
 Unsubscribe: 
 http://mail.python.org/mailman/options/python-dev/brett%40python.org

 ___
 Python-Dev mailing list
 Python-Dev@python.org
 http://mail.python.org/mailman/listinfo/python-dev
 Unsubscribe: 
 http://mail.python.org/mailman/options/python-dev/python-python-dev%40m.gmane.org


-- 
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-24 Thread Brett Cannon
On Fri, Sep 24, 2010 at 13:04, Georg Brandl g.bra...@gmx.net 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 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 those two counts which in total must sum
 up to the total difference in issues.

 If I understand correctly how the counters work, they at least need to
 be renamed -- they do *not* count open/closed issues, they count
 openings/closings.

Guess the only way to settle this is look at the code, but I don't
care enough to bother. =)

-Brett


 Georg

 Am 24.09.2010 22:00, schrieb Brett Cannon:
 On Fri, Sep 24, 2010 at 12:57, Georg Brandl g.bra...@gmx.net 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
 deltas can apply to pre-existing bugs, e.g., a bug that was re-opened.

 -Brett


 Georg

 Am 24.09.2010 20:00, schrieb Brett Cannon:
 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 sta...@bugs.python.org 
 wrote:

 ACTIVITY SUMMARY (2010-09-17 - 2010-09-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 stats:
  open    2533 (+42)
  closed 19189 (+57)
  total  21722 (+53)

 Open issues with patches: 1061

 ___
 Python-Dev mailing list
 Python-Dev@python.org
 http://mail.python.org/mailman/listinfo/python-dev
 Unsubscribe: 
 http://mail.python.org/mailman/options/python-dev/brett%40python.org

 ___
 Python-Dev mailing list
 Python-Dev@python.org
 http://mail.python.org/mailman/listinfo/python-dev
 Unsubscribe: 
 http://mail.python.org/mailman/options/python-dev/python-python-dev%40m.gmane.org


 --
 Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
 Four shall be the number of spaces thou shalt indent, and the number of thy
 indenting shall be four. Eight shalt thou not indent, nor either indent thou
 two, excepting that thou then proceed to four. Tabs are right out.

 ___
 Python-Dev mailing list
 Python-Dev@python.org
 http://mail.python.org/mailman/listinfo/python-dev
 Unsubscribe: 
 http://mail.python.org/mailman/options/python-dev/brett%40python.org

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-05 Thread Paul Moore
On 3 September 2010 17:41, Paul Moore p.f.mo...@gmail.com wrote:
 On 3 September 2010 17:30, Victor Stinner victor.stin...@haypocalc.com 
 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.

Odd. There's 2GB free on the disk (not a lot, but it's only a 19GB
disk and it's had the same amount of free space for ages). I suspect
that it's something that has changed triggering an error which is
getting reported as space but isn't actually (IIRC, you can get that
error from things like broken pipes on Windows).

I'll keep digging when I get the chance, but I've not got much free
time just now, so it may be a while...
Paul.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-03 Thread Victor Stinner
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 x86 XP-5 * build slaves.

-- 
Victor Stinner
http://www.haypocalc.com/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-09-03 Thread Paul Moore
On 3 September 2010 17:30, Victor Stinner victor.stin...@haypocalc.com 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.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-08-20 Thread Florent Xicluna
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 (probably) linked with an existing issue
   (the association [failure] -- [issue] is based on regexp rules)

 - *No recent failure* : these issues are no longer reported on recent
builds. Either the problem is fixed, or the failure is elusive.

The page is hosted on Google Code. Victor hosts a cron job which
recalculates and upload the JSON data.
Currently, the report is uploaded every hour.

Regards,

-- 
Florent Xicluna

2010/8/20 Python tracker

 ACTIVITY SUMMARY (2010-08-13 - 2010-08-20)
 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    2624 (+44)
  closed 18808 (+80)
  total  21432 (+63)

 Open issues with patches: 1110


 Issues opened (44)
 ==

 #9189: Improve CFLAGS handling
 http://bugs.python.org/issue9189  reopened by skrah

 #9445: Fix undefined symbol errors on VS8.0 build
 http://bugs.python.org/issue9445  reopened by amaury.forgeotdarc

 #9591: kqueue not reporting EOF under certain circumstances
 http://bugs.python.org/issue9591  opened by Volodymyr.Kostyrko

 #9592: Limitations in objects returned by multiprocessing Pool
 http://bugs.python.org/issue9592  opened by macfreek

 #9594: typo on Mac/Makefile.in? s/pythonw/python/
 http://bugs.python.org/issue9594  opened by srid

 #9597: mac: Install 2to3 in /usr/local/bin
 http://bugs.python.org/issue9597  opened by srid

 #9598: untabify.py fails on files that contain non-ascii characters
 http://bugs.python.org/issue9598  opened by belopolsky

 #9601: ftplib should accept 250 on MKD
 http://bugs.python.org/issue9601  opened by alphablue52

 #9602: PyObject_AsCharBuffer() should only accept read-only objects
 http://bugs.python.org/issue9602  opened by haypo

 #9607: Test file 'test_keyword.py' submission for use with keyword.py
 http://bugs.python.org/issue9607  opened by gregmalcolm

 #9608: Re-phrase best way of using exceptions in doanddont.rst
 http://bugs.python.org/issue9608  opened by flub

 #9609: make cProfile multi-stack aware
 http://bugs.python.org/issue9609  opened by krisvale

 #9610: buildbot: uncaptured python exception (smtpd), but no failure
 http://bugs.python.org/issue9610  opened by flox

 #9611: FileIO not 64-bit safe under Windows
 http://bugs.python.org/issue9611  opened by pitrou

 #9613: Python considers pid longs under 64-bit Windows
 http://bugs.python.org/issue9613  opened by pitrou

 #9614: _pickle is not entirely 64-bit safe
 http://bugs.python.org/issue9614  opened by pitrou

 #9617: Buffered IO shouldn't ignore incoming signals during a partial
 http://bugs.python.org/issue9617  opened by pitrou

 #9618: IDLE shell ignores all but first statement
 http://bugs.python.org/issue9618  opened by cben

 #9620: Python 2.7 IDLE fails on OS X 10.6
 http://bugs.python.org/issue9620  opened by bpumali

 #9621: Graphviz output for 2to3 fixer patterns
 http://bugs.python.org/issue9621  opened by gmattbond

 #9622: Allow to set profile/trace function globally
 http://bugs.python.org/issue9622  opened by krisvale

 #9624: 2755
 http://bugs.python.org/issue9624  opened by Kartton

 #9625: argparse: Problem with defaults for variable nargs
 http://bugs.python.org/issue9625  opened by thesociable

 #9628: runtests.sh -x doesn't work with more than two args (sed error
 http://bugs.python.org/issue9628  opened by dmalcolm

 #9630: Reencode filenames when setting the filesystem encoding
 http://bugs.python.org/issue9630  opened by haypo

 #9631: Python 2.7 installation issue for Linux gcc-4.1.0-3 (Fedora Co
 http://bugs.python.org/issue9631  opened by spprakash

 #9632: Remove sys.setfilesystemencoding()
 http://bugs.python.org/issue9632  opened by haypo

 #9633: pdb go stack up/down
 http://bugs.python.org/issue9633  opened by Markus.Pröller

 #9634: Add timeout parameter to Queue.join()
 http://bugs.python.org/issue9634  opened by kdlucas

 #9635: Add Py_BREAKPOINT and sys.breakpoint hooks
 http://bugs.python.org/issue9635  opened by dmalcolm

 #9637: docs do not say that urllib uses HTTP_PROXY
 http://bugs.python.org/issue9637  opened by kirikaza

 #9640: Improved doctest REPORT_*DIFFs with ELLIPSIS and/or NORMALIZE_
 http://bugs.python.org/issue9640  opened by labrat

 #9642: #ifdef and mbcs: don't check for defined(HAVE_USABLE_WCHAR_T)
 http://bugs.python.org/issue9642  opened by haypo

 #9643: urllib2 - Basic,Digest Proxy Auth Handlers failure will give 4
 http://bugs.python.org/issue9643  opened by orsenthil

 #9644: PEP 383: os.statvfs() does not accept surrogateescape argument
 http://bugs.python.org/issue9644  opened by baikie

 #9645: PEP 383: os.pathconf() does not accept 

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

2010-08-20 Thread Victor Stinner
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 an issue in
 the tracker
 
  - *Known issues* : failures which are (probably) linked with an existing
 issue (the association [failure] -- [issue] is based on regexp rules)

There is a configuration file, bbreport.conf, which uses some patterns to match 
an issue:

 - test name (regex)
 - message (regex)
 - builder (regex)

All fields are optional, but it's better to set at least one field :-)

Extract of the config:
---
8265: test_float::ARMv4 Debian (2.6|3.1)
8423: test_pep277::x86 Tiger (2.7|3.x)
8428: test_multiprocessing::(x86 FreeBSD 7.2 3.x|x86 Windows7 3.1|.* 2.7)
8429: test_subprocess:hung:
8431: :hung:(ARM|.* debian parallel)
---

-- 
Victor Stinner
http://www.haypocalc.com/
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-08-10 Thread Ezio Melotti

 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 week.
(This was supposed to be the report for last week, but it's from Monday 
to Sunday instead of from Saturday to Friday because I specified the 
wrong dates.)



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:
   open2640 (+35)
   closed 18679 (+194)
   total  21319 (+57)


The +35 means that there are 35 more issues opened since the last week. 
This is not the number of issues that have been created during the last 
week, but the number of new issues that have been created or reopened 
that are still open. Also note that 'pending' and 'languishing' are 
considered as 'open' too.
The +194 means that are 194 more issues closed since last week that are 
still closed.

Both the open and closed issues are listed later.
The +57 means that overall the tracker has 57 more issues since last 
week. This also mean that about 25 issues created this week are already 
closed (i.e. 57 new - (35 still open - 3 older that got reopened) = 25 
issues).



Open issues with patches: 1112



This is the total number of open issues with the 'patch' keyword.


Issues opened (35)
==

#8821: Range check on unicode repr
http://bugs.python.org/issue8821  reopened by pitrou
[...]


This is the list of *all* the issues created or reopened during the last 
week *that are still open*.



Recent issues with no replies (15)
==

#9535: Pending signals are inherited by child processes
http://bugs.python.org/issue9535
[...]


This is the list of the open issues with only 1 message, sorted by 
creation date.
The list is limited to max 15 issues but is not limited to the last 
week. This means that issues older than a week are included here if less 
than 15 issues with only 1 message have been created this week.



Issues waiting for review (15)
==

#1474680: pickling files works with protocol=2.
http://bugs.python.org/issue1474680
[...]


This is the list of issues with 'patch' or 'needs review' keywords or 
'patch review' stage that have been active during the last week.

The list is limited to max 15 issues.


Top issues most discussed (10)
==

#9079: Make gettimeofday available in time module
http://bugs.python.org/issue9079  42 msgs
[...]


This is the list of issues with activity in the last week sorted by 
number of message.

This list is limited to max 10 issues.


Issues closed (154)
===

#1474680: pickling files works with protocol=2.
http://bugs.python.org/issue1474680  closed by alexandre.vassalotti
[...]


This is the list of *all* the issues closed in the last week *that are 
still closed*.
Since this list might be quite long I put it at the end, to make it 
easier to reach the other lists.



The previous report also had the average and median durations of open 
issues.
While I was refactoring the function that calculated them, I realized 
that these values are not so useful/clear so I decided to remove them. 
These values could be added back if they are needed, but it might be 
more interesting to know how long does it usually take for an issue to 
be closed, rather than for how long the open issues are around.


For more information see 
http://psf.upfronthosting.co.za/roundup/meta/issue284.


Best Regards,
Ezio Melotti

P.S.: Thanks to R. David Murray that helped me out with the testing and 
to all the people who provided (and will provide) feedback.

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-08-10 Thread R. David Murray
On Tue, 10 Aug 2010 17:28:18 +0300, Ezio Melotti ezio.melo...@gmail.com 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)
 
 The +35 means that there are 35 more issues opened since the last week. 
 This is not the number of issues that have been created during the last 
 week, but the number of new issues that have been created or reopened 
 that are still open. Also note that 'pending' and 'languishing' are 
 considered as 'open' too.

How about changing the label to 'not closed' to make that clear?

  Issues opened (35)
  ==
 
  #8821: Range check on unicode repr
  http://bugs.python.org/issue8821  reopened by pitrou
  [...]
 
 This is the list of *all* the issues created or reopened during the last 
 week *that are still open*.

I wonder if it would be useful to split this into two tables, one for
new issues still open and one for reopened issues.  I think the mental
space in which one considers re-opened issues is different from the
one for new issues.  In particular, a developer who doesn't have time
to scan the new issues might notice a reopened issue they were involved
in but haven't yet looked at their 'nosy' email about.  Perhaps not
worth the effort, it's just a thought.

  Recent issues with no replies (15)
  ==
 
  #9535: Pending signals are inherited by child processes
  http://bugs.python.org/issue9535
  [...]
 
 This is the list of the open issues with only 1 message, sorted by 
 creation date.
 The list is limited to max 15 issues but is not limited to the last 
 week. This means that issues older than a week are included here if less 
 than 15 issues with only 1 message have been created this week.
 
  Issues waiting for review (15)
  ==
 
  #1474680: pickling files works with protocol=2.
  http://bugs.python.org/issue1474680
  [...]
 
 This is the list of issues with 'patch' or 'needs review' keywords or 
 'patch review' stage that have been active during the last week.
 The list is limited to max 15 issues.

For both of these I think it is important that the fact that they
are limited to 15 be mentioned in the section header.

The issues needing review is a great addition, probably every bit
as valuable as the no replies report.  I hope that it, too, will
draw on the previous weeks if there are less than fifteen that
were active in the current week?

  Top issues most discussed (10)
  ==
 
  #9079: Make gettimeofday available in time module
  http://bugs.python.org/issue9079  42 msgs
  [...]
 
 This is the list of issues with activity in the last week sorted by 
 number of message.
 This list is limited to max 10 issues.

I've already talked with Ezio in IRC about the fact that this list
represents a regression from the old report, since the old report
gave the issues with the most messages *during the week* whereas
his current looks at the *total* message count for any issue that
has had *any* activity during the current week.  He's going to fix
that.

  Issues closed (154)
  ===
 
  #1474680: pickling files works with protocol=2.
  http://bugs.python.org/issue1474680  closed by alexandre.vassalotti
  [...]
 
 This is the list of *all* the issues closed in the last week *that are 
 still closed*.
 Since this list might be quite long I put it at the end, to make it 
 easier to reach the other lists.

It would be lovely if we could manage to get this one to be the
longest table in the report each week :)

--
R. David Murray  www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2010-08-10 Thread Terry Reedy

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 Reedy

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2009-04-24 Thread Terry Reedy

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

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2009-04-24 Thread Mark Dickinson
On Fri, Apr 24, 2009 at 9:25 PM, Terry Reedy tjre...@udel.edu 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 in this at PyCon, and then taken on
the major internal replumbing job this entailed for all of Python's
string formatting.

 3.1.  As a certain-to-be beneficiary, I want to thank all who contributed.

Glad you like it!

Mark
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2009-04-24 Thread Eric Smith

Mark Dickinson wrote:

On Fri, Apr 24, 2009 at 9:25 PM, Terry Reedy tjre...@udel.edu 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 in this at PyCon, and then taken on
the major internal replumbing job this entailed for all of Python's
string formatting.


Not to get too much into a mutual admiration mode, but Mark did the 
parts involving hard thinking.



3.1.  As a certain-to-be beneficiary, I want to thank all who contributed.


Glad you like it!


Me, too. I think it's going to be great once we get it all straightened 
out. And I think we're close!


Eric.

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2009-02-20 Thread Daniel (ajax) Diniz
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 another story:

 Issues Created Or Reopened (84)
[...]
 Issues Now Closed (103)

Woot! We did it! More issues closed than opened, that's sweet :)

To celebrate, I'll have a two-day tracker sprint (probably Sunday and
Monday, a holiday here) to add a couple of search options and a view
for mass-updating issues.

During the sprint, you'll be able to get your feature requests for
and/or bug reports about the tracker at a considerably lower price, so
send them in :)

Daniel

P.S.: It seems the 2341 open (+55) / 14813 closed (+27) / 17154 total
(+82) line is about Issues Created only :)
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2009-01-30 Thread Jean-Paul Calderone

On Fri, 30 Jan 2009 18:06:48 +0100 (CET), Python tracker 
sta...@bugs.python.org 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
day.  I just went back and checked and the week before it was one
day it was 2759 days.  Perhaps there is some sort of overflow problem
when computing this value?

Jean-Paul
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2008-11-24 Thread Jeremy Hylton
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 won't fix?

A meta-question:  Is there a document that has any tips on how to
handle bug reports?  It might be helpful to have a list of hints or
policy decisions to help people decide what to do with bugs.

Jeremy

On Fri, Nov 21, 2008 at 12:06 PM, Python tracker [EMAIL PROTECTED] wrote:

 ACTIVITY SUMMARY (11/14/08 - 11/21/08)
 Python tracker at http://bugs.python.org/

 To view or respond to any of the issues listed below, click on the issue
 number.  Do NOT respond to this message.


  2194 open (+35) / 14007 closed (+18) / 16201 total (+53)

 Open issues with patches:   728

 Average duration of open issues: 712 days.
 Median duration of open issues: 2043 days.

 Open Issues Breakdown
   open  2177 (+35)
 pending17 ( +0)

 Issues Created Or Reopened (56)
 ___

 Tkinter binding involving Control-spacebar raises unicode error  11/18/08
   http://bugs.python.org/issue1028reopened ocean-city
   patch

 Byte/string inconsistencies between different dbm modules11/21/08
   http://bugs.python.org/issue3799reopened brett.cannon
   patch, needs review

 type of UserList instance returns class instead of instance  11/14/08
 CLOSED http://bugs.python.org/issue4326created  chafporte


 Patch: simplify complex constant assignment statements   11/14/08
   http://bugs.python.org/issue4327created  novalis_dt
   patch

 à in ufoo raises a misleading error 11/15/08
   http://bugs.python.org/issue4328created  ezio.melotti


 base64 does not properly handle unicode strings  11/15/08
   http://bugs.python.org/issue4329created  mbecker


 wsgiref.validate doesn't accept arguments to readline11/16/08
 CLOSED http://bugs.python.org/issue4330created  ianb


 Can't use _functools.partial() created function as method11/16/08
   http://bugs.python.org/issue4331created  ssadler


 asyncore.file_dispatcher does not use dup()'ed fd11/17/08
 CLOSED http://bugs.python.org/issue4332created  christianbecke
   patch

 Reworked Dialog.py   11/17/08
   http://bugs.python.org/issue4333created  gpolo
   patch

 Mac Build Script is broken for 2.6 release   11/17/08
 CLOSED http://bugs.python.org/issue4334created  ngift


 inspect.getsourcelines ignores last line in module   11/17/08
   http://bugs.python.org/issue4335created  RafeSacks


 Fix performance issues in xmlrpclib  11/17/08
   http://bugs.python.org/issue4336created  krisvale
   patch, patch, easy

 Iteration over a map object with list()  11/17/08
 CLOSED http://bugs.python.org/issue4337created  jmfauth


 TypeError (bytes/str) in distutils command upload  11/17/08
 CLOSED http://bugs.python.org/issue4338created  hagen
   patch

 Fix set-like dictview doc11/17/08
 CLOSED http://bugs.python.org/issue4339created  tjreedy


 xmlrpc.client - default 'SlowParser' not defined 11/17/08
   http://bugs.python.org/issue4340created  mwatkins


 Update __hash__ doc  11/17/08
 CLOSED http://bugs.python.org/issue4341created  tjreedy


 (Tkinter) Please backport these  11/18/08
   http://bugs.python.org/issue4342created  gpolo


 New function in Tkinter.py: setup_master 11/18/08
   http://bugs.python.org/issue4343created  gpolo
   patch

 crash upon launch11/18/08
 CLOSED http://bugs.python.org/issue4344created  source.mod


 Implement nb_nonzero for PyTclObject 11/18/08
   http://bugs.python.org/issue4345created  gpolo
   patch

 PyObject_CallMethod changes the exception message already set by 11/18/08
   http://bugs.python.org/issue4346created  gpolo
   patch

 Dependencies of graminit.h are not rebuilt when the file is rege 11/18/08
   http://bugs.python.org/issue4347created  thomas.lee
   patch

 bytearray methods returning self 11/18/08
 CLOSED http://bugs.python.org/issue4348created  DinoV
   patch, needs review

 sys.path includes extraneous junk11/18/08
 CLOSED http://bugs.python.org/issue4349created  exarkun
   patch, needs review

 Remove dead code from Tkinter.py 11/19/08
   

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

2008-11-24 Thread Brett Cannon
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.  Since Python 2.4 is in
 security-fix only mode, is it fair to close this with a won't fix?


I think so.

 A meta-question:  Is there a document that has any tips on how to
 handle bug reports?  It might be helpful to have a list of hints or
 policy decisions to help people decide what to do with bugs.

It's coming. I just have not gotten around to it yet. I plan to
outline the basic steps in the life of an issue and that includes
closing an issue and the various reasons this can happen.

-Brett



 Jeremy

 On Fri, Nov 21, 2008 at 12:06 PM, Python tracker [EMAIL PROTECTED] wrote:

 ACTIVITY SUMMARY (11/14/08 - 11/21/08)
 Python tracker at http://bugs.python.org/

 To view or respond to any of the issues listed below, click on the issue
 number.  Do NOT respond to this message.


  2194 open (+35) / 14007 closed (+18) / 16201 total (+53)

 Open issues with patches:   728

 Average duration of open issues: 712 days.
 Median duration of open issues: 2043 days.

 Open Issues Breakdown
   open  2177 (+35)
 pending17 ( +0)

 Issues Created Or Reopened (56)
 ___

 Tkinter binding involving Control-spacebar raises unicode error  11/18/08
   http://bugs.python.org/issue1028reopened ocean-city
   patch

 Byte/string inconsistencies between different dbm modules11/21/08
   http://bugs.python.org/issue3799reopened brett.cannon
   patch, needs review

 type of UserList instance returns class instead of instance  11/14/08
 CLOSED http://bugs.python.org/issue4326created  chafporte


 Patch: simplify complex constant assignment statements   11/14/08
   http://bugs.python.org/issue4327created  novalis_dt
   patch

 à in ufoo raises a misleading error 11/15/08
   http://bugs.python.org/issue4328created  ezio.melotti


 base64 does not properly handle unicode strings  11/15/08
   http://bugs.python.org/issue4329created  mbecker


 wsgiref.validate doesn't accept arguments to readline11/16/08
 CLOSED http://bugs.python.org/issue4330created  ianb


 Can't use _functools.partial() created function as method11/16/08
   http://bugs.python.org/issue4331created  ssadler


 asyncore.file_dispatcher does not use dup()'ed fd11/17/08
 CLOSED http://bugs.python.org/issue4332created  christianbecke
   patch

 Reworked Dialog.py   11/17/08
   http://bugs.python.org/issue4333created  gpolo
   patch

 Mac Build Script is broken for 2.6 release   11/17/08
 CLOSED http://bugs.python.org/issue4334created  ngift


 inspect.getsourcelines ignores last line in module   11/17/08
   http://bugs.python.org/issue4335created  RafeSacks


 Fix performance issues in xmlrpclib  11/17/08
   http://bugs.python.org/issue4336created  krisvale
   patch, patch, easy

 Iteration over a map object with list()  11/17/08
 CLOSED http://bugs.python.org/issue4337created  jmfauth


 TypeError (bytes/str) in distutils command upload  11/17/08
 CLOSED http://bugs.python.org/issue4338created  hagen
   patch

 Fix set-like dictview doc11/17/08
 CLOSED http://bugs.python.org/issue4339created  tjreedy


 xmlrpc.client - default 'SlowParser' not defined 11/17/08
   http://bugs.python.org/issue4340created  mwatkins


 Update __hash__ doc  11/17/08
 CLOSED http://bugs.python.org/issue4341created  tjreedy


 (Tkinter) Please backport these  11/18/08
   http://bugs.python.org/issue4342created  gpolo


 New function in Tkinter.py: setup_master 11/18/08
   http://bugs.python.org/issue4343created  gpolo
   patch

 crash upon launch11/18/08
 CLOSED http://bugs.python.org/issue4344created  source.mod


 Implement nb_nonzero for PyTclObject 11/18/08
   http://bugs.python.org/issue4345created  gpolo
   patch

 PyObject_CallMethod changes the exception message already set by 11/18/08
   http://bugs.python.org/issue4346created  gpolo
   patch

 Dependencies of graminit.h are not rebuilt when the file is rege 11/18/08
   http://bugs.python.org/issue4347created  thomas.lee
   patch

 bytearray methods returning self 11/18/08
 CLOSED http://bugs.python.org/issue4348created  

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

2008-11-24 Thread Jeremy Hylton
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/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 won't fix?


 I think so.

 A meta-question:  Is there a document that has any tips on how to
 handle bug reports?  It might be helpful to have a list of hints or
 policy decisions to help people decide what to do with bugs.

 It's coming. I just have not gotten around to it yet. I plan to
 outline the basic steps in the life of an issue and that includes
 closing an issue and the various reasons this can happen.

If you put up skeleton doc, I can add a note to this effect.

Jeremy


 -Brett



 Jeremy

 On Fri, Nov 21, 2008 at 12:06 PM, Python tracker [EMAIL PROTECTED] wrote:

 ACTIVITY SUMMARY (11/14/08 - 11/21/08)
 Python tracker at http://bugs.python.org/

 To view or respond to any of the issues listed below, click on the issue
 number.  Do NOT respond to this message.


  2194 open (+35) / 14007 closed (+18) / 16201 total (+53)

 Open issues with patches:   728

 Average duration of open issues: 712 days.
 Median duration of open issues: 2043 days.

 Open Issues Breakdown
   open  2177 (+35)
 pending17 ( +0)

 Issues Created Or Reopened (56)
 ___

 Tkinter binding involving Control-spacebar raises unicode error  11/18/08
   http://bugs.python.org/issue1028reopened ocean-city
   patch

 Byte/string inconsistencies between different dbm modules11/21/08
   http://bugs.python.org/issue3799reopened brett.cannon
   patch, needs review

 type of UserList instance returns class instead of instance  11/14/08
 CLOSED http://bugs.python.org/issue4326created  chafporte


 Patch: simplify complex constant assignment statements   11/14/08
   http://bugs.python.org/issue4327created  novalis_dt
   patch

 à in ufoo raises a misleading error 11/15/08
   http://bugs.python.org/issue4328created  ezio.melotti


 base64 does not properly handle unicode strings  11/15/08
   http://bugs.python.org/issue4329created  mbecker


 wsgiref.validate doesn't accept arguments to readline11/16/08
 CLOSED http://bugs.python.org/issue4330created  ianb


 Can't use _functools.partial() created function as method11/16/08
   http://bugs.python.org/issue4331created  ssadler


 asyncore.file_dispatcher does not use dup()'ed fd11/17/08
 CLOSED http://bugs.python.org/issue4332created  christianbecke
   patch

 Reworked Dialog.py   11/17/08
   http://bugs.python.org/issue4333created  gpolo
   patch

 Mac Build Script is broken for 2.6 release   11/17/08
 CLOSED http://bugs.python.org/issue4334created  ngift


 inspect.getsourcelines ignores last line in module   11/17/08
   http://bugs.python.org/issue4335created  RafeSacks


 Fix performance issues in xmlrpclib  11/17/08
   http://bugs.python.org/issue4336created  krisvale
   patch, patch, easy

 Iteration over a map object with list()  11/17/08
 CLOSED http://bugs.python.org/issue4337created  jmfauth


 TypeError (bytes/str) in distutils command upload  11/17/08
 CLOSED http://bugs.python.org/issue4338created  hagen
   patch

 Fix set-like dictview doc11/17/08
 CLOSED http://bugs.python.org/issue4339created  tjreedy


 xmlrpc.client - default 'SlowParser' not defined 11/17/08
   http://bugs.python.org/issue4340created  mwatkins


 Update __hash__ doc  11/17/08
 CLOSED http://bugs.python.org/issue4341created  tjreedy


 (Tkinter) Please backport these  11/18/08
   http://bugs.python.org/issue4342created  gpolo


 New function in Tkinter.py: setup_master 11/18/08
   http://bugs.python.org/issue4343created  gpolo
   patch

 crash upon launch11/18/08
 CLOSED http://bugs.python.org/issue4344created  source.mod


 Implement nb_nonzero for PyTclObject 11/18/08
   http://bugs.python.org/issue4345created  gpolo
   patch

 PyObject_CallMethod changes the exception message already set by 11/18/08
   http://bugs.python.org/issue4346created  gpolo
   patch

 Dependencies of graminit.h are not rebuilt when the file is rege 11/18/08
   http://bugs.python.org/issue4347created  

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

2008-11-24 Thread Brett Cannon
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
 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 won't fix?


 I think so.

 A meta-question:  Is there a document that has any tips on how to
 handle bug reports?  It might be helpful to have a list of hints or
 policy decisions to help people decide what to do with bugs.

 It's coming. I just have not gotten around to it yet. I plan to
 outline the basic steps in the life of an issue and that includes
 closing an issue and the various reasons this can happen.

 If you put up skeleton doc, I can add a note to this effect.


The doc I have for it is made up like five bullet points, so nothing
to really put up yet. But I did add another bullet point for this.

-Brett


 Jeremy


 -Brett



 Jeremy

 On Fri, Nov 21, 2008 at 12:06 PM, Python tracker [EMAIL PROTECTED] wrote:

 ACTIVITY SUMMARY (11/14/08 - 11/21/08)
 Python tracker at http://bugs.python.org/

 To view or respond to any of the issues listed below, click on the issue
 number.  Do NOT respond to this message.


  2194 open (+35) / 14007 closed (+18) / 16201 total (+53)

 Open issues with patches:   728

 Average duration of open issues: 712 days.
 Median duration of open issues: 2043 days.

 Open Issues Breakdown
   open  2177 (+35)
 pending17 ( +0)

 Issues Created Or Reopened (56)
 ___

 Tkinter binding involving Control-spacebar raises unicode error  11/18/08
   http://bugs.python.org/issue1028reopened ocean-city
   patch

 Byte/string inconsistencies between different dbm modules11/21/08
   http://bugs.python.org/issue3799reopened brett.cannon
   patch, needs review

 type of UserList instance returns class instead of instance  11/14/08
 CLOSED http://bugs.python.org/issue4326created  chafporte


 Patch: simplify complex constant assignment statements   11/14/08
   http://bugs.python.org/issue4327created  novalis_dt
   patch

 à in ufoo raises a misleading error 11/15/08
   http://bugs.python.org/issue4328created  ezio.melotti


 base64 does not properly handle unicode strings  11/15/08
   http://bugs.python.org/issue4329created  mbecker


 wsgiref.validate doesn't accept arguments to readline11/16/08
 CLOSED http://bugs.python.org/issue4330created  ianb


 Can't use _functools.partial() created function as method11/16/08
   http://bugs.python.org/issue4331created  ssadler


 asyncore.file_dispatcher does not use dup()'ed fd11/17/08
 CLOSED http://bugs.python.org/issue4332created  christianbecke
   patch

 Reworked Dialog.py   11/17/08
   http://bugs.python.org/issue4333created  gpolo
   patch

 Mac Build Script is broken for 2.6 release   11/17/08
 CLOSED http://bugs.python.org/issue4334created  ngift


 inspect.getsourcelines ignores last line in module   11/17/08
   http://bugs.python.org/issue4335created  RafeSacks


 Fix performance issues in xmlrpclib  11/17/08
   http://bugs.python.org/issue4336created  krisvale
   patch, patch, easy

 Iteration over a map object with list()  11/17/08
 CLOSED http://bugs.python.org/issue4337created  jmfauth


 TypeError (bytes/str) in distutils command upload  11/17/08
 CLOSED http://bugs.python.org/issue4338created  hagen
   patch

 Fix set-like dictview doc11/17/08
 CLOSED http://bugs.python.org/issue4339created  tjreedy


 xmlrpc.client - default 'SlowParser' not defined 11/17/08
   http://bugs.python.org/issue4340created  mwatkins


 Update __hash__ doc  11/17/08
 CLOSED http://bugs.python.org/issue4341created  tjreedy


 (Tkinter) Please backport these  11/18/08
   http://bugs.python.org/issue4342created  gpolo


 New function in Tkinter.py: setup_master 11/18/08
   http://bugs.python.org/issue4343created  gpolo
   patch

 crash upon launch11/18/08
 CLOSED http://bugs.python.org/issue4344created  source.mod


 Implement nb_nonzero for PyTclObject 11/18/08
   http://bugs.python.org/issue4345created  gpolo
   patch

 PyObject_CallMethod changes the exception message already 

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

2008-11-24 Thread Martin v. Löwis
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, is it fair to close this with a won't fix?

Correct.

Regards,
Martin

___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2008-11-24 Thread Terry Reedy

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-fix only mode, is it fair to close this with a won't fix?


Correct.


If a bug exists and is fixed in a later release -- I would call it 'out 
of date' instead.


___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


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

2008-11-24 Thread Martin v. Löwis
 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 was specifically
that the bug is in 2.4.x, with a request to fix it in 2.4.x+1, then
it's won't fix.

Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com