Mailing List Archive

ACTIVITY SUMMARY (02/05/10 - 02/12/10)
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.


2602 open (+33) / 17137 closed (+25) / 19739 total (+58)

Open issues with patches: 1069

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

Open Issues Breakdown
open 2567 (+33)
pending 34 ( +0)

Issues Created Or Reopened (59)
_______________________________

support "with self.assertRaises(SomeException) as exc:" syntax 02/07/10
CLOSED http://bugs.python.org/issue7859 reopened flox


32-bit Python on 64-bit Windows reports incorrect architecture 02/05/10
http://bugs.python.org/issue7860 created brian.curtin
patch, patch, needs review

2to3: "import foo" -> "from . import foo" 02/05/10
CLOSED http://bugs.python.org/issue7861 created tomspur


fileio.c: ValueError vs. IOError with impossible operations 02/05/10
http://bugs.python.org/issue7862 created skrah


platform module doesn't detect Windows 7 02/05/10
http://bugs.python.org/issue7863 created adal
patch, needs review

Deprecation markers in unittest docs are unclear 02/06/10
CLOSED http://bugs.python.org/issue7864 created Justin.Lebar


io close() swallowing exceptions 02/06/10
http://bugs.python.org/issue7865 created pakal


it looks like a typo in unittest 02/06/10
CLOSED http://bugs.python.org/issue7866 created artech


Proposed FAQ entry on pass-by-? semantics and the meaning of 'va 02/06/10
http://bugs.python.org/issue7867 created r.david.murray


add a loggerClass attribute to Manager 02/06/10
CLOSED http://bugs.python.org/issue7868 created georg.brandl
patch, patch, easy

traceback from logging is unusable. 02/07/10
CLOSED http://bugs.python.org/issue7869 created naoki
patch

Duplicate test methods in test_memoryio 02/07/10
CLOSED http://bugs.python.org/issue7870 created georg.brandl


Duplicate test method in test_heapq 02/07/10
http://bugs.python.org/issue7871 created georg.brandl


Incorrect error raised on importing invalid module via unittest 02/07/10
CLOSED http://bugs.python.org/issue7872 created Daniel.Waterworth


Remove precision restriction for integer formatting. 02/07/10
http://bugs.python.org/issue7873 created mark.dickinson
easy

logging.basicConfig should raise warning/exception on second cal 02/07/10
CLOSED http://bugs.python.org/issue7874 created tocomo


test_multiprocessing / importlib failure 02/07/10
http://bugs.python.org/issue7875 created pitrou
buildbot

unittest docs use deprecated method in code example 02/07/10
CLOSED http://bugs.python.org/issue7876 created Bernt.Røskar.Brenna


Iterators over _winreg EnumKey and EnumValue results 02/07/10
http://bugs.python.org/issue7877 created brian.curtin
patch, patch, needs review

regrtest should check for changes in import machinery 02/07/10
http://bugs.python.org/issue7878 created brett.cannon
easy

Too narrow platform check in test_datetime 02/07/10
http://bugs.python.org/issue7879 created akrpic77
patch

sysconfig does not like symlinks 02/07/10
http://bugs.python.org/issue7880 created flox
patch

Hardcoded path, unsafe tempfile in test_logging 02/08/10
CLOSED http://bugs.python.org/issue7881 created nascheme


Compiling on MOX 10.6 "Snow Leopard" --#warning Building for Int 02/08/10
CLOSED http://bugs.python.org/issue7882 created global667


CallTips.py _find_constructor does not work 02/08/10
http://bugs.python.org/issue7883 created Bernt.Røskar.Brenna


IDLE 3.1.1 crashes with UnicodeDecodeError when I press Ctrl-Spa 02/08/10
CLOSED http://bugs.python.org/issue7884 created Bernt.Røskar.Brenna


test_distutils fails if Python built in separate directory 02/08/10
http://bugs.python.org/issue7885 created nascheme


