| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- weakref.ref and weakref.ReferenceType will become aliases for each
other
- weakref.ref will be a modern, new-style class with proper __new__
and __init__ methods
- weakref.WeakValueDictionary will have a lighter memory footprint,
using a new weakref.ref subclass to associate the key with the
value, allowing us to have only a single object of overhead for each
dictionary entry (currently, there are 3 objects of overhead per
entry: a weakref to the value, a weakref to the dictionary, and a
function object used as a weakref callback; the weakref to the
dictionary could be avoided without this change)
- a new macro, PyWeakref_CheckRefExact(), will be added
- PyWeakref_CheckRef() will check for subclasses of weakref.ref
This closes SF patch #983019.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
table' of the dll, to make sure that the dll really was build for the
correct Python version. It does this by looking for an entry
'pythonXY.dll' (X.Y is the Python version number).
The code now checks the size of the dll's import table before reading
entries from it. Before this patch, the code crashed trying to read
the import table when the size was zero (as in Win2k's wmi.dll, for
example).
Look for imports of 'pythonXY_d.dll' in a debug build instead of
'pythonXY.dll'.
Fixes SF 951851: Crash when reading "import table" of certain windows dlls.
Already backported to the 2.3 branch.
|
|
|
|
|
|
|
| |
Patch from Mark Hammond.
Recompiled binary.
Already packported to the 2.3 branch.
|
|
|
|
|
|
| |
The builtin eval() function now accepts any mapping for the locals argument.
Time sensitive steps guarded by PyDict_CheckExact() to keep from slowing
down the normal case. My timings so no measurable impact.
|
| |
|
|
|
|
|
|
|
|
| |
char *`` instead of just ``char *``. Also added the mentioning of "const" in
some places where it was left out even when the signature already stated the
fact.
Closes bug #980925.
|
|
|
|
| |
test_repr() fails with id() values that appear negative
|
|
|
|
|
|
| |
instead of ValueError.
Add a note about error handling schemes added by PEP 293.
|
| |
|
|
|
|
|
|
|
|
| |
[ 924301 ] A leak case with cmd.py & readline & exception
by ensuring that the readline completion function is always reset
even in the case of an exception being raised. As a bonus, this
makes the documentation for pre & postloop accurate again.
|
| |
|
| |
|
|
|
|
|
| |
* Format an example so that the identation is more obvious.
* Add a section on the decimal module to the Brief Tour Part II.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
on the marshalling characteristics of infinities.
|
|
|
|
| |
end-of-options marker wasn't recognized
|
| |
|
|
|
|
|
| |
(I ran this through texcheck, but don't have LaTeX installed on this machine and therefore haven't
verified that the changes are accepted by LaTeX.)
|
| |
|
|
|
|
|
|
| |
legal if a Range: header was supplied.
(Actually, should the first 'if' statement be modified to allow any 2xx status code?)
|
|
|
|
| |
have been commented.)
|
| |
|
| |
|
| |
|
|
|
|
| |
entailed editing the urlparse module.
|
|
|
|
|
|
| |
location) in its addressing.
Closes bug #981299.
|
|
|
|
|
|
|
|
|
| |
PyArg_ParseTuple() to ``const char *`` to match the recommendation made in
section 1.3 and to support better coding habits.
Section 1.8 ("Keyword Parameters for Extension Functions") and it's coding
example were not touched since it is stems from an accredited source and thus
did not want to step on anyone's toes.
|
| |
|
|
|
|
| |
Now runs without exception on WinME/98.
|
|
|
|
|
| |
Based on a patch supplied by Ian Ward <ian@arevco.ca> on the pybsddb
mailing list 2004-03-26.
|
|
|
|
|
| |
Make DBTxn objects automatically call abort() in their destructor if
not yet finalized and raise a RuntimeWarning to that effect.
|
|
|
|
| |
getservbyname() optional. Update the tests and the docs.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix memory leaks revealed by valgrind and ensuing code inspection.
In the existing test suite valgrind revealed two memory leaks (DB_get
and DBC_set_range). Code inspection revealed that there were many other
potential similar leaks (many on odd code error paths such as passing
something other than a DBTxn object for a txn= parameter or in the face
of an out of memory error). The most common case that would cause a
leak was when using recno or queue format databases with integer keys,
sometimes only with an exception exit.
|
|
|
|
|
|
|
|
|
| |
Cleaned up existing code by abstracting code to parse arguments. Also removed
any unneeded operations (such as calling 'int' on a division when using floor
division also works). Fixed a bug where the values returned by
OldStyleRange could be short by one value. Added more documentation.
Testing code also has a basic sanity check.
|
|
|
|
|
|
| |
opening the DB to implement legacy interface flag='n' support as
BerkeleyDB 4.2.52 no longer allows it in transaction protected
environments. Do the os.unlink ourselves.
|
|
|
|
| |
places it's just noise.
|
| |
|
| |
|
|
|
|
| |
return Py_None.
|
|
|
|
|
|
|
|
|
|
| |
regrtest.py after it ran test_frozen. This test was really only
designed to be run immediately after startup. Afterwards, other
modules could be loaded when had not been fixed-up by site.py
Took the chicken way out and only tested those modules known to
be imported by site.py.
* Normalized whitespace.
|
| |
|