[issue1148] TypeError on join - httplib mixing str and bytes

New submission from Eduardo Padoan: To reproduce: >>> import httplib >>> conn = httplib.HTTPConnection("www.python.org") >>> conn.request("GET", "/index.html") >>> r1 = conn.getresponse() >>> r1.read() Traceback (most re

[issue1151] "TypeError: expected string, bytes found" instead of KeyboardInterrupt

New submission from Eduardo Padoan: On revision 54803, interactive mode, on linux: if type ctrl+c you type ctrl+c, it should raise KeyboardInterrupt, but "TypeError: expected string, bytes found" printed. Also, I could *not* catch it doing: >>> try: ... while Tr

[issue1161] Mangled chars in offending line of SyntaxError traceback

New submission from Eduardo Padoan: Python 3.0a1 (py3k:58103, Sep 11 2007, 13:52:21) [GCC 4.1.2 (Ubuntu 4.1.2-0ubuntu4)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> asd asd File &qu

[issue1161] Garbled chars in offending line of SyntaxError traceback

Changes by Eduardo Padoan: -- title: Mangled chars in offending line of SyntaxError traceback -> Garbled chars in offending line of SyntaxError traceback __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.o

[issue1165] Should itertools.count work for arbitrary integers?

New submission from Eduardo Padoan: Currently, itertools.count.__next__ checks wether the current value is > PY_SSIZE_T_MAX and raises OverflowError if so. Shouldn't the value be stored as "long", at least in Py3k? Not that I have any use case for it, so it is minor. ---

[issue1165] Should itertools.count work for arbitrary integers?

Changes by Eduardo Padoan: -- severity: critical -> minor __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1165> __ ___ Python-bugs-list mailing li

[issue1161] Garbled chars in offending line of SyntaxError traceback

Eduardo Padoan added the comment: Can't reproduce this error anymore with revision 58472. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1161> __ ___ Python-

[issue1151] "TypeError: expected string, bytes found" instead of KeyboardInterrupt

Eduardo Padoan added the comment: Can't reproduce this error anymore with revision 58472. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1151> __ ___ Python-

[issue2046] patch to fix_import: UserDict -> collections

New submission from Eduardo Padoan: UserDict moved from UserDict module (deleted) to collections on py3k. This patch adds this case to fix_import.py on 2to3. -- assignee: collinwinter components: 2to3 (2.x to 3.0 conversion tool) files: fix_import_udict.diff messages: 62186 nosy

[issue2060] python2.6 -3 gives "warning: callable() not supported in 3.x" on startup

New submission from Eduardo Padoan: Running python2.6 with the -3 option, you get 6 warnings about callable(): [EMAIL PROTECTED]:~/dev/svn/python2.6$ python2.6 -3 warning: callable() not supported in 3.x warning: callable() not supported in 3.x warning: callable() not supported in 3.x warning

[issue2060] python2.6 -3 gives "warning: callable() not supported in 3.x" on startup

Eduardo Padoan added the comment: > By the way, what are you supposed you use in py3k instead of callable? Either "try: foo(); except TypeError: ...", or "if hasattr(foo, '__call__'): foo()". __ Tracker <[EMAIL PROTECTED