[issue4071] ntpath.abspath fails for long str paths

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: Fixed unicode issue in r67154(trunk). I'm not sure how to handle long str, so I didn't touch it for now. -- versions: +Python 2.5.3, Python 2.7 ___ Python tracker <[EMAIL PROTECTED]>

[issue4282] (Python3) The profile module deesn't understand the character set definition

New submission from Takafumi SHIDO <[EMAIL PROTECTED]>: The profile module of Python3 deesn't understand the character set of the script. When a profile is executed (like $python -m profile -o prof.dat foo.py) on a code (say foo.py) which defines its character set in the second line (like #codin

[issue4118] Built-in compile() and ast module doc issues

Terry J. Reedy <[EMAIL PROTECTED]> added the comment: The 2.6 sentence that got deleted in 3.0: I at least somewhat agree. "When compiling a string with multi-line statements, two caveats apply: line endings must be represented by a single newline character ('\n'), and the input must be termina

[issue3073] Cookie.Morsel breaks in parsing cookie values with whitespace

mixedpuppy <[EMAIL PROTECTED]> added the comment: The problem is that spaces are not allowed in the attribute values. Here is a work around # hack fix of Cookie.BasicCookie import Cookie import re _LegalCharsPatt = r"\w\d!#%&'~_`><@,:/\$\*\+\-\.\^\|\)\(\?\}\{\=" _FixedCookiePattern = re.compil

[issue3073] Cookie.Morsel breaks in parsing cookie values with whitespace

Changes by Trent Mick <[EMAIL PROTECTED]>: -- nosy: +trentm ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing list

[issue4281] Idle - incorrectly displaying a character (Latin capital letter sharp s)

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: My mistake, I did not know that "SHARP S" stands for the "Eszett" German letter. There is a font (Myriad Web on my system) that proposes a (wrong) glyph for this code point. According to http://www.tcl.tk/software/tcltk/whatsnew.tml#i

[issue4118] Built-in compile() and ast module doc issues

Raymond Hettinger <[EMAIL PROTECTED]> added the comment: General comment: Stylistically, the docs should mostly be stated in a positive manner, stating what a tool does, how it should be used, and what is left undefined. IMO, it is harmful to fill the docs with CAVEATS and WARNINGS. --

[issue1429539] pdb: fix for 1326406 (import __main__ pdb failure)

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: I am not sure whether it is appropriate to comment on a closed issue, but if the tracker will take this comment, hopefully it will find the right audience. I have recently stumbled on this bug running python 2.5. While tracking the

[issue4281] Idle - incorrectly displaying a character (Latin capital letter sharp s)

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: IDLE, in itself, doesn't do anything special to render that character. It passes it on to Tk. I don't know how precisely Tk works in this case, but it might be that it doesn't do anything special with the character *either*, but passes it on

[issue4280] Version Checker

Changes by Martin v. Löwis <[EMAIL PROTECTED]>: -- nosy: +loewis ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing

[issue4275] socketserver example code not correctly ported to py3k

Brad Miller <[EMAIL PROTECTED]> added the comment: After looking at the socket documentation pointed to from another issue it looks like the right solution is to convert to a byte array. I've attached a patch with fixes for all the examples in socketserver.rst there were several other problems

[issue4281] Idle - incorrectly displaying a character (Latin capital letter sharp s)

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Idle seems indeed to do a hard job to find a font that can display the character. On my machine (WinXP sp3, French) there are many fonts, but only "Myriad Web" can display \N{LATIN CAPITAL LETTER SHARP S}. I was surprised that the "Ch

[issue4118] Built-in compile() and ast module doc issues

Terry J. Reedy <[EMAIL PROTECTED]> added the comment: It appears that blanks on the last line also triggers a syntax error. See #4262. So the situation seems to be that the input must *sometimes* be terminated by . So adding 'sometimes' is the only change I would make, besides restoring th

[issue4262] import and compile() do not treat trailing whitespace the same

Terry J. Reedy <[EMAIL PROTECTED]> added the comment: Both differences are covered in the 2.x docs: "When compiling multi-line statements, two caveats apply: line endings must be represented by a single newline character ('\n'), and the input must be terminated by at least one newline character.

[issue4250] urllib2.py: HTTPResponse instance has no attribute 'code'

Terry J. Reedy <[EMAIL PROTECTED]> added the comment: This appears to be a duplicate of #1507166, with essentially the same title. I found it by searching all issues for "response.code HTTPResponse". That was closed because "The problem came from an external module (urlgrabber) which aparently

[issue4249] HTTPResponse instance has no attribute 'code'

Terry J. Reedy <[EMAIL PROTECTED]> added the comment: You should have edited the title and added a note here instead of opening a new issue to clarify that the problem is in urllib2.py. Anyway, closing this in favor of issue 4250 -- nosy: +tjreedy resolution: -> duplicate status: open

[issue4246] execution model - clear and complete example in documentation

Terry J. Reedy <[EMAIL PROTECTED]> added the comment: Your example seem too verbose and diffuse. Perhaps something more focused on what people do wrong would be more helpful. I presume you mean something like this -- with or without x=2 before the def. >>> def f(): print (x) x

[issue4281] Idle - incorrectly displaying a character (Latin capital letter sharp s)

