[issue2423] test_smtplib.py no longer butt slow
Richard Jones richardjo...@optushome.com.au added the comment: Merged mock socket from test_smtpd.py and committed. -- resolution: - accepted status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2423 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8739] Update to smtpd.py to RFC 5321
Richard Jones richardjo...@optushome.com.au added the comment: The smtpd module now has a test suite. Please add your unit tests to test_smtpd.py -- nosy: +richard ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8739 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9455] platform test borked in 2.7 branch on Power PC
Ronald Oussoren ronaldousso...@mac.com added the comment:
On 2 Aug, 2010, at 21:49, Bill Janssen wrote:
Bill Janssen bill.jans...@gmail.com added the comment:
So the problem is in the _mac_ver_xml() routine in Lib/platform.py, which
says:
machine = os.uname()[4]
if machine == 'ppc':
# for compatibility with the gestalt based code
machine = 'PowerPC'
and perhaps should say:
machine = os.uname()[4]
if machine in ('ppc', 'Power Macintosh'):
# for compatibility with the gestalt based code
machine = 'PowerPC'
That's correct. Thanks for catching this, I will fix this asap.
Ronald
--
Added file: http://bugs.python.org/file18333/smime.p7s
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9455
___
smime.p7s
Description: S/MIME cryptographic signature
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7900] posix.getgroups() failure on Mac OS X
Ronald Oussoren ronaldousso...@mac.com added the comment: Some else backported to 3.1 (that is, 3.1 already contained the fix when I tried the svnmerge) Backported to 2.7 in r83643 Backported to 2.6 in r83650 -- Added file: http://bugs.python.org/file18336/smime.p7s ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7900 ___ smime.p7s Description: S/MIME cryptographic signature ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7900] posix.getgroups() failure on Mac OS X
Changes by Ronald Oussoren ronaldousso...@mac.com: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7900 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9455] platform test borked in 2.7 branch on Power PC
Ronald Oussoren ronaldousso...@mac.com added the comment: Fixed in r83644 (3.x), r83645 (3.1), r83646 (2.7), r83651 (2.6) I'm not yet closing the issue, I want to check the buildbots later today. -- resolution: - fixed stage: - committed/rejected status: open - closed versions: +Python 2.6, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9455 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1748064] inspect.getargspec fails on built-in or slot wrapper methods
Changes by Trundle andy-pyt...@hammerhartes.de: -- nosy: +Trundle ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1748064 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9458] xml.etree.ElementTree.write(): encoding handling problems
Éric Araujo mer...@netwok.org added the comment: Is this a behavior bug or a doc bug? -- nosy: +merwok ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9458 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9458] xml.etree.ElementTree.write(): encoding handling problems
Changes by Florent Xicluna florent.xicl...@gmail.com: -- nosy: +effbot, flox ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9458 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8312] Add post/pre hooks for distutils commands
Éric Araujo mer...@netwok.org added the comment: And if you don’t allow hooks on other commands, people can still subclass them to add hooks support. I guess it’s best to keep it a consenting adults matter and not adding a restriction that can easily be circumvented. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8312 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5752] xml.dom.minidom does not escape CR, LF and TAB characters within attribute values
W. Trevor King wk...@drexel.edu added the comment:
And while we're at it, we should also
.replace('', 'amp;').replace('', quot;).replace('', 'lt;')
which would have to go at the beginning to avoid double-escaping the ''.
We could use xml.sax.saxutils.escape to do all the escaping rather than
chaining replaces:
data = escape(data, {'':'quot;', '\r':'#xD;', '\n':'#xA;', '\t':'#x9;'})
which also escapes '' (not strictly required for attribute values, but
shouldn't be harmful either).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5752
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Changes by Éric Araujo mer...@netwok.org: -- nosy: +merwok ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Georg Brandl ge...@python.org added the comment: The 3.2 docs now don't mention ConfigParser prominently anymore (as part of a different patch that added some features). Could be done in other branches as well. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6751] Default return value in ConfigParser
Changes by Éric Araujo mer...@netwok.org: -- nosy: +lukasz.langa, merwok ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6751 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6751] Default return value in ConfigParser
Éric Araujo mer...@netwok.org added the comment: Why is it needed to add varargs and kwargs instead of only a new “default” argument? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6751 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1410680] Add 'surgical editing' to ConfigParser
Changes by Éric Araujo mer...@netwok.org: -- nosy: +lukasz.langa ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1410680 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Łukasz Langa luk...@langa.pl added the comment: Yes, so the patch part is already solved. The thing that is still open to discussion is whether we should do something like this: 1. Pending-Deprecate naked the ConfigParser class in 3.2. 2. Deprecate it in 3.3. 3. Remove it in 3.4 and rename SafeConfigParser to ConfigParser. This is controversial but many developers (myself included) don't see the point in running naked ConfigParser because it's basically SafeConfigParser sans its completeness and predictability. So, please +1 or -1 the deprecation process idea. +1 from me -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Michael Foord mich...@voidspace.org.uk added the comment: +1 for deprecation. Nobody *should* be using ConfigParser anyway, and of those who are 99% either wouldn't notice or would have bugs in their code *fixed* by the rename, so I can't see much of a downside. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Éric Araujo mer...@netwok.org added the comment: If ConfigParser is not documented first, the name “SafeConfigParser” becomes strange—safe compared to what? These names have an historical motivation and could become clearer if renamed, but I don’t know if python-dev will agree with this deprecation. Renaming a class to an existing name with different behavior can be bad. FTR, in my head RawConfigParser is the config parser, and SafeConfigParser is another thing that I’ll maybe use one day. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Łukasz Langa luk...@langa.pl added the comment: If ConfigParser is not documented first, the name “SafeConfigParser” becomes strange—safe compared to what? The first sentence is Derived class of ConfigParser that implements a sane variant of the magical interpolation feature. I think it's enough for an explanation. If this were an encyclopedia, you would be right. But this is more like a Google search results page. Most people will take the first thing that looks like a solution they need. These names have an historical motivation and could become clearer if renamed That is the point. but I don’t know if python-dev will agree with this deprecation. That would be a shame, essentially it should happen in 3.0 IMO. But it's never too late I think. Think of the children! One day you will read this comment and think: whoa, this was even BEFORE 3.2! Yeah, ancient history. Renaming a class to an existing name with different behavior can be bad. Yes but this is going to be a problem for 3.4. Maybe then we'll come up with something more natural. FTR, in my head RawConfigParser is the config parser, and SafeConfigParser is another thing that I’ll maybe use one day. YMMV. FTR, many people I've spoken to treated RawConfigParser as something more low-level and not suitable for consumer use just because of the name AND the presence of a default (=name like the module) ConfigParser class. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Georg Brandl ge...@python.org added the comment: Agree with Michael, +1. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9292] Dead code in Modules/pyexpat.c
Changes by Antoine Pitrou pit...@free.fr: -- keywords: +easy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9292 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9299] os.makedirs(): Add a keyword argument to suppress File exists exception
Ray.Allen ysj@gmail.com added the comment: Doc review: Small typo, Flase vs False. Also, exceptions are raised rather than thrown in Python land (same for the docstring). Both exception references should be :exc:`OSError`. Here fixed these doc problems. Thanks for reviewing! Besides, the reason why I use throw rather than raise is that I found current Doc use throw an exception, so I think an exception is thrown. ^_^ -- Added file: http://bugs.python.org/file18338/mkdir.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9299 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9299] os.makedirs(): Add a keyword argument to suppress File exists exception
Georg Brandl ge...@python.org added the comment: Thanks for bringing that up, I've now fixed all these instances of throw that should be raise. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9299 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Éric Araujo mer...@netwok.org added the comment: The first sentence is Derived class of ConfigParser that implements a sane variant of the magical interpolation feature. I think it's enough for an explanation. True. but I don’t know if python-dev will agree with this deprecation. I wrote that before seeing Michael’s reply. Since Georg is +1 too, I can only say: Great, let’s do it! FTR, many people I've spoken to treated RawConfigParser as something more low-level and not suitable for consumer use just because of the name AND the presence of a default (=name like the module) ConfigParser class. Right. I don’t know if people using ConfigParser really want to use the interpolation. If we want to give the same name as the module to the best class for people who don’t read docs, I’d prefer renaming RawConfigParser to ConfigParser and SafeConfigParser to SomethingConfigParser. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9061] cgi.escape Can Lead To XSS Vulnerabilities
Éric Araujo mer...@netwok.org added the comment: Are 2.6 docs built by an older Sphinx version? I wonder why the text uses “the :func:`quoteattr` function in the :mod:`xml.sax.saxutils` module” and not “:func:`~xml.sax.saxutils.quoteattr” to get a direct link (or even just “consider using :func:`xml.sax.saxutils.quoteattr`.”). -- nosy: +merwok ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9061 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9061] cgi.escape Can Lead To XSS Vulnerabilities
Georg Brandl ge...@python.org added the comment: No, that's just a relic from the olden LaTeX days, and I've not paid attention enough to fix it :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9061 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Łukasz Langa luk...@langa.pl added the comment: Eric, while I agree that would be nice as well, renaming each and every parser in the module will be more problematic for sure. *** TO ALL: WHAT DO YOU SAY TO A PATH LIKE THIS *** 1) In 3.2 we add an alias: InterpolatingConfigParser = SafeConfigParser 1.1) In 3.2 we Pending-Deprecate: ConfigParser (message about it being removed in 3.4) SafeConfigParser (message about it being renamed to InterpolatingConfigParser in 3.4, a name you can already use) 2) In 3.3 we Deprecate: ConfigParser SafeConfigParser Same messages. 3) In 3.4 we remove ConfigParser and rename SafeConfigParser to InterpolatingConfigParser (removing the alias). So then we have two to choose from: Raw and Interpolating. As you see there's no default ConfigParser any more. I like that because it opens a new possibility which I would wait with until 3.5: re-introduce ConfigParser but as a completely new subclass that has better but backwards incompatible defaults. For now most of the new functionality I've added is turned off by default because of backwards compatibility reasons and this is unfortunate. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Fred L. Drake, Jr. fdr...@acm.org added the comment: 2010/8/3 Łukasz Langa rep...@bugs.python.org: 1) In 3.2 we add an alias: InterpolatingConfigParser = SafeConfigParser I'd rather see the class renamed and SafeConfigParser made the alias in 3.2. Otherwise, +1 for this plan (msg 112589), as there's no silent breakage. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Michael Foord mich...@voidspace.org.uk added the comment: I'd be happy with aliasing SafeConfigParser to ConfigParser in 3.2. Can we just do this without a deprecation process? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Fred L. Drake, Jr. fdr...@acm.org added the comment: Making ConfigParser an alias for SafeConfigParser creates a silent behavioral change. An application developer may not realize that users rely on the full ConfigParser anti-glory and end up breaking their configurations without so much as providing a heads-up in the application news. -1 So long as the application developer has to change their code to move away from ConfigParser, there's a better chance of affected end users receiving a heads-up. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Łukasz Langa luk...@langa.pl added the comment: Unfortunately, I have to agree with Fred here. We'll stick to renaming and the deprecation process. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9061] cgi.escape Can Lead To XSS Vulnerabilities
Fred L. Drake, Jr. fdr...@acm.org added the comment: Such constructs are notoriously tedious to grep for; patches are welcome. -- nosy: +fdrake ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9061 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Michael Foord mich...@voidspace.org.uk added the comment: Sorry - I misunderstood your earlier suggestion Fred. configparser.ConfigParser is the *natural* name for SafeConfigParser. I'm strongly +1 on moving towards that. (I doubt there would *actually* be any real code breakage if we did it earlier though ;-) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Michael Foord mich...@voidspace.org.uk added the comment: By the way, given that deprecation warnings are silent I am strongly -1 on removing the ConfigParser name altogether. That would cause far more breakage. As ConfigParser should not be used at all, and SafeConfigParser provides its functionality minus bugs, SafeConfigParser (horrible name) should replace it. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9444] argparse does not honor prefix_chars when adding default options
Steven Bethard steven.beth...@gmail.com added the comment: Yep, I'm fine with you committing this (after adding the prefix=+-/ you suggested). I don't have time right now to test the patches, but the code looks about right, and the tests ran fine for you, so I'm fine with it. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9444 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Éric Araujo mer...@netwok.org added the comment: Agree on the proposal of Łukasz, with the caveat mentioned by Fred (rename the class and make the old name an alias, for pickle and all). I’ll let Michael and Fred decide if the name ConfigParser has to go or not, I’m happy enough that the class will be deprecated and removed. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4188] Lib/threading.py causes infinite recursion when running as verbose
Changes by Meador Inge mead...@gmail.com: -- nosy: +minge ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4188 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled
Barry A. Warsaw ba...@python.org added the comment: Hi Ezio, what's the status on this issue for 2.6.6rc1? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7092 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5248] Adding T_SIZET to structmember.h
Changes by Meador Inge mead...@gmail.com: -- nosy: +minge ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5248 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1172711] long long support for array module
Changes by Meador Inge mead...@gmail.com: -- nosy: +minge ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1172711 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7828] chr() and ord() documentation for wide characters
Changes by Dirkjan Ochtman dirk...@ochtman.nl: -- nosy: +djc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7828 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7225] fwrite() compiler warnings
Changes by Dirkjan Ochtman dirk...@ochtman.nl: -- nosy: +djc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7186] Document specialness of __doc__, and possibly other special attributes
Changes by Dirkjan Ochtman dirk...@ochtman.nl: -- nosy: +djc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7186 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7141] 2to3 should add from __future__ import print_statement
Changes by Dirkjan Ochtman dirk...@ochtman.nl: -- nosy: +djc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7141 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8450] httplib: false BadStatusLine() raised
Changes by Dirkjan Ochtman dirk...@ochtman.nl: -- nosy: +djc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8450 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8867] serve.py (using wsgiref) cannot serve Python docs under Python3 due to encoding issues
Changes by Dirkjan Ochtman dirk...@ochtman.nl: -- nosy: +djc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8867 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8906] Document TestCase attributes in class docstring
Changes by Dirkjan Ochtman dirk...@ochtman.nl: -- nosy: +djc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8906 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9452] configparser support for reading from strings and dictionaries
Changes by Łukasz Langa luk...@langa.pl: Removed file: http://bugs.python.org/file18329/issue9452.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9452 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3871] cross and native build of python for mingw32 with distutils
LRN lrn1...@gmail.com added the comment:
Here's an alternative patch that enables Python building with MinGW/MSys
I've skimmed rpetrov's patch, and it seems that my patch is more about building
Python than about distutils (i've patched distutils only as far as the
compilation of Python itself (with the extensions already included in the
trunk) requires.
Brief patch description - what i did, and why:
Python/import.c:
* briefly fixed an issue with mkdir() already pointed out in code comments
Python/dynload_win.c:
* renamed strcasecmp to pystrcasecmp to avoid conflicts with the same function
defined in MinGW
Python/thread.c:
Python/ceval_gil.h:
* Made sure that Python won't try to include pthreads header when NT threads
are available
Include/osdefs.h:
* Made sure that the PYCC_GCC won't lead Python into defining *nix path
separation scheme
* Fixed redefinition of MAXPATHLEN (one of the few redefinitions i did fix,
there are just too many of them)
configure.in:
* Added corret MACHDEP=win32 for MinGW
* Added lots of new AC_SUBST'ed variables, they are used later to alter
Makefile and Setup functionality
MACHDEP_PATH_SEPARATOR - to put ';' instead of ':' as path separator in
machdep
NTOBJS - extra object files to insert into makefile
FROZEN_MAIN - controls the inclusion of Python/frozenmain.o into libpython.
Why is it even there? Prevents the library from linking.
NT_LDFLAGS - extra LDFLAGS to add on Windows
SHAREDINSTALL - controls which sharedinstall target is built (works around
MSys weirdness, see below)
USE_*_MODULE - controls the inclusion of modules in Setup.config.in
ms_windows - indicates that we're building on Windows through the rest of
configure.in
Special MINGW32_NT*/1.* case entry sets all of the above as well as some some
#defines that traditionally are just hard-coded in PC/pyconfig.h (not all the
defines from PC/pyconfig.h are here, there might be a need to add some more)
* Added MINGW32* to trigger CYGWIN* cases or added separate MINGW32* cases in
most uname tests.
* Added MS_COREDLL definition (why is it separate from other Windows-specific
AC_DEFINEs? I don't remember...)
* Added a separate check for CreateThread, a special variable
(ac_cv_nt_threads) to indicate its success, and some code to switch on NT
threads and switch off any other threads (including pthreads which ARE
available on Windows)
* Added checks for some headers (pwd.h, sys/ioctl.h etc) and functions (spawn,
spawnv, system etc) that are (are they?) traditionally available on *nix and
are not checked for.
* Added correct DYNLOADFILE definition for MinGW
* Worked around AC_STRUCT_ST_BLOCKS weirdness by removing fileblocks.o from the
list of object files (this one might not be portable, should check that it
works on *nix)
* Fixed a strange bug in AC_COMPILE_IFELSE around have_prototypes=yes - when
left with an empty argument [] it probuces broken (?) code in configure script
(or maybe it's bash that is broken, i don't know)
* Fixed /dev/ptmx detection - MSys will tell you it's available, but it is only
an MSys thing, Python shouldn't think it is there.
* Fixed PY_FORMAT_SIZE_T definition - AFAIK MinGW does not allow %z format in
printf (in my test cases i've found that some definitions can prevent GCC from
throwing an error about this format, but i couldn't reproduce this GCC
behaviour in Python build system).
* Added ws2tcpip.h into socket test
* Added PC as a subdirectory
setup.py:
* Added module's location into sys.path. This is required to correctly import
multiprocessing (it imports itself recursively, and since its .pyd file is in
unusual location, it couldn't find itself)
* Added some config_h_vars.get() checks for some extensions (which is why some
extra function/header checks were necessary in configure.in) - no setup.py
won't try to build extensions that can't be built
* Added 'msys' in sys.builtin_module_names kind of checks in some places.
When successful, this check indicates that Python is built in MSys, and alters
otherwise win32-oriented logic in setup.py and some other modules to adapt to
MSys environment
* Changed the way MODULE_NAME is passed to sqlite3 extension (see below)
* Added extra library dependencies for multiprocessing extension
* Prevented setup.py from adding libX11 dependency to tkinter on Windows
* Added some msysize() calls (see below) to fix the paths passed to os.system()
calls
* Added extra library dependencies for ctypes extension
PC/errmap.h:
* Re-generated it with new generrmap.c (see below)
PC/generrmap.c:
* Added an implementation of _dosmaperr() function, which is available in MSVC
MSVCRT static library, but not in its MinGW counterpart (code is from
PostgreSQL, should be compatible with Python license)
Lib/distutils/spawn.py:
* Fixed spawn_nt to use os.system() in conjunction with 'env.exe' program to
call external tools - works like a charm in MSys ('env.exe' is an MSys tool,
lives in /bin, and it hooks up MSys shell
[issue8138] wsgiref.simple_server.SimpleServer claims to be multithreaded
Changes by Dirkjan Ochtman dirk...@ochtman.nl: -- nosy: +djc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8138 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6785] IncompleteRead / BadStatus when parsing http://peakoil.mobi
Changes by Dirkjan Ochtman dirk...@ochtman.nl: -- nosy: +djc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6785 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9452] configparser support for reading from strings and dictionaries
Łukasz Langa luk...@langa.pl added the comment: Updated patch after discussion on #python-dev: - PEP8 compliant names used: read_file, read_string, read_dict. readfp has been PendingDeprecated - documentation updates - option validation is now optional with the use of `strict=` argument in the parser's __init__ - new unit tests introduced to check for the new behaviour -- Added file: http://bugs.python.org/file18341/issue9452.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9452 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9452] configparser support for reading from strings and dictionaries
Łukasz Langa luk...@langa.pl added the comment: FTR, some people questioned the purpose of read_dict(). Let me summarize this very briefly here: - the API is using dictionaries similar to those in defaults= but has one level of depth more (sections) - initializing a parser with a dictionary produces syntax that is more natural in code - having a single method implementing reading a dictionary with unit tests, support for proper duplicate handling, etc. frees users from writing their own - we need that anyway for upcoming mapping protocol access discussed in #5412 - more detailed use cases in msg112429 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9452 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Michael Foord mich...@voidspace.org.uk added the comment: Getting *rid* of the name ConfigParser would be annoying and cause *gratuitous* code breakage. If we are going to keep the name but get rid of the unsafe version then we can only replace it with what is now SafeConfigParser - as it is almost entirely compatible with it. (Modulo the bug fixing behavioural change.) So the real choices are: * leave ConfigParser as it is * deprecate it but not remove it (so as not to needlessly break code) * deprecate now and replace with SafeConfigParser later Only the last of these is a positive step forwards... :-) (Strongly -1 on introducing *yet another name* to refer to these classes by.) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Łukasz Langa luk...@langa.pl added the comment: There IS one more option that seems to be better than all of the above: 1. Add an interpolation=True argument to RawConfigParser __init__ and move the interpolating functionality from SafeConfigParser to it. 2. Rename RawConfigParser to ConfigParser leaving the old name in PendingDeprecation with interpolation=False. 3. Make an alias for SafeConfigParser pointing to ConfigParser with PendingDeprecation. We can do all this for 3.2 I guess without inflicting any actual damage. It will fix more bugs in running code that break config files. Maybe we shouldn't be so afraid after all and just clean it up. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9352] argparse eats characters when parsing multiple merged short options
Catherine Devlin fredv8vi...@liquidid.net added the comment: Attaching a test to verify parse failure on mismatched prefix (-abc or +abc). Steven's patch makes it pass. -- nosy: +catherine versions: -Python 2.7, Python 3.2 Added file: http://bugs.python.org/file18342/test_multiple_short_same_prefix.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9352] argparse eats characters when parsing multiple merged short options
Catherine Devlin fredv8vi...@liquidid.net added the comment: Updated Steven's patch; no changes, but now it knows the new context so that ``patch -p0`` won't fail. -- Added file: http://bugs.python.org/file18343/multiple_short_same_prefix_new.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9352 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9450] readline.replace_history_item leaks memory.
Mark Dickinson dicki...@gmail.com added the comment: Leaks in replace_history_item and remove_history_item fixed in r83667 (py3k), r83668 (release31-maint) and r83669 (release27-maint). -- versions: +Python 2.7, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9450 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9495] argparse unittest tracebacks are confusing if an error is raised when not expected
New submission from R. David Murray rdmur...@bitdance.com: In python3 if an error is raised from ErrorRaisingArgumentParser that is not caught by an assertRaises, unittest prints out the traceback, which is a chained traceback including the SystemExit that the argparse test suite catches in order to produce the ArgumentParserError that is actually of interest. I think the argparse test suite should break that chain to make the tracebacks when failures happen more on-point. -- components: Tests keywords: easy messages: 112625 nosy: r.david.murray priority: low severity: normal stage: needs patch status: open title: argparse unittest tracebacks are confusing if an error is raised when not expected type: behavior versions: Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9495 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7003] finish documentation of user local paths
Mark Lawrence breamore...@yahoo.co.uk added the comment: Should this now go to d...@python or is it best left with Christian? -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7003 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7141] 2to3 should add from __future__ import print_statement
Mark Lawrence breamore...@yahoo.co.uk added the comment: @Daniel there's far chance of this happening if you could provide a patch. -- nosy: +BreamoreBoy versions: -Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7141 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7186] Document specialness of __doc__, and possibly other special attributes
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- assignee: georg.brandl - d...@python nosy: +d...@python ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7186 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9495] argparse unittest tracebacks are confusing if an error is raised when not expected
R. David Murray rdmur...@bitdance.com added the comment: I can't find anyway to actually do what I suggested. There doesn't seem to be any way to break the traceback chain. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9495 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9340] argparse parse_known_args does not work with subparsers
Catherine Devlin fredv8vi...@liquidid.net added the comment: Some basic unit tests for parse_known_args on a subparser. -- keywords: +patch nosy: +catherine Added file: http://bugs.python.org/file18344/test_subparser_parse_known_args.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9340 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7225] fwrite() compiler warnings
Mark Lawrence breamore...@yahoo.co.uk added the comment: I'm assuming that this is still an issue, sorry I don't have gcc 4.3.2 to try it out on. -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8065] Memory leak in readline.get_current_history_length
Mark Dickinson dicki...@gmail.com added the comment: I've fixed this leak in r83670 through r83672. It's still using the old, inefficient method (get the state, read the length, free the state), because without good tests I don't want to disturb things too much. In particular, it's not clear whether libedit keeps the history_length variable properly updated. There are still the remaining issues of: - better testing for the readline module, and - attempting to work around libedit bugs. Perhaps those should become separate issues, though? -- versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8065 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9450] readline.replace_history_item leaks memory.
Mark Dickinson dicki...@gmail.com added the comment: The other leaks have now been fixed too; see issue 8065 for details. -- assignee: - mark.dickinson resolution: - fixed stage: needs patch - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9450 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7828] chr() and ord() documentation for wide characters
Changes by Antoine Pitrou pit...@free.fr: -- assignee: georg.brandl - d...@python nosy: +d...@python, haypo versions: -Python 2.6, Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7828 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9340] argparse parse_known_args does not work with subparsers
Changes by Catherine Devlin fredv8vi...@liquidid.net: Removed file: http://bugs.python.org/file18344/test_subparser_parse_known_args.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9340 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8867] serve.py (using wsgiref) cannot serve Python docs under Python3 due to encoding issues
Antoine Pitrou pit...@free.fr added the comment: Here is a simple patch. -- keywords: +patch nosy: +pitrou Added file: http://bugs.python.org/file18345/serve.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8867 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8867] serve.py (using wsgiref) cannot serve Python docs under Python3 due to encoding issues
Antoine Pitrou pit...@free.fr added the comment: Fixed in r83673. -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8867 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9340] argparse parse_known_args does not work with subparsers
Catherine Devlin fredv8vi...@liquidid.net added the comment: Some simple unit tests for parse_known_args on a parser with a subparser. They are indeed failing on the trunk. -- Added file: http://bugs.python.org/file18346/test_subparser_parse_known_args.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9340 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9496] Unittests for Lib/rlcompleter.py
New submission from Michele Orrù maker...@gmail.com: The attached patch tests Lib/rlcompleter.py. -- components: Tests files: testrlcompleter.patch keywords: patch messages: 112636 nosy: ezio.melotti, maker priority: normal severity: normal status: open title: Unittests for Lib/rlcompleter.py type: feature request versions: Python 3.2 Added file: http://bugs.python.org/file18347/testrlcompleter.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9496 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9497] test_ssl memory leak
New submission from Mark Dickinson dicki...@gmail.com: On OS X 10.6, with a 64-bit build of Python, regrtest -L is showing leaks from test_ssl. Here are the first few lines of the output; I've also attached the full output. newton:py3k dickinsm$ ./python.exe -m test.regrtest -L test_ssl [1/1] test_ssl 1 test OK. leaks Report Version: 2.0 Process: python.exe [36421] Path:/Users/dickinsm/python/svn/py3k/python.exe Load Address:0x1 Identifier: python.exe Version: ??? (???) Code Type: X86-64 (Native) Parent Process: bash [80529] Date/Time: 2010-08-03 18:48:10.072 +0100 OS Version: Mac OS X 10.6.4 (10F569) Report Version: 6 Process 36421: 8194 nodes malloced for 15049 KB Process 36421: 106 leaks for 4080 total leaked bytes. Leak: 0x10173df50 size=272 zone: DefaultMallocZone_0x1002f7000string '/C=US/ST=Delaware/L=Wilmington/O=Python Software Foundation/OU=SSL/CN=somemachine.python.org' Leak: 0x10171c0c0 size=192 zone: DefaultMallocZone_0x1002f7000 0x31898130 0x0609300b 0x06045503 0x53550213 0..1.0...UUS 0x0f301131 0x04550306 0x44081308 0x77616c65 1.0...UDelaw 0x31657261 0x06113013 0x07045503 0x69570a13 are1.0...UWi 0x6e696d6c 0x6e6f7467 0x21302331 0x04550306 lmington1#0!..U. 0x501a130a 0x6f687479 0x6f53206e 0x61777466 ...Python Softwa 0x46206572 0x646e756f 0x6f697461 0x300c316e re Foundation1.0 0x5503060a 0x03130b04 0x314c5353 0x061d301f ...USSL1.0.. 0x03045503 0x6f731613 0x616d656d 0x6e696863 .Usomemachin ... Leak: 0x10171e7a0 size=192 zone: DefaultMallocZone_0x1002f7000 0x31898130 0x0609300b 0x06045503 0x53550213 0..1.0...UUS 0x0f301131 0x04550306 0x44081308 0x77616c65 1.0...UDelaw 0x31657261 0x06113013 0x07045503 0x69570a13 are1.0...UWi 0x6e696d6c 0x6e6f7467 0x21302331 0x04550306 lmington1#0!..U. 0x501a130a 0x6f687479 0x6f53206e 0x61777466 ...Python Softwa 0x46206572 0x646e756f 0x6f697461 0x300c316e re Foundation1.0 0x5503060a 0x03130b04 0x314c5353 0x061d301f ...USSL1.0.. 0x03045503 0x6f731613 0x616d656d 0x6e696863 .Usomemachin ... -- files: test_ssl_leak_report.txt messages: 112637 nosy: janssen, mark.dickinson priority: normal severity: normal stage: needs patch status: open title: test_ssl memory leak type: resource usage versions: Python 3.2 Added file: http://bugs.python.org/file18348/test_ssl_leak_report.txt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9497 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Fred L. Drake, Jr. fdr...@acm.org added the comment: It doesn't make sense to make any of these changes to Python 2; this really should have been separate from the documentation issue. That's probably understood by everyone, but explicit is better. Merging implementations --- - I've no objection to merging RawConfigParser and SafeConfigParser, using a constructor argument to control whether interpolation is performed. It's not clear this provides any improvement in maintainability or usage. - Isolating the old (broken interpolation) ConfigParser behavior so it's not in the middle of the inheritance stack would be good. Changing ConfigParser behavior -- Changing the behavior of the ConfigParser name requires the deprecation process. We may think nobody in their right mind is using that, but changing something out from under app developers is really bad. This should be considered a problem for configparser as outlined in msg 112598. Whether we can assign new semantics to the ConfigParser name in the future is questionable. I think Python's compatibility policy allows it, but that doesn't make it a good idea. (This seems to be the real sticking point, unfortunately.) Class names --- I don't understand Michael's objection to adding new names for the configparser classes; that's one of the few points where we don't run into backward-compatibility black holes. In the case of a merged implementation, a new name for the merged class (possibly Configuration) may be the best bet; the old names can then be subclasses of that which generate appropriate deprecation warnings. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1777398] IDLE Freezes After Running Scripts
Terry J. Reedy tjre...@udel.edu added the comment: Intermittent bugs involving 3rd-party packages are hard to even confirm, let alone fix. 2.6.6rc will be out today, so no fix for that. IDLE on 3.1.2 is more stable than it was on 3.0, so I will not assume that the problem still exists on the even newer 2.7. And AFAIK, there is no wxpython for 3.1. So unless this is verified to still be a problem with 2.7 and the latest wxpython 2.8.11.0+, it should be closed as out-of-date. -- nosy: +tjreedy status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1777398 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Changes by Łukasz Langa luk...@langa.pl: -- versions: -Python 2.6, Python 2.7, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3362] locale.getpreferredencoding() gives bus error on Mac OS X 10.4.11 PPC
Changes by Terry J. Reedy tjre...@udel.edu: -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.5, Python 2.6, Python 3.0 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3362 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2620] Multiple buffer overflows in unicode processing
Changes by Terry J. Reedy tjre...@udel.edu: -- status: open - closed versions: -Python 2.4, Python 3.0 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2620 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9496] Unittests for Lib/rlcompleter.py
Antoine Pitrou pit...@free.fr added the comment: From a quick look the patch looks nice, thanks! There's a typo (builtinis namespace). -- nosy: +pitrou versions: +Python 2.7, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9496 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9496] Unittests for Lib/rlcompleter.py
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +r.david.murray stage: - patch review type: feature request - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9496 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1856] shutdown (exit) can hang or segfault with daemon threads running
Terry J. Reedy tjre...@udel.edu added the comment: Is this still an issue in 2.7 or 3.x? Or should it be closed? -- nosy: +tjreedy versions: +Python 2.7 -Python 2.5, Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1856 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1758146] Crash in PyObject_Malloc
Terry J. Reedy tjre...@udel.edu added the comment: Is this still an issue for 2.7 or 3.x? Is it actually a Python issue or should it be closed? -- nosy: +tjreedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1758146 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6517] Emphasising in the docs configparser.SafeConfigParser over ConfigParser
Michael Foord mich...@voidspace.org.uk added the comment: If we merge the functionality in a single class with a new name then I guess that is fine as it will simplify the documentation rather than complexify it (good word hey). We still need to *mention* the old names so that people finding them in old code can find an up to date reference on them. Here's what I don't understand about Fred's difficulty with replacing ConfigParser with the sane implementation. After we deprecate ConfigParser as it is now we have two choices. * delete the ConfigParser name - breaking *all* code that uses it and has not been updated * point the name at what is currently called SafeConfigParser - causing a slight risk of incompatibility but likely *improving* most code that hasn't been updated I don't see how the first option could *in any way* be preferable to the second. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9444] argparse does not honor prefix_chars when adding default options
R. David Murray rdmur...@bitdance.com added the comment: Committed (with the additional test) to py3k in r83657, and 2.7 in r83676. -- stage: commit review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9444 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9497] test_ssl memory leak
Mark Dickinson dicki...@gmail.com added the comment: From a bit of experimentation, ssl._ssl._test_decode_cert seems to be the call that's leaking. I haven't studied the source to see if I can pinpoint the cause yet. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9497 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9496] Unittests for Lib/rlcompleter.py
Mark Dickinson dicki...@gmail.com added the comment: The new tests pass on OS X, using both GNU readline (v6.1) and the system libedit. -- nosy: +mark.dickinson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9496 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1540529] cgi.py error on parsing/handling content-disposition
Terry J. Reedy tjre...@udel.edu added the comment: With 3.1.2, cgi.parse_header gives the same correct response as cgtest.parse_header, so I will assume that the same is true in 2.7 until demonstrated otherwise. -- nosy: +tjreedy resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1540529 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3467] sqlite3 path is hard coded in setup.py
Terry J. Reedy tjre...@udel.edu added the comment: Martin, should this be closed? fixed? won't fix? out-of-date? The link to Modules/Setup does not work for py3k branch. -- nosy: +tjreedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3467 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4956] Py_Initialize needs to be done before file load (on msys+wine)
Changes by Terry J. Reedy tjre...@udel.edu: -- resolution: - out of date status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4956 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5202] wave.py cannot write wave files into a shell pipeline
Terry J. Reedy tjre...@udel.edu added the comment: Is this still a problem with 2.7-3.2? GP, what state do you think either patch is in? -- nosy: +tjreedy stage: - patch review versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.5, Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5202 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3067] setlocale fails with unicode strings on Py2 and with byte strings on Py3
Terry J. Reedy tjre...@udel.edu added the comment: The docs say that the locale arg should be None, tuple, or string, so I take that to mean that Unicode should be OK for 2.x, and that would help porting to 3.x. If bytes are rejected in 3.x, there should be TypeError raised, not ValueError, as is still the case in 3.1.2. -- keywords: +easy nosy: +tjreedy stage: - unit test needed type: - behavior versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.5, Python 2.6, Python 3.0 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3067 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9497] test_ssl memory leak
Mark Dickinson dicki...@gmail.com added the comment: The fix turned out to be as simple as adding a single X509_free call to _test_decode_cert. Fixed in revisions r83677 (py3k), r83679 (release31-maint), r83680 (release27-maint) and r83686 (release26-maint). [The last with Barry's approval.] -- assignee: - mark.dickinson components: +Extension Modules resolution: - fixed stage: needs patch - committed/rejected status: open - closed versions: +Python 2.6, Python 2.7, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9497 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3511] Incorrect charset range handling with ignore case flag?
Terry J. Reedy tjre...@udel.edu added the comment: EM and MB seemed to agree on closing this. -- nosy: +tjreedy resolution: - wont fix status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3511 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2200] find_executable fails to find .bat files on win32
Changes by Terry J. Reedy tjre...@udel.edu: -- versions: -Python 2.5, Python 2.6, Python 3.0 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2200 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1978] Python(2.5.1) will be crashed when i use _ssl module in multi-threads environment in linux.
Changes by Terry J. Reedy tjre...@udel.edu: -- resolution: - out of date status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1978 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9458] xml.etree.ElementTree.ElementTree.write(): encoding handling problems
Uli Kunitz uli.kun...@googlemail.com added the comment: I believe handling of TextIOWrapper streams is broken in xml.etree.ElementTree.ElementTree.write(). First example: import sys from xml.etree import ElementTree element = ElementTree.fromstring(foobarfoobar/bar/foo) element_tree = ElementTree.ElementTree(element) assert sys.stdout.encoding == UTF-8 element_tree.write(sys.stdout, encoding=UTF-8) print() I don't think that write a tree into a stream with the correct encoding should generate any problem at all. The output looks like this: Traceback (most recent call last): File /home/kunitz/test/lib/python3.2/xml/etree/ElementTree.py, line 825, in write xmlcharrefreplace)) TypeError: must be str, not bytes During handling of the above exception, another exception occurred: Traceback (most recent call last): File bug1.py, line 9, in module element_tree.write(sys.stdout, encoding=UTF-8) File /home/kunitz/test/lib/python3.2/xml/etree/ElementTree.py, line 843, in write write(?xml version='1.0' encoding='%s'?\n % encoding_) File /home/kunitz/test/lib/python3.2/xml/etree/ElementTree.py, line 827, in write _raise_serialization_error(text) File /home/kunitz/test/lib/python3.2/xml/etree/ElementTree.py, line 1077, in _raise_serialization_error cannot serialize %r (type %s) % (text, type(text).__name__) TypeError: cannot serialize ?xml version='1.0' encoding='UTF-8'?\n (type str) Example 2: import sys from xml.etree import ElementTree element = ElementTree.fromstring(foobarfööbar/bar/foo) element_tree = ElementTree.ElementTree(element) with open(bug2.xml, w, encoding=US-ASCII) as f: element_tree.write(f) The first ö umlaut generates an UnicodeEncodeError here, while the method could use XML character references. One could argue this, but the method could take care of the problem. Third example: import sys from xml.etree import ElementTree element = ElementTree.fromstring(foobarfööbar/bar/foo) element_tree = ElementTree.ElementTree(element) with open(bug3.xml, w, encoding=ISO-8859-1, errors=xmlcharrefreplace) as f: element_tree.write(f, xml_declaration=True) This creates finally an ISO-8859-1 encoded XML file, but without XML declaration. Didn't we request one? Example 4: Try to do the right thing. import sys from xml.etree import ElementTree element = ElementTree.fromstring(foobarfööbar/bar/foo) element_tree = ElementTree.ElementTree(element) with open(bug4.xml, w, encoding=ISO-8859-1, errors=xmlcharrefreplace) as f: element_tree.write(f, encoding=ISO-8859-1, xml_declaration=True) Here we get the same exception as example 1 of course. All the files can be found in the tar container below. -- title: xml.etree.ElementTree.write(): encoding handling problems - xml.etree.ElementTree.ElementTree.write(): encoding handling problems type: - behavior Added file: http://bugs.python.org/file18349/bugs.tar.gz ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9458 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5414] asciibin.a2b_uu returns unexpected values on non ascii data
Terry J. Reedy tjre...@udel.edu added the comment: In 3.1.2, a2b_uu() now raises TypeError: a2b_uu() takes exactly 1 argument (0 given) as it should. I assume the same of 2.7. The manual claims, in effect, that a2b_uu(b2a_uu(data))== data. The behavior of a2b_uu with any other input (not from b2a_uu) seems to be undefined. -- nosy: +tjreedy resolution: - out of date stage: - unit test needed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5414 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5504] ctypes should work with systems where mmap can't be PROT_WRITE and PROT_EXEC
Changes by Terry J. Reedy tjre...@udel.edu: -- versions: -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5504 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
