[issue2101] xml.dom documentation doesn't match implementation
Bruno Gola added the comment: This seems to be a documentation bug. Patch attached. -- nosy: +brunogola Added file: http://bugs.python.org/file9494/issue_2101_doc.patch __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2101> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2285] list.sort.__doc__ says "cmp" is a keyword, but it isn't.
Bruno Gola <[EMAIL PROTECTED]> added the comment: i'm using the lastest version from subversion (trunk) and cmp still is a keyord for list.sort. -- nosy: +brunogola __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2285> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3709] BaseHTTPRequestHandler innefficient when sending HTTP header
Bruno Gola added the comment: applied the patch on py3k on trunk and everything seems fine (works here) -- nosy: +brunogola ___ Python tracker <http://bugs.python.org/issue3709> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10453] Add -h/--help option to compileall
Bruno Gola added the comment: applied the patch on an ubuntu 10.04 64bits, py3k (trunk) test_force fails as following: == FAIL: test_force (__main__.CommandLineTests) -- Traceback (most recent call last): File "Lib/test/test_compileall.py", line 202, in test_force self.assertNotEqual(access, access2) AssertionError: 1290285399.744327 == 1290285399.744327 -- -- nosy: +brunogola ___ Python tracker <http://bugs.python.org/issue10453> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10492] test_doctest fails with iso-8859-15 locale
Bruno Gola added the comment: tests are OK for me running on ubuntu 10.04 64bits and py3k from svn repository. -- nosy: +brunogola ___ Python tracker <http://bugs.python.org/issue10492> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2535] duplicate Misc.lower
Bruno Gola <[EMAIL PROTECTED]> added the comment: The patch seems to be ok, worked here applying it to rev62992 (trunk). This "bug" is also on py3k, but Tkinter.py has changed. Could anyone create and send a patch for py3k? -- nosy: +brunogola __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2535> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2345] Using an exception variable outside an 'except' clause should raise a Py3K warning
Bruno Gola <[EMAIL PROTECTED]> added the comment: see http://bugs.python.org/issue2380, I think that it's related. the only reason i see for nested tuples to be valid syntax in an except clause was: x = ValueError y = (TypeError, IndexError) ... except (x, y): ... and this will not be valid in py3k, as noticed here. -- nosy: +brunogola __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2345> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2380] Raise a Py3K warning for catching nested tuples with non-BaseException exceptions
Bruno Gola <[EMAIL PROTECTED]> added the comment: Should nested tuples in an except clause be a valid syntax? like: ... except ((ValueError, Exception), TypeError, (...)): pass I don't see any benefit and because of this behavior the implementation (in Python/errors.c and in the patch attached) will use recursive function. I think that any objects inside a tuple in an except clause should be treated equally (as an object), even a tuple, so the except clause above should be an error in py3k and should produce a warning because the list objects does not inherits BaseException. Please, see my comment in http://bugs.python.org/issue2345, it is related to this issue. -- nosy: +brunogola __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2380> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3156] bytes type has inconsistent methods (append, insert)
Bruno Gola <[EMAIL PROTECTED]> added the comment: The following patch fixes the behavior, .append and .insert will accept only integer as parameters. Is this really the desired behavior? I mean, why not to accept a character for both methods? There are two tests in Lib/test/test_io.py that uses the old behavior for .append(). -- keywords: +patch nosy: +brunogola Added file: http://bugs.python.org/file10691/issue3156.patch ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3156> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
