| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Closes bug #796149 . Will be backported.
|
|
|
|
| |
database environments to use shared memory on systems supporting it.
|
|
|
|
|
| |
Make sure the inner function is not compiled when there is a syntax
error in the default arguments.
|
|
|
|
| |
Bug fix candidate.
|
|
|
|
| |
Will backport to 2.3 myself.
|
| |
|
| |
|
|
|
|
|
|
| |
Adding missing support for '%F'.
Will backport to 2.3.1.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
platforms (e.g., Cygwin) that are "particular" about open files, this will
cause other regression tests that use the same temp file to fail:
$ ./python.exe -E -tt Lib/test/regrtest.py -l
test_largefile test_mmap test_mutants
test_largefile
test test_largefile failed -- got -1794967295L, but expected 2500000001L
test_mmap
test test_mmap crashed -- exceptions.IOError: [Errno 13] Permission denied: '@test'
test_mutants
test test_mutants crashed -- exceptions.IOError: [Errno 13] Permission denied: '@test'
This patch solves the problem by adding missing "try/finally" blocks. Note
that the "large" size of this patch is due to many white space changes --
otherwise, the patch is small.
I tested this patch under Red Hat Linux 8.0 too.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The -- is special to TeX and was printing as just -.
|
|
|
|
| |
Thou shalt not count to two unless proceeding to the number three.
|
| |
|
|
|
|
| |
Python 1.5.2 wrong in the section on config files.
|
| |
|
|
|
|
|
| |
I have a different WISE version, and it's installed in a different directory.
My sytem directory is somewhere else.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
test_rfc2231_no_language_or_charset_in_boundary(),
test_rfc2231_no_language_or_charset_in_charset(): New tests for proper
decoding of some RFC 2231 headers.
Backport candidate (as was the Utils.py 1.25 change) to both Python
2.3.1 and 2.2.4 -- will do momentarily.
|
|
|
|
|
|
|
|
|
|
| |
can be None, and what to do in that situation.
get_filename(), get_boundary(), get_content_charset(): Make sure these
handle RFC 2231 headers without a CHARSET field.
Backport candidate (as was the Utils.py 1.25 change) to both Python
2.3.1 and 2.2.4 -- will do momentarily.
|
|
|
|
|
|
| |
charset and language fields are not present, e.g. as in:
title*0="This%20is%20encoded"
|
|
|
|
|
|
|
| |
which is a disaster on Windows. Restored the binary default of all
previous releases. Also minor code cleanups.
Bugfix candidate!
|
|
|
|
|
|
| |
NULL pointer. (Detected by Michael Hudson, patch provided by Neal Norwitz).
Fix refcounting leak in filtertuple().
|
|
|
|
| |
Will backport to release23-maint.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Relaxed the argument restrictions for non-operator methods. They now
allow any iterable instead of requiring a set. This makes the module
a little easier to use and paves the way for an efficient C
implementation which can take better advantage of iterable arguments
while screening out immutables.
* Deprecated Set.update() because it now duplicates Set.union_update()
* Adapted the tests and docs to include the above changes.
* Added more test coverage including testing identities and checking
to make sure non-restartable generators work as arguments.
Will backport to Py2.3.1 so that the interface remains consistent
across versions. The deprecation of update() will be changed to
a FutureWarning.
|
|
|
|
| |
throughout the documentation.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Positive wording for the description of why < and > and = can all
be False.
* Move to a three column table format that puts long method names
side-by-side with their operator equivalents
* Mention that KeyError can be raised by Set.pop() and Set.remove().
* Minor tweaks to the examples.
Will backport as soon as Fred rebuilds the docs so I can confirm
the tables formatted properly
|
| |
|
|
|
|
| |
If opening a directory, the exception would leak.
|
|
|
|
|
|
| |
unchanged (and sys.gettotalrefcount() remains constant).
Fix a few typos.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
[ 784825 ] fix obscure crash in descriptor handling
Should be applied to release23-maint and in all likelyhood
release22-maint, too.
Certainly doesn't apply to release21-maint.
|
| |
|
|
|
|
|
|
| |
Fix, by not using n at all in that case.
Needs to be applied to release23-maint, too.
|
|
|
|
|
|
| |
number. This accounts for the 2 refcount leaks per test_complex run
Michael Hudson discovered (I figured only I would have the stomach to
look for leaks in floating-point code <wink>).
|
|
|
|
| |
usually preferred.
|
|
|
|
|
| |
When parsing the constructor arguments failed, a
reference to the argument tuple was leaked.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
when an encoding error occurs and the callback name is unknown,
i.e. when the callback has to be called. The problem was that
the fact that the callback has already been looked up was only
recorded in a local variable in charmap_encoding_error(), because
charmap_encoding_error() got it's own copy of the errorHandler
pointer instead of a pointer to the pointer in
PyUnicode_EncodeCharmap().
|
|
|
|
| |
(Contributed by George Yoshida.)
|
|
|
|
|
|
| |
Check for a[:] = a _before_ calling PySequence_Fast on a.
release23-maint candidate
Reference leak doesn't happen with head of release22-maint.
|
|
|
|
|
| |
the output was consumed would cause and exception to be raise in
logmerge; suppress this specific error, because it's not helpful.
|