New submission from Vlastimil Brom <[EMAIL PROTECTED]>: While experimenting with the new unicodedata for version 5.1 (many thanks for it!) I discovered some strange behaviour of Idle with regard to a character not available in any font on my system, namely Latin capital letter sharp s - U+1E9E

[issue4275] socketserver example code not correctly ported to py3k

Brad Miller <[EMAIL PROTECTED]> added the comment: I found a similar problem in the Demo/sockets/unixclient.py code. from socket import * FILE = 'unix-socket' s = socket(AF_UNIX, SOCK_STREAM) s.connect(FILE) s.send('Hello, world') data = s.recv(1024) s.close() print('Received', repr(data)) Pro

[issue4280] Version Checker

New submission from Colin J. Williams <[EMAIL PROTECTED]>: Versions 2.5, 2.6 and 3.0 contain a Version Checker in the Tools directory. This appears to no longer serve a useful purpose. Perhaps it can be dropped from the distribution. Colin W -- components: Tests files: pyversioncheck.

[issue1656675] Drop-Handler for Python files

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: I have now added a drop handler in r67149, r67150, and r67151. However, I chose the wsh handler ({60254CA5-953B-11CF-8C96-00AA00B8708C}) instead of the batch file one, as the wsh handler provides long file names, whereas the batch file handle

[issue4273] cycle created by profile.run

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- nosy: -benjamin.peterson resolution: out of date -> status: closed -> open ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue4273] cycle created by profile.run

darrenr <[EMAIL PROTECTED]> added the comment: Issue also occurs in 2.6. Note that it only shows up if gc is set to save all cycles. -- versions: +Python 2.6 Added file: http://bugs.python.org/file11961/profile_cycle_26.txt ___ Python tracker <[EMAIL

[issue4273] cycle created by profile.run

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Let's mark this as out of date then. -- nosy: +benjamin.peterson resolution: -> out of date status: open -> closed ___ Python tracker <[EMAIL PROTECTED]>

[issue4264] Patch: optimize code to use LIST_APPEND instead of calling list.append

David Turner <[EMAIL PROTECTED]> added the comment: > Obviously if there's another sufficiently good argument for the visitor > approach, I'm all ears. But again, if we do that I think we should do > it for the compiler as well. I'm not sure how much support such a > change would have. The arg

[issue2306] Update What's new in 3.0

STINNER Victor <[EMAIL PROTECTED]> added the comment: "PEP 352: Exceptions must derive from BaseException. This is the root of the exception hierarchy." I prefer to derive from Exception to be able to use "exept Exception as: ..." which doesn't catch SystemExit nor KeyboardInterrupt.

[issue4264] Patch: optimize code to use LIST_APPEND instead of calling list.append

David Turner <[EMAIL PROTECTED]> added the comment: > FWIW, I see exposing bytecodes as an anti-pattern that locks in a > particular implementation in a way that makes it hard to change and > hard to port to other Python implementations. The current bound > method approach works fine. Don't r

[issue4279] Module 'parser' fails to build

Changes by David W. Lambert <[EMAIL PROTECTED]>: -- nosy: +LambertDW ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mai

[issue4273] cycle created by profile.run

Winfried Plappert <[EMAIL PROTECTED]> added the comment: I tested profile_cycle.txt on both Python 2.5.2 and Python 2.6. The cycle you are showing for release 2.4.1 cannot be seen on both releases. Why dont't you try and upgrade to Python 2.6? -- nosy: +wplappert ___

[issue4279] Module 'parser' fails to build

New submission from Andy <[EMAIL PROTECTED]>: With a clean checkout of the py3k source it fails to build the Parser exension module (based on Modules/parsermodule.c) when building against a cygwin target. This appears to be related to the movement of the symbol _PyParser_Grammar from graminit

[issue4236] Crash when importing builtin module during interpreter shutdown

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue2306] Update What's new in 3.0

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3799] Byte/string inconsistencies between different dbm modules

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue4278] optparse quirks

New submission from Keith Briggs <[EMAIL PROTECTED]>: I got the message: optparse.OptionError: invalid long option string '-T0': must start with --, followed by non-dash This is bad - the real error was that I gave a short option which did not have a single letter. Also, it seems that add_opti

[issue4277] asynchat's handle_error inconsistency

Changes by Giampaolo Rodola' <[EMAIL PROTECTED]>: -- versions: +Python 3.0 ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-li

[issue4277] asynchat's handle_error inconsistency

New submission from Giampaolo Rodola' <[EMAIL PROTECTED]>: Suppose you have tow sockets handled by two asynchat.async_chat class instances and from class1 you want to send some data through class2: class1(asynchat.async_chat): ... def mymethod(self): class2_instance.push_wi

[issue4236] Crash when importing builtin module during interpreter shutdown

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Christian, The initial example only works in interactive mode. To make your script crash, you have to set __builtins__._ = Crasher() There are several other places where Crasher() will crash on shutdown: sys.argv.insert(0, Cras

[issue4266] Python 3.0 docs are broken.

Georg Brandl <[EMAIL PROTECTED]> added the comment: Actually, that the build doesn't work is almost OK, because that seealso directive was invalid markup syntax (until very recently) :) Anyway, should be fixed now after a "make update". -- resolution: -> fixed status: open -> closed _