| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
to extern. It's not legal C to say
static whatever[];
because the size isn't given. Presumably this is a gcc extension.
|
|
|
|
|
|
| |
and installed layouts to make maintenance simple and easy. And it
also adds four new codecs; big5hkscs, euc-jis-2004, shift-jis-2004
and iso2022-jp-2004.
|
| |
|
|
|
|
| |
modules and objects.
|
|
|
|
| |
it is used, and made it private. Should fix #978662.
|
| |
|
| |
|
|
|
|
| |
http://mail.python.org/pipermail/python-dev/2004-June/045785.html
|
| |
|
|
|
|
|
| |
docstrings for decode and encode; accidentally were left out of the PyMethodDev
table.
|
|
|
|
| |
compatibility with various broken SSL implementations out there.
|
|
|
|
|
|
|
| |
in Python 2.3.
(It turns out that the Debian unstable packaging of Python 2.3.4 includes this patch.)
Patch by Tino Lange.
|
|
|
|
| |
off #ifndef's.
|
| |
|
|
|
|
| |
any restriction on the return type (like unicode.encode() et al. do).
|
|
|
|
|
|
|
| |
incorrect declaration for ypall_callback in /usr/include/rpcsvc/ypcInt.h .
Shouldn't hurt any code since the differences are unsigned long instead of int and
void * instead of char *. Removes warning about improper function pointer
assignment during compilation.
|
| |
|
| |
|
|
|
|
|
| |
* use assertions instead of tests after internal calls that can't fail.
* expand test coverage
|
|
|
|
| |
[ 987287 ] Python 2.4a1, interpreter hanging on Keyboard Interrupt
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[ 960406 ] unblock signals in threads
although the changes do not correspond exactly to any patch attached to
that report.
Non-main threads no longer have all signals masked.
A different interface to readline is used.
The handling of signals inside calls to PyOS_Readline is now rather
different.
These changes are all a bit scary! Review and cross-platform testing
much appreciated.
|
|
|
|
| |
#984672 by James Lamanna
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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.
|
|
|
|
|
| |
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.
|
|
|
|
| |
places it's just noise.
|
| |
|
|
|
|
|
|
|
| |
--disable-framework build; header file was protected in an #if using the wrong
macro to check.
Closes bug #978645.
|
| |
|
|
|
|
|
|
| |
The LaTeX is untested (well, so is the new API, for that matter).
Note that I also changed NULL to get spelled consistently in concrete.tex.
If that was a wrong thing to do, Fred should yell at me.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
New include file timefuncs.h exports private API function
_PyTime_DoubleToTimet() from timemodule.c. timemodule should export
some other functions too (look for painful bits in datetimemodule.c).
Added insane-argument checking to datetime's assorted fromtimestamp()
and utcfromtimestamp() methods. Added insane-argument tests of these
to test_datetime, and insane-argument tests for ctime(), localtime()
and gmtime() to test_time.
|
|
|
|
|
|
|
|
|
|
|
| |
more than a second of precision. Primarily affects ctime, localtime, and
gmtime.
Closes bug #919012 thanks to Tim Peters' code.
Tim suggests that the new funciton being introduced, _PyTime_DoubletoTimet(),
should be added to the internal C API and then used in datetime where
appropriate. Not being done now for lack of time.
|
| |
|
| |
|
|
|
|
| |
Reads better when the iterable is a generator expression.
|
| |
|
|
|
|
| |
(Contributed by Andrew Gaul.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Beardsley.
If the seconds are different, we still need to calculate the differences
between milliseconds.
Also, on a Gentoo Linux (2.6.5) dual Athlon MP box with glibc 2.3,
time can go backwards. This probably happens when the process switches
the CPU it's running on. Time can also go backwards when running NTP.
If we detect a negative time delta (ie, time went backwards), return
a delta of 0. This prevents an illegal array access elsewhere.
I think it's safest to *not* update prev_timeofday in this case, so we
return without updating.
Backport candidate.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Maxheap version of heapq.smallest() is forthcoming.
|
|
|
|
|
| |
(reported by Thomas Heller). If have_unicode_filename is set,
path looks like it will not be used, so there's no need to free it.
|