reverse on an empty list returns None 02/08/10
CLOSED http://bugs.python.org/issue7886 created tormen


errno 107 socket.recv issure 02/08/10
CLOSED http://bugs.python.org/issue7887 created twistedphrame


turtle "settiltangle" should be marked deprecated, not "tiltangl 02/09/10
http://bugs.python.org/issue7888 created mnewman


random produces different output on different architectures 02/09/10
http://bugs.python.org/issue7889 created terrence


equal unicode/str objects can have unequal hash 02/09/10
CLOSED http://bugs.python.org/issue7890 created ldeller


add links to SVN for documentation developers 02/09/10
http://bugs.python.org/issue7891 created techtonik


refactor "test_dict.py" using new assertRaises context manager. 02/09/10
http://bugs.python.org/issue7892 created flox
patch

unittest: have to subclass TextTestRunner to use alternative Tes 02/09/10
CLOSED http://bugs.python.org/issue7893 created michael.foord
easy

too aggressive dependency tracking in distutils 02/09/10
http://bugs.python.org/issue7894 created ronaldoussoren


Mac 10.6 mac_ver() crashes with USING_FORK_WITHOUT_EXEC_IS _NOT_ 02/09/10
http://bugs.python.org/issue7895 created aahz


IDLE.app crashes when attempting to open a .py file 02/09/10
http://bugs.python.org/issue7896 created phyreman


Support parametrized tests in unittest 02/10/10
http://bugs.python.org/issue7897 created fperez


rlcompleter add "real tab" when text is empty feature 02/10/10
http://bugs.python.org/issue7898 created lilaboc
patch

MemoryError While Executing Python Code 02/10/10
http://bugs.python.org/issue7899 created p_noblebose


posix.getgroups() failure on Mac OS X 02/10/10
http://bugs.python.org/issue7900 created michael.foord


Add Vista/7 symlink support 02/10/10
CLOSED http://bugs.python.org/issue7901 created ipatrol


relative import broken 02/10/10
http://bugs.python.org/issue7902 created gangesmaster


Configure script incorrect for reasonably recent OpenBSD 02/10/10
http://bugs.python.org/issue7903 created johns


urlparse.urlsplit mishandles novel schemes 02/10/10
http://bugs.python.org/issue7904 created mbloore


Shelf 'keyencoding' keyword argument is undocumented and does no 02/11/10
http://bugs.python.org/issue7905 created r.david.murray
patch, patch, needs review

float("INFI") returns inf on certain platforms 02/11/10
CLOSED http://bugs.python.org/issue7906 created csernazs


winreg docs: CreateKeyEx should be CreateKey (minor) 02/11/10
CLOSED http://bugs.python.org/issue7907 created patraulea
patch, needs review

remove leftover macos9 support code 02/11/10
http://bugs.python.org/issue7908 created ronaldoussoren
patch, needs review

os.path.abspath(os.devnull) returns \\\\nul should be nul? 02/11/10
http://bugs.python.org/issue7909 created abakker


immutability w/r to tuple.__add__ 02/11/10
CLOSED http://bugs.python.org/issue7910 created mattrussell


unittest.TestCase.longMessage should default to True in Python 3 02/11/10
http://bugs.python.org/issue7911 created michael.foord
easy

Error in additon of decimal numbers 02/11/10
CLOSED http://bugs.python.org/issue7912 created James.Sparenberg


Enhance Cmd support for docstrings and document it. 02/11/10
http://bugs.python.org/issue7913 created r.david.murray
patch

IntVar() - AttributeError: 'NoneType' object has no attribute 't 02/11/10
CLOSED http://bugs.python.org/issue7914 created Plazma


A lists which list.sort seems to leave out of order. 02/12/10
CLOSED http://bugs.python.org/issue7915 created throwaway


zipfile.ZipExtFile passes long to fileobj.read() 02/12/10
CLOSED http://bugs.python.org/issue7916 created anacrolix


