[issue9539] python-2.6.4: test failure in test_distutils due to linking to system libpython2.6

Sandro Tosi added the comment: Hello, on an up-to-date 2.7 I can't replicate this bug: $ ./python Lib/test/regrtest.py test_distutils test_distutils 1 test OK. Is it just me or is been fixed already? -- nosy: +sandro.tosi versions: -Python 2.6 ___

[issue8863] Display Python backtrace on SIGSEGV, SIGFPE and fatal error

STINNER Victor added the comment: Version 6: - don't use fputc(), fputs(), fprintf() or fflush() on stderr: use write() on file descriptor 2 (should be stderr) - write tests: add sigsegv(), sigfpe() and fatal_error() functions to the _testcapi module I was too lazy to reimplement functions

[issue8863] Display Python backtrace on SIGSEGV, SIGFPE and fatal error

STINNER Victor added the comment: TODO (maybe): Call the original signal handler to make tools like apport or ABRT able to catch segmentation faults. > By the way, don't you want to handle SIGILL and SIGBUS too? Maybe. SIGILL is a very rare exception. To test it, should I send a SIGILL signa

[issue8863] Display Python backtrace on SIGSEGV, SIGFPE and fatal error

Dave Malcolm added the comment: > About SIGBUS: I don't know this signal. Is it used on Linux? If not, on > which OS is it used? Yes, IIRC typically you'll only see it on RISC CPUs that require instructions to be word-aligned; you typically see it if the program counter jumps to a broken addr

[issue7287] import hook demo does not work

Benjamin Peterson added the comment: See r85429. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bug

[issue7287] import hook demo does not work

Benjamin Peterson added the comment: 2010/10/13 Sandro Tosi : > > Sandro Tosi added the comment: > > Hi Benjamin, > you are the author of r63966 (I know, it's quite old, sorry about that) where > you removed Demo/imputil/importers.py : do you think Demo/imputil/knee.py is > still something in

[issue9992] Command-line arguments are not correctly decoded if locale and fileystem encodings are different

STINNER Victor added the comment: I commited issue9992.patch as r85430 (remove PYTHONFSENCODING) + r85435 (OSX: decode command line arguments from utf-8). These commits should fix this issue. Reopen the issue if you notice new problems, or if the problem is not fixed yet. I will watch Mac OS

[issue10039] python é.py fails with UnicodeEncodeErr or if PYTHONFSENCODING is used

STINNER Victor added the comment: Fixed by r85430 (remove PYTHONFSENCODING), see #9992. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue10093] Warn when files are not explicitly closed

Jean-Paul Calderone added the comment: If the warnings are emitted as usual with the warnings module, you can use -W to control this. -X isn't necessary. -- nosy: +exarkun ___ Python tracker

[issue10014] sys.path[0] is incorrect if PYTHONFSENCODING is used

STINNER Victor added the comment: Fixed by r85430 (remove PYTHONFSENCODING), see #9992. -- resolution: -> fixed ___ Python tracker ___ _

[issue9988] test_warnings fails with PYTHONFSENCODING=latin-1 on UNIX/BSD

STINNER Victor added the comment: Fixed by r85430 (remove PYTHONFSENCODING), see #9992. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue4388] test_cmd_line fails on MacOS X

STINNER Victor added the comment: This issue should be fixed by r85435 (OSX: decode command line arguments from utf-8), see #9992. I will watch for the OSX buildbots. -- ___ Python tracker ___

[issue10014] sys.path[0] is incorrect if PYTHONFSENCODING is used

Changes by STINNER Victor : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue10094] test_urllib.py fails in py3k r85440 with RuntimeError

New submission from Barry A. Warsaw : Running the test suite on py3k r85440, I get the following failure: == ERROR: test_getproxies_environment_keep_no_proxies (__main__.ProxyTests) -

[issue10049] Add a "no-op" (null) context manager to contextlib

Nick Coghlan added the comment: To me, this is more a matter of conceptual completeness than one of practical utility (ala fractions.Fraction). That said, I *have* personally encountered the "I only sometimes want to wrap this code in a CM" situation, so it isn't completely impractical, eithe

[issue9005] Year range in timetuple

Alexander Belopolsky added the comment: Committed in r85441. -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mai

[issue4388] test_cmd_line fails on MacOS X

STINNER Victor added the comment: > This issue should be fixed by r85435 ... > I will watch for the OSX buildbots. I don't know if it fixes the issue, but it introduces a regression. r85442 reverts it. --- Revert r85435 (and r85440): decode command line arguments from utf-8 Python exits wi

[issue9377] socket, PEP 383: Mishandling of non-ASCII bytes in host/domain names

David Watson added the comment: > platform.system() fails with UnicodeEncodeError on systems that have their > computer name set to a name containing non-ascii characters. The > implementation of platform.system() uses at some point socket.gethostname() ( > see http://www.pasteall.org/16215 f

[issue4388] test_cmd_line fails on MacOS X

STINNER Victor added the comment: osx_utf8_cmdline.patch: copy of r85435. -- Added file: http://bugs.python.org/file19228/osx_utf8_cmdline.patch ___ Python tracker ___ __

[issue10095] Support undecodable filenames in the parser API

New submission from STINNER Victor : It looks like the parser API (eg. PyParser_ParseFileFlagsEx, PyParser_ASTFromFile) expects utf-8 filename: err_input() decodes the filename from utf-8. But Example in a non-ascii directory (/home/SHARE/SVN/py3kéŁ) and an ascii locale: $ LANG= ./python

[issue10093] Warn when files are not explicitly closed

Antoine Pitrou added the comment: > If the warnings are emitted as usual with the warnings module, you can > use -W to control this. Right. Perhaps we can add a new warning category (e.g. ResourceWarning), or simply reuse RuntimeWarning. -- ___ Py

[issue10093] Warn when files are not explicitly closed

Changes by Brian Curtin : -- nosy: +brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue10093] Warn when files are not explicitly closed

