This change also makes sure the logger handlers are not alterated after an
installation. That also fixes the remaining environment alteration issue in
test_packaging.
DATA_CRLF was used to test BZ2File's universal newline logic, which was removed
in changeset ce63a5dcb0af. The tests themselves were removed in fbabdb0d7dd2.
* In bz2.decompress(), concatenate partial results in a way that should
be more friendly to other Python implementations
* Remove redundant comments in test_bz2
* Use 'while True:' instead of 'while 1:'
changeset: 70465:4f248dd34dd9
branch: 3.2
parent: 70463:7f2e3c466d57
user: Gregory P. Smith <greg@krypto.org>
date: Sat May 28 09:06:02 2011 -0700
files: Lib/test/test_subprocess.py
description:
Fix ProcessTestCasePOSIXPurePython to test the module from import when
changeset: 70466:2c91045d16a6
parent: 70464:2936e8f12e4f
user: Gregory P. Smith <greg@krypto.org>
date: Sat May 28 09:06:02 2011 -0700
files: Lib/test/test_subprocess.py
description:
Fix ProcessTestCasePOSIXPurePython to test the module from import when
The tests now pass all combinations of -O/-OO and -B. See also #7071
and #6292 for previous variations on the same theme.
test_versionpredicate needs a skip when sys.flags.optimize is true, but
I don’t know how to make that work with a DocTestSuite.
Remove the pure Python POSIX subprocess implementation.
If non-CPython VMs (are there any for 3.x yet?) were somehow depending
on this, they already have the exact same set of problems with Python
code being executed after os.fork() that _posixsubprocess was written
to deal with. They should implement an equivalent outside of Python.
_posixsubprocess doesn't exist rather than simply stubbing it out
after the fact. This adds coverage for the RuntimeWarning as well as
using the pure python _create_pipe instead of using
_posixsubprocess.cloexec_pipe unintentionally with the pure python
code.
Ironically: I don't think any platform should ever actually _use_ the
pure Python subprocess code on POSIX platforms anymore. This at least
tests it properly in this stable branch. The pure python code for
this is likely to be removed in 3.3.
_posixsubprocess doesn't exist rather than simply stubbing it out
after the fact. This adds coverage for the RuntimeWarning as well as
using the pure python _create_pipe instead of using
_posixsubprocess.cloexec_pipe unintentionally with the pure python
code.
Ironically: I don't think any platform should ever actually _use_ the
pure Python subprocess code on POSIX platforms anymore. This at least
tests it properly in this stable branch. The pure python code for
this is likely to be removed in 3.3.
Tarek Ziade
Nadeem Vawda
Ned Deily
Benjamin Peterson
Charles-François Natali
Éric Araujo
Martin v. Löwis
Gregory P. Smith