list of list created by * 02/12/10
CLOSED http://bugs.python.org/issue7917 created sledge76




Issues Now Closed (60)
______________________

Intermitent failure in test_multiprocessing.test_number_of_objec 543 days
http://bugs.python.org/issue3562 flox


allow unicode keyword args 2 days
http://bugs.python.org/issue4978 benjamin.peterson
patch, needs review

A selection of spelling errors and typos throughout source 3 days
http://bugs.python.org/issue5341 merwok
patch

[PATCH]Add FastDbfilenameShelf: shelf nerver sync cache even whe 335 days
http://bugs.python.org/issue5483 r.david.murray
patch

memory leaks in py3k 317 days
http://bugs.python.org/issue5596 flox
patch

Serious interpreter crash and/or arbitrary memory leak using .re 309 days
http://bugs.python.org/issue5677 pitrou
patch

Shelve module writeback parameter does not act as advertised 302 days
http://bugs.python.org/issue5754 r.david.murray
patch, easy

ZipFile.writestr "compression_type" argument 271 days
http://bugs.python.org/issue6003 ronaldoussoren
patch

ElementTree (py3k) doesn't properly encode characters that can't 247 days
http://bugs.python.org/issue6233 pitrou
patch

rare assertion failure in test_multiprocessing 224 days
http://bugs.python.org/issue6366 flox


OS X: python3 from python-3.1.dmg crashes at startup 224 days
http://bugs.python.org/issue6393 srid
patch, needs review

multiprocessing logging support test 77 days
http://bugs.python.org/issue6615 vinay.sajip
patch

test test_multiprocessing failed 172 days
http://bugs.python.org/issue6747 flox


enable compilation of readline module on Mac OS X 10.5 and 10.6 7 days
http://bugs.python.org/issue6877 minge
patch, 26backport, needs review

Update version{added,changed} entries in py3k unittest docs 127 days
http://bugs.python.org/issue7030 ezio.melotti


Make assertMultilineEqual default for unicode string comparison 130 days
http://bugs.python.org/issue7032 michael.foord


low performance of zipfile readline() 105 days
http://bugs.python.org/issue7216 amaury.forgeotdarc


OverflowError: signed integer is greater than maximum on mips64 91 days
http://bugs.python.org/issue7296 mark.dickinson


OS X 2.6.4 installer fails on 10.3 with two corrupted file names 64 days
http://bugs.python.org/issue7437 ronaldoussoren


python -m unittest path_to_suite_function errors 59 days
http://bugs.python.org/issue7501 michael.foord


unittest.TestCase.shortDescription isn't short anymore 44 days
http://bugs.python.org/issue7588 michael.foord


OS X pythonw.c compile error with 10.4 or earlier deployment tar 30 days
http://bugs.python.org/issue7658 ronaldoussoren
patch

configure GCC version detection fix for Darwin 22 days
http://bugs.python.org/issue7714 ronaldoussoren
patch, needs review

Allow use of GNU arch on Darwin 26 days
http://bugs.python.org/issue7715 ronaldoussoren
patch, needs review

test_timeout should use "find_unused_port" helper 19 days
http://bugs.python.org/issue7728 r.david.murray
patch, easy, buildbot

unittest returning standard_tests from load_tests in module fail 8 days
http://bugs.python.org/issue7799 michael.foord
easy

test_macostools fails on OS X 10.6: no attribute 'FSSpec' 9 days
http://bugs.python.org/issue7807 ronaldoussoren


Call to gestalt('sysu') on OSX can lead to freeze in wxPython ap 8 days
http://bugs.python.org/issue7812 ronaldoussoren


Minor bug in 2.6.4 related to cleanup at end of program 9 days
http://bugs.python.org/issue7835 r.david.murray
patch, easy

python-dev archives are not updated 5 days
http://bugs.python.org/issue7843 isandler


Remove 'python -U' or document it 2 days
http://bugs.python.org/issue7847 barry
patch, needs review

