Summary of Python tracker Issues
ACTIVITY SUMMARY (2012-11-23 - 2012-11-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: open 3792 ( -7) closed 24566 (+48) total 28358 (+41) Open issues with patches: 1653 Issues opened (27) ================== #8824: Improve documentation of exec http://bugs.python.org/issue8824 reopened by mark.dickinson #9400: multiprocessing.pool.AsyncResult.get() messes up exceptions http://bugs.python.org/issue9400 reopened by sbt #15587: IDLE is pixelated on the Macbook Pro with Retina Display http://bugs.python.org/issue15587 reopened by Tyler.Crompton #16541: tk_setPalette doesn't accept keyword parameters http://bugs.python.org/issue16541 opened by HJarausch #16543: improve TypeError messages for missing arguments (meta issue) http://bugs.python.org/issue16543 opened by ezio.melotti #16544: Add external link to ast docs http://bugs.python.org/issue16544 opened by asvetlov #16547: IDLE raises an exception in tkinter after fresh file's text ha http://bugs.python.org/issue16547 opened by ebfe #16550: pickletools.py treats 32bit lengths as signed, but pickle.py a http://bugs.python.org/issue16550 opened by serhiy.storchaka #16551: Cleanup the pure Python pickle implementation http://bugs.python.org/issue16551 opened by serhiy.storchaka #16554: The description of the argument of MAKE_FUNCTION and MAKE_CLOS http://bugs.python.org/issue16554 opened by daniel.urban #16555: Add es_cu to locale aliases http://bugs.python.org/issue16555 opened by Leiser.Fernández.Gallo #16557: PEP 380 isn't reflected in the Functional Programming HOWTO http://bugs.python.org/issue16557 opened by msmhrt #16561: Windows installer doesn't use UAC, then crashes http://bugs.python.org/issue16561 opened by Redoute #16562: Optimize dict equality test http://bugs.python.org/issue16562 opened by rhettinger #16564: email.generator.BytesGenerator fails with bytes payload http://bugs.python.org/issue16564 opened by Alexander.Kruppa #16565: Increase Py_AddPendingCall array size http://bugs.python.org/issue16565 opened by felipecruz #16566: Structure._anonymous_ should not allow strings http://bugs.python.org/issue16566 opened by techtonik #16568: allow constructors to be documented separately from class http://bugs.python.org/issue16568 opened by chris.jerdonek #16569: Preventing errors of simultaneous access in zipfile http://bugs.python.org/issue16569 opened by serhiy.storchaka #16572: Bad multi-inheritance support in some libs like threading or m http://bugs.python.org/issue16572 opened by thomas.chiroux #16574: clarify policy on updates to final peps http://bugs.python.org/issue16574 opened by chris.jerdonek #16575: ctypes: unions as arguments http://bugs.python.org/issue16575 opened by arigo #16576: ctypes: structure with bitfields as argument http://bugs.python.org/issue16576 opened by arigo #16577: Suspect test.test_codeccallbacks.test_mutatingdecodehandler http://bugs.python.org/issue16577 opened by amaury.forgeotdarc #16579: .pyw disturb multiprocessing behavior http://bugs.python.org/issue16579 opened by Alex.stein #16580: Add examples to int.to_bytres and int.from_bytes http://bugs.python.org/issue16580 opened by paddy3118 #16581: define "PEP editor" in PEP 1 http://bugs.python.org/issue16581 opened by chris.jerdonek Most recent 15 issues with no replies (15) ========================================== #16581: define "PEP editor" in PEP 1 http://bugs.python.org/issue16581 #16580: Add examples to int.to_bytres and int.from_bytes http://bugs.python.org/issue16580 #16575: ctypes: unions as arguments http://bugs.python.org/issue16575 #16561: Windows installer doesn't use UAC, then crashes http://bugs.python.org/issue16561 #16557: PEP 380 isn't reflected in the Functional Programming HOWTO http://bugs.python.org/issue16557 #16551: Cleanup the pure Python pickle implementation http://bugs.python.org/issue16551 #16550: pickletools.py treats 32bit lengths as signed, but pickle.py a http://bugs.python.org/issue16550 #16516: argparse types (and actions) must be hashable http://bugs.python.org/issue16516 #16509: sqlite3 docs do not explain check_same_thread http://bugs.python.org/issue16509 #16494: Add a method on importlib.SourceLoader for creating bytecode f http://bugs.python.org/issue16494 #16492: Add a load_parents argument to importlib.find_loader() http://bugs.python.org/issue16492 #16486: Add context manager support to aifc module http://bugs.python.org/issue16486 #16463: test_timeout failure on the RHEL buildbot http://bugs.python.org/issue16463 #16450: test_missing_localfile masks problems in urlopen http://bugs.python.org/issue16450 #16429: Emit SyntaxWarning for code that risks UnboundLocalError http://bugs.python.org/issue16429 Most recent 15 issues waiting for review (15) ============================================= #16572: Bad multi-inheritance support in some libs like threading or m http://bugs.python.org/issue16572 #16569: Preventing errors of simultaneous access in zipfile http://bugs.python.org/issue16569 #16562: Optimize dict equality test http://bugs.python.org/issue16562 #16554: The description of the argument of MAKE_FUNCTION and MAKE_CLOS http://bugs.python.org/issue16554 #16551: Cleanup the pure Python pickle implementation http://bugs.python.org/issue16551 #16550: pickletools.py treats 32bit lengths as signed, but pickle.py a http://bugs.python.org/issue16550 #16543: improve TypeError messages for missing arguments (meta issue) http://bugs.python.org/issue16543 #16537: Python’s setup.py raises a ValueError when self.extensions i http://bugs.python.org/issue16537 #16525: wave file module does not support 32bit float format http://bugs.python.org/issue16525 #16523: attrgetter and itemgetter signatures in docs need cleanup http://bugs.python.org/issue16523 #16515: TypeError message incorrect for max() with one keyword arg http://bugs.python.org/issue16515 #16512: imghdr doesn't support jpegs with an ICC profile http://bugs.python.org/issue16512 #16511: IDLE configuration file: blank height and width fields trip up http://bugs.python.org/issue16511 #16510: Using appropriate checks in tests http://bugs.python.org/issue16510 #16507: Patch selectmodule.c to support WSAPoll on Windows http://bugs.python.org/issue16507 Top 10 most discussed issues (10) ================================= #16543: improve TypeError messages for missing arguments (meta issue) http://bugs.python.org/issue16543 21 msgs #16518: add "buffer protocol" to glossary http://bugs.python.org/issue16518 15 msgs #16574: clarify policy on updates to final peps http://bugs.python.org/issue16574 15 msgs #4591: 32-bits unsigned user/group identifier http://bugs.python.org/issue4591 11 msgs #4945: json checks True/False by identity, not boolean value http://bugs.python.org/issue4945 11 msgs #16547: IDLE raises an exception in tkinter after fresh file's text ha http://bugs.python.org/issue16547 9 msgs #7976: warnings should provide a public API for accessing its option http://bugs.python.org/issue7976 8 msgs #16565: Increase Py_AddPendingCall array size http://bugs.python.org/issue16565 8 msgs #16566: Structure._anonymous_ should not allow strings http://bugs.python.org/issue16566 8 msgs #11175: allow argparse FileType to accept encoding and errors argument http://bugs.python.org/issue11175 6 msgs Issues closed (45) ================== #1827: svnversion_init() doesn't support svn urls in sandbox/trunk http://bugs.python.org/issue1827 closed by christian.heimes #1977: Python reinitialization test http://bugs.python.org/issue1977 closed by christian.heimes #2039: Pymalloc patch for int and float objects http://bugs.python.org/issue2039 closed by christian.heimes #3410: platform.version() don't work as expected in Vista in portugue http://bugs.python.org/issue3410 closed by ezio.melotti #4473: POP3 missing support for starttls http://bugs.python.org/issue4473 closed by pitrou #9011: ast_for_factor unary minus optimization changes AST http://bugs.python.org/issue9011 closed by mark.dickinson #9176: module termios doesn't build on HP-UX http://bugs.python.org/issue9176 closed by skrah #10259: Entry text not set if all of 'Font', 'Foreground' and 'Justify http://bugs.python.org/issue10259 closed by gpolo #11076: Iterable argparse Namespace http://bugs.python.org/issue11076 closed by asvetlov #12848: pickle.py treats 32bit lengths as signed, but _pickle.c as uns http://bugs.python.org/issue12848 closed by pitrou #14478: Decimal hashing very slow, could be cached http://bugs.python.org/issue14478 closed by mark.dickinson #15990: solidify argument/parameter terminology http://bugs.python.org/issue15990 closed by chris.jerdonek #16205: update :class:`str` references to link to the str type section http://bugs.python.org/issue16205 closed by chris.jerdonek #16209: add a "class str" entry to the docs http://bugs.python.org/issue16209 closed by chris.jerdonek #16323: Wrong C API documentation for locale encoding http://bugs.python.org/issue16323 closed by asvetlov #16333: Trailing whitespace in json dump when using indent http://bugs.python.org/issue16333 closed by ezio.melotti #16339: Document "exec(stmt, global_dict, local_dict)" form in Python http://bugs.python.org/issue16339 closed by mark.dickinson #16423: urllib data URL http://bugs.python.org/issue16423 closed by pitrou #16464: urllib.request: opener not resetting content-length http://bugs.python.org/issue16464 closed by asvetlov #16477: tarfile fails to close file handles in case of exception http://bugs.python.org/issue16477 closed by asvetlov #16483: Make int(float('inf')) raise ValueError rather than OverflowEr http://bugs.python.org/issue16483 closed by mark.dickinson #16519: site.venv() should use abspath(executable) http://bugs.python.org/issue16519 closed by python-dev #16521: logging.basicConfig creates empty file when using handlers http://bugs.python.org/issue16521 closed by python-dev #16524: File access not always working with Python for Windows 32 bits http://bugs.python.org/issue16524 closed by terry.reedy #16530: documentation of os.wait3 http://bugs.python.org/issue16530 closed by ezio.melotti #16532: AMD64 Windows 7 build failures http://bugs.python.org/issue16532 closed by pitrou #16534: -Olimit: unsupported option: warnings and ./configure failures http://bugs.python.org/issue16534 closed by skrah #16540: Make itertools count, cycle, and repeat objects subscriptable http://bugs.python.org/issue16540 closed by rhettinger #16542: http//bugs.python/joko.suwito http://bugs.python.org/issue16542 closed by ezio.melotti #16545: ast.FunctionDef sets a bad value for kw_defaults when keyword- http://bugs.python.org/issue16545 closed by brett.cannon #16546: ast.YieldFrom needlessly has its expr value as optional http://bugs.python.org/issue16546 closed by mark.dickinson #16548: os.system won't run any command and there is no error message http://bugs.python.org/issue16548 closed by r.david.murray #16549: regression: -m json.tool module is broken http://bugs.python.org/issue16549 closed by ezio.melotti #16552: os.path.basename() docs should link to os.path.split() http://bugs.python.org/issue16552 closed by chris.jerdonek #16553: named kwd form of OrderedDict ctor yield random key order http://bugs.python.org/issue16553 closed by benjamin.peterson #16556: Update string.Formatter.vformat documentation to say "**kwargs http://bugs.python.org/issue16556 closed by ezio.melotti #16558: multiprocessing fails to raise exception with parameters http://bugs.python.org/issue16558 closed by sbt #16559: Update JSON tests http://bugs.python.org/issue16559 closed by serhiy.storchaka #16560: Python sighandlers delayed for no reason http://bugs.python.org/issue16560 closed by zdenek.pavlas #16563: re.match loops forever on simple regexp http://bugs.python.org/issue16563 closed by mark.dickinson #16567: Implementing .= for variable operator http://bugs.python.org/issue16567 closed by amaury.forgeotdarc #16570: Absolute imports fail to take full path into account? http://bugs.python.org/issue16570 closed by brett.cannon #16571: Iterating over inconsistently-indented code block causes execu http://bugs.python.org/issue16571 closed by mark.dickinson #16573: 2to3 should treat enumerate like sorted for zip, map, filter, http://bugs.python.org/issue16573 closed by python-dev #16578: Regular expressions with empty named groups break isname check http://bugs.python.org/issue16578 closed by Gabriel.Rodríguez.Alberich
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.
On Fri, 30 Nov 2012 14:38:12 -0500, 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
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
On Fri, Nov 30, 2012 at 4:07 PM, R. David Murray
On Fri, 30 Nov 2012 14:38:12 -0500, Brett Cannon
wrote: Do we have a graph of the historical trend of the number of bugs (or at least the historical details stored somewhere)? I think we have had a net
Not really. Ezio made one by hand once, but there is nothing automated.
The historical 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. =)
Hi,
On Fri, Nov 30, 2012 at 11:52 PM, Brett Cannon
On Fri, Nov 30, 2012 at 4:07 PM, R. David Murray
wrote: On Fri, 30 Nov 2012 14:38:12 -0500, Brett Cannon
wrote: Do we have a graph of the historical trend of the number of bugs (or at least the historical details stored somewhere)? I think we have had a net
Not really. Ezio made one by hand once, but there is nothing automated.
The one I made can be found here: https://docs.google.com/spreadsheet/ccc?key=0AplyAWXqkvHUdFF0SkVrT3VKcnRBZXN... 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
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.
participants (6)
-
Brett Cannon
-
Ezio Melotti
-
Petri Lehtinen
-
Python tracker
-
R. David Murray
-
Serhiy Storchaka