[issue1125] bytes.split shold have same interface as str.split, or different name

Stefan Sonnenberg-Carstens added the comment: IMHO I also aggree that strings and bytes (list of bytes) should have the same interface. It is common sense that talking about strings most programmers think of a list of bytes composing it (char *). So the abbreviation should also hold true with

[issue1765140] logging: delay_fh option and configuration kwargs

Vinay Sajip added the comment: Thanks for the patch. I think it would be simpler to just implement an optional delay parameter in FileHandler and its subclasses: then the configuration stuff need not be touched at all, since the delay parameter can be specified in the configuration file. There

[issue1099] Mac compile fails with pydebug and framework enabled

Elias Pipping added the comment: I can reproduce this problem on both an intel and a powerpc mac. With '--with-pydebug --enable-framework --enable-universalsdk', the behavior is very much different: On a powerpc mac, configure fails with 'checking size of wchar_t...configure: error: cannot

[issue1131] Reference Manual: for statement links to break statement

New submission from Martoon: Error in the Windows distro documentation. If you go to for or for statement in the index, it brings you to the doc page for The break statement. -- components: Documentation, Windows messages: 55749 nosy: Martoon severity: minor status: open title:

[issue1125] bytes.split shold have same interface as str.split, or different name

Guido van Rossum added the comment: Updated patch that also modifies bytes.*strip(). __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1125 __Index: Objects/bytesobject.c

[issue1125] bytes.split shold have same interface as str.split, or different name

Guido van Rossum added the comment: New version with corrected docstrings and buffer support for *split() as well. Added unittests. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1125 __Index: Objects/bytesobject.c

[issue1125] bytes.split shold have same interface as str.split, or different name

Changes by Guido van Rossum: __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1125 __ ___ Python-bugs-list mailing list Unsubscribe:

[issue1125] bytes.split shold have same interface as str.split, or different name

Changes by Guido van Rossum: __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1125 __ ___ Python-bugs-list mailing list Unsubscribe:

[issue1099] Mac compile fails with pydebug and framework enabled

Bill Janssen added the comment: Which versions of OS X, please? And which Xcode versions? -- nosy: +janssen __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1099 __ ___

[issue1132] compile error in poplib.py

New submission from André: File c:\Python30\lib\poplib.py, line 137, in _getlongresp while line != '.': TypeError: can't compare bytes and str -- components: Library (Lib) messages: 55753 nosy: andre severity: normal status: open title: compile error in poplib.py type: compile error

[issue1107] 2to3, lambda with non-tuple argument inside parenthesis

Collin Winter added the comment: Fixed in r58055, r58056. -- resolution: - fixed status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1107 __ ___

[issue1132] compile error in poplib.py

Bill Janssen added the comment: Isn't this 1094? -- nosy: +janssen __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1132 __ ___ Python-bugs-list mailing list

[issue1133] python3.0-config raises SyntaxError

New submission from Viktor Ferenczi: Running python3.0-config raises SyntaxError: $ python3.0-config File /usr/local/bin/python3.0-config, line 33 print sysconfig.PREFIX ^ SyntaxError: invalid syntax OS: Ununtu Feisty, up-to-date Python: Python 3.0a1, compiled from

[issue1134] Parsing a simple script eats all of your memory

New submission from Viktor Ferenczi: Read the WARNING below, then run the attached script with Python3.0a2. It will eat all of your memory. WARNING: Keep a process killing tool or an extra command line at your fingertips, since this script could render your machine unusable in about 10-20

[issue1134] Parsing a simple script eats all of your memory

Viktor Ferenczi added the comment: Confirmed on Windows: OS: Windows XP SP2 ENG Python: Python3.0a1 MSI installer, default installation __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1134 __

[issue1134] Parsing a simple script eats all of your memory

Viktor Ferenczi added the comment: Works fine (does nothing) with Python 2.4.4 and Python 2.5.1 under Windows, so this bug must be caused by some new code in Python3.0a1. The bug depends on the contents of the doc string. There's another strange behavior if you write the word this in the

[issue1134] Parsing a simple script eats all of your memory

Viktor Ferenczi added the comment: Errata: In the first line of my original post I mean Python3.0a1 and not 3.0a2, certainly. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1134 __

[issue1135] xview/yview of Tix.Grid is broken

New submission from Hirokazu Yamamoto : Attached code test_tixGrid.py fails with following error message. TypeError: yview() takes exactly 1 argument (4 given) -- components: Tkinter files: test_tixGrid.py

[issue1135] xview/yview of Tix.Grid is broken

Hirokazu Yamamoto added the comment: Probably right fix is attached file fix_tixGrid.patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1135