copy.copy corrupts objects that return false value from __getsta 4 days
http://bugs.python.org/issue7848 georg.brandl


on __exit__(), exc_value does not contain the exception. 2 days
http://bugs.python.org/issue7853 benjamin.peterson
patch

test_logging fails 3 days
http://bugs.python.org/issue7857 vinay.sajip
buildbot

support "with self.assertRaises(SomeException) as exc:" syntax 0 days
http://bugs.python.org/issue7859 flox


2to3: "import foo" -> "from . import foo" 3 days
http://bugs.python.org/issue7861 tomspur


Deprecation markers in unittest docs are unclear 0 days
http://bugs.python.org/issue7864 georg.brandl


it looks like a typo in unittest 0 days
http://bugs.python.org/issue7866 merwok


add a loggerClass attribute to Manager 0 days
http://bugs.python.org/issue7868 georg.brandl
patch, patch, easy

traceback from logging is unusable. 0 days
http://bugs.python.org/issue7869 vinay.sajip
patch

Duplicate test methods in test_memoryio 0 days
http://bugs.python.org/issue7870 pitrou


Incorrect error raised on importing invalid module via unittest 0 days
http://bugs.python.org/issue7872 michael.foord


logging.basicConfig should raise warning/exception on second cal 0 days
http://bugs.python.org/issue7874 vinay.sajip


unittest docs use deprecated method in code example 1 days
http://bugs.python.org/issue7876 ezio.melotti


Hardcoded path, unsafe tempfile in test_logging 0 days
http://bugs.python.org/issue7881 vinay.sajip


Compiling on MOX 10.6 "Snow Leopard" --#warning Building for Int 1 days
http://bugs.python.org/issue7882 ronaldoussoren


IDLE 3.1.1 crashes with UnicodeDecodeError when I press Ctrl-Spa 0 days
http://bugs.python.org/issue7884 ezio.melotti


reverse on an empty list returns None 0 days
http://bugs.python.org/issue7886 tormen


errno 107 socket.recv issure 1 days
http://bugs.python.org/issue7887 twistedphrame


equal unicode/str objects can have unequal hash 0 days
http://bugs.python.org/issue7890 lemburg


unittest: have to subclass TextTestRunner to use alternative Tes 1 days
http://bugs.python.org/issue7893 michael.foord
easy

Add Vista/7 symlink support 0 days
http://bugs.python.org/issue7901 tim.golden


float("INFI") returns inf on certain platforms 1 days
http://bugs.python.org/issue7906 r.david.murray


winreg docs: CreateKeyEx should be CreateKey (minor) 0 days
http://bugs.python.org/issue7907 ezio.melotti
patch, needs review

immutability w/r to tuple.__add__ 0 days
http://bugs.python.org/issue7910 rhettinger


Error in additon of decimal numbers 0 days
http://bugs.python.org/issue7912 r.david.murray


IntVar() - AttributeError: 'NoneType' object has no attribute 't 0 days
http://bugs.python.org/issue7914 brian.curtin


A lists which list.sort seems to leave out of order. 0 days
http://bugs.python.org/issue7915 throwaway


zipfile.ZipExtFile passes long to fileobj.read() 0 days
http://bugs.python.org/issue7916 amaury.forgeotdarc


list of list created by * 0 days
http://bugs.python.org/issue7917 flox




Top Issues Most Discussed (10)
______________________________

17 Add a context manager to change cwd in test.test_support and ru 27 days
open http://bugs.python.org/issue7712

17 enable compilation of readline module on Mac OS X 10.5 and 10.6 7 days
closed http://bugs.python.org/issue6877

10 random produces different output on different architectures 4 days
open http://bugs.python.org/issue7889

9 Support parametrized tests in unittest 3 days
open http://bugs.python.org/issue7897

9 support "with self.assertRaises(SomeException) as exc:" syntax 0 days
closed http://bugs.python.org/issue7859

