- 14 Dec, 2009 2 commits
-
-
R. David Murray authored
any errors that might occur during coercion of the left operand and turning them into a TypeError with a message text that was confusing in the given context. This patch lets any errors through, as was already done during coercion of the right hand side.
-
R. David Murray authored
-
- 13 Dec, 2009 15 commits
-
-
Tarek Ziadé authored
reorganized the distutils doc a bit : the MANIFEST.in template system has its own section now. This is easier to find and follow
-
Benjamin Peterson authored
-
Benjamin Peterson authored
-
Benjamin Peterson authored
-
Mark Dickinson authored
sem_unlink calls to delete those semaphore files.
-
Benjamin Peterson authored
-
Benjamin Peterson authored
This is for consistency with imitation file objects like StringIO and BytesIO. This commit also adds a few tests, where they were lacking for concerned methods.
-
Ezio Melotti authored
-
Benjamin Peterson authored
-
Benjamin Peterson authored
-
Benjamin Peterson authored
-
Antoine Pitrou authored
in 2.7 alpha 1)
-
Benjamin Peterson authored
-
Lars Gustäbel authored
default. TarFile's errorlevel argument controls how errors are handled that occur during extraction. There are three possible levels 0, 1 and 2. If errorlevel is set to 1 or 2 fatal errors (e.g. a full filesystem) are raised as exceptions. If it is set to 0, which is the default value, extraction errors are suppressed, and error messages are written to the debug log instead. But, if the debug log is not activated, which is the default as well, all these errors go unnoticed. The original intention was to imitate GNU tar which tries to extract as many members as possible instead of stopping on the first error. It turns out that this is no good default behaviour for a tar library. This patch simply changes the default value for the errorlevel argument from 0 to 1, so that fatal extraction errors are raised as EnvironmentError exceptions.
-
Benjamin Peterson authored
-
- 12 Dec, 2009 1 commit
-
-
Antoine Pitrou authored
in the middle of populating a tuple. Patch by Florent Xicluna. (note: no NEWS entry for trunk since the bug was introduced in 2.7/3.1)
-
- 11 Dec, 2009 2 commits
-
-
Mark Dickinson authored
-
Vinay Sajip authored
-
- 10 Dec, 2009 7 commits
-
-
Tarek Ziadé authored
-
Tarek Ziadé authored
-
Mark Dickinson authored
equivalent[*] check that doesn't produce compiler warnings about a 'x < 0' check on an unsigned type. [*] it's equivalent for inputs of type size_t or Py_ssize_t, or any smaller unsigned or signed integer type.
-
Ronald Oussoren authored
on OSX. Without this patch it wasn't possible after all to compile extensions on OSX 10.6 with the binary installer unless the user had installed the (non-default) 10.4u SDK.
-
Raymond Hettinger authored
-
Raymond Hettinger authored
-
Benjamin Peterson authored
-
- 09 Dec, 2009 2 commits
-
-
R. David Murray authored
-
R. David Murray authored
missing proper end-of-line termination. Patch and tests by Scott Dial. The new tests include a test harness which will make it easier to add additional tests.
-
- 08 Dec, 2009 8 commits
-
-
Antoine Pitrou authored
-
Antoine Pitrou authored
-
Antoine Pitrou authored
Diagnosis and original patch by Florent Xicluna (flox).
-
Ronald Oussoren authored
an i386 based machine, but should only be active when compiling the x86 part of the universal binary.
-
Antoine Pitrou authored
wrong parameter types. Patch by Victor Stinner.
-
Tarek Ziadé authored
-
Tarek Ziadé authored
Issue #7457: added a read_pkg_file method to distutils.dist.DistributionMetadata so we can read back PKG-INFO files
-
Andrew M. Kuchling authored
-
- 06 Dec, 2009 3 commits
-
-
Benjamin Peterson authored
-
Martin v. Löwis authored
-
Vinay Sajip authored
-