Benjamin Peterson added the comment: +1 for RuntimeError. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue9992] Command-line arguments are not correctly decoded if locale and fileystem encodings are different

STINNER Victor added the comment: test_undecodable_env() of test_subprocess fails. r85430 removes the following code which was added by Antoine to fix this issue. # Force surrogate-escaping of \xFF in the child process; # otherwise it can be decoded as-is if the default locale # is latin-1. en

[issue10093] Warn when files are not explicitly closed

Alex added the comment: RuntimeWarning you mean? I don't think anyone is suggesting making it an error. -- nosy: +alex ___ Python tracker ___ __

[issue10093] Warn when files are not explicitly closed

Benjamin Peterson added the comment: 2010/10/13 Alex : > > Alex added the comment: > > RuntimeWarning you mean?  I don't think anyone is suggesting making it an > error. Indeed. -- ___ Python tracker __

[issue7944] Use the 'with' statement in conjunction with 'open' throughout test modules

Brian Curtin added the comment: Backported test_gzip to to release27-maint in r85446. Backported test_mailbox to to release27-maint in r85447. Backported test_bz2 to to release27-maint in r85448. Fixed test_old_mailbox, the original problem file, in release27-maint in r85449. -- _

[issue3482] re.split, re.sub and re.subn should support flags

Matt Keeler added the comment: Python 2.7 docs say this was added in 2.7.3.1 Python 3.1 docs say this was added in 3.1 The problem with calling 're.split(pattern, string, re.I)' is that you are using positional arguments only. If you were to do 're.split(pattern, string, flags=re.I)', that s

[issue10096] Question regarding python migration

New submission from Pramod T Sridhar : Hi All, We have a Python based test framework which is being used in various projects. Our current environment is Python (ver 2.5.1) wxPython (wxPython2.8-win32-ansi-2.8.6.0-py25) pywin32-210.win32-py2.5 vcredist_x86.exe pyserial-2.2 Our Framework is bei

[issue10079] idlelib for Python 3 with Guilherme Polo GSoC enhancements

Ned Deily added the comment: Thanks for creating the patch. Since it is a feature, it would be considered to be applied to the current py3k branch (which at the moment is what will be going into the 3.2 release) rather than 3.1 which is generally only accepting bug fixes. By the way, since

[issue10096] Question regarding python migration

Senthil Kumaran added the comment: Please ask python-l...@python.org Bug tracker is for raising bugs on python. -- nosy: +orsenthil resolution: -> invalid stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue10097] platform.uname gives UnicodeError for non-ASCII computer names on Windows

New submission from Martin v. Löwis : Reportedly, platform.uname gives UnicodeError for non-ASCII computer names on Windows, see http://www.pasteall.org/16215 I think it is incorrect that _node uses socket.gethostname on Windows. uname() should return the local hostname (i.e. the one that the

[issue10049] Add a "no-op" (null) context manager to contextlib

Georg Brandl added the comment: I like your latest suggestion, except for the name. Given that we also have the (quite generic) "closing", what about just "optional"? -- nosy: +georg.brandl ___ Python tracker __

[issue9377] socket, PEP 383: Mishandling of non-ASCII bytes in host/domain names

Martin v. Löwis added the comment: The failure of platform.uname is an independent bug. IMO, it shouldn't use socket.gethostname on Windows, but instead look at the COMPUTERNAME environment variable or call the GetComputerName API function. This is more close to what uname() does on Unix (i.e

[issue10079] idlelib for Python 3 with Guilherme Polo GSoC enhancements

Bruce Sherwood added the comment: Thanks for catching the missing utils.py file. I can explain the missing/commented statement in IOBinding.py. I found experimentally that if that statement is present, when you open a file on Windows the first line is off the top of the display, which can be

[issue4388] test_cmd_line fails on MacOS X

Martin v. Löwis added the comment: One solution would be to duplicate the UTF-8 decoder for OSX, incorporating surrogate escape. This should be much shorter than the full UTF-8 codec, and perhaps at least utf8_code_length could be shared. -- ___ Py

[issue7642] Minor improvement to os.system doc

Georg Brandl added the comment: Unfortunately, the rewrap makes it much more complicated to see what the patch changes (i.e. the whole second part of the hunk only adds Windows versions). Please leave that to the committer in the future. Otherwise, committed in r85450; I also removed mentio

[issue3865] explain that profilers should be used for profiling, not benchmarking

Georg Brandl added the comment: Freshed up and committed in r85451. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue10046] Correction to atexit documentation

Georg Brandl added the comment: Fixed in r85452. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bu

[issue7642] Minor improvement to os.system doc

Sandro Tosi added the comment: On Thu, Oct 14, 2010 at 08:36, Georg Brandl wrote: > > Georg Brandl added the comment: > > Unfortunately, the rewrap makes it much more complicated to see what  the > patch changes (i.e. the whole second part of the hunk only adds Windows > versions).  Please l

<    1   2