8 test_multiprocessing / importlib failure 5 days
open http://bugs.python.org/issue7875

8 Add os.link() and os.symlink() and os.path.islink() support for 1215 days
open http://bugs.python.org/issue1578269

7 float("INFI") returns inf on certain platforms 1 days
closed http://bugs.python.org/issue7906

7 Proposed FAQ entry on pass-by-? semantics and the meaning of 'v 6 days
open http://bugs.python.org/issue7867

7 platform module doesn't detect Windows 7 7 days
open http://bugs.python.org/issue7863

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/list-python-dev%40lists.gossamer-threads.com

On 3 September 2010 17:41, Paul Moore <p.f.moore@gmail.com> wrote:
> On 3 September 2010 17:30, Victor Stinner <victor.stinner@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/list-python-dev%40lists.gossamer-threads.com

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 <status@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/list-python-dev%40lists.gossamer-threads.com

On Fri, Sep 24, 2010 at 12:57, Georg Brandl <g.brandl@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 <status@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/list-python-dev%40lists.gossamer-threads.com

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.brandl@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 <status@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/list-python-dev%40lists.gossamer-threads.com

On Fri, Sep 24, 2010 at 13:04, Georg Brandl <g.brandl@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.brandl@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 <status@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/list-python-dev%40lists.gossamer-threads.com

Am 25.09.2010 03:45, schrieb Brett Cannon:
> On Fri, Sep 24, 2010 at 13:04, Georg Brandl <g.brandl@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/list-python-dev%40lists.gossamer-threads.com

>> 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/list-python-dev%40lists.gossamer-threads.com

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/list-python-dev%40lists.gossamer-threads.com

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/list-python-dev%40lists.gossamer-threads.com

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/list-python-dev%40lists.gossamer-threads.com

On Sat, 25 Sep 2010 19:02:06 +0200
Georg Brandl <g.brandl@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.

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/list-python-dev%40lists.gossamer-threads.com

On Sat, 25 Sep 2010 14:22:06 +0200, Georg Brandl <g.brandl@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/list-python-dev%40lists.gossamer-threads.com

> 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/list-python-dev%40lists.gossamer-threads.com

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/list-python-dev%40lists.gossamer-threads.com

On 9/25/2010 1:08 PM, Antoine Pitrou wrote:
> On Sat, 25 Sep 2010 19:02:06 +0200
> Georg Brandl<g.brandl@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/list-python-dev%40lists.gossamer-threads.com

On Fri, Jan 7, 2011 at 1:17 PM, anatoly techtonik <techtonik@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/list-python-dev%40lists.gossamer-threads.com

>
> Most recent 15 issues waiting for review (15)
> =============================================
>
Just curious: How is a issue considered "waiting for review"?

Thanks!
francis


_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/list-python-dev%40lists.gossamer-threads.com

Zitat von francis <francismb@email.de>:

>>
>> Most recent 15 issues waiting for review (15)
>> =============================================
>>
> Just curious: How is a issue considered "waiting for review"?

Issues that have the "patch" or "needs review" keyword or are
in the "patch review" stage.

Regards,
Martin


_______________________________________________
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/list-python-dev%40lists.gossamer-threads.com

>>>
>>> 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/list-python-dev%40lists.gossamer-threads.com

Zitat von francis <francismb@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/file<id>/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/list-python-dev%40lists.gossamer-threads.com

Hi,

On Sat, Aug 25, 2012 at 2:07 PM, <martin@v.loewis.de> wrote:
>
> Zitat von francis <francismb@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/list-python-dev%40lists.gossamer-threads.com

On Fri, Nov 2, 2012 at 10:05 PM, Eric Snow <ericsnowcurrently@gmail.com>
wrote:
>
> On Fri, Nov 2, 2012 at 11:07 AM, Python tracker <status@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:
> > open 3804 (-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

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/list-python-dev%40lists.gossamer-threads.com