| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
it was being used even without threads. This of course might be an
all-platform problem so now we only use the _r variant when we are
using threads.
|
|
|
|
|
| |
Tamito Kajiyama. (This caused a bug only on platforms where malloc(0)
returns NULL.)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Without this, if inflate() returned Z_BUF_ERROR asking for more output
space, we would report the error; now, we increase the buffer size and
try again, just as for Z_OK.
|
| |
|
|
|
|
| |
#else/#endif are wrong, and that #if HAVE_TM_ZONE should be #ifdef.
|
|
|
|
| |
The problem was reported by Moshe Zadka.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"""
The GNU folks, in their infinite wisdom, have decided not to implement
altzone in libc6; this would not be horrible, except that timezone
(which is implemented) includes the current DST setting (i.e. timezone
for Central is 18000 in summer and 21600 in winter). So Python's
timezone and altzone variables aren't set correctly during DST.
Here's a patch relative to 1.5.2b2 that (a) makes timezone and altzone
show the "right" thing on Linux (by using the tm_gmtoff stuff
available in BSD, which is how the GLIBC manual claims things should
be done) and (b) should cope with the southern hemisphere. In pursuit
of (b), I also took the liberty of renaming the "summer" and "winter"
variables to "july" and "jan". This patch should also make certain
time calculations on Linux actually work right (like the tz-aware
functions in the rfc822 module).
(It's hard to find DST that's currently being used in the southern
hemisphere; I tested using Africa/Windhoek.)
"""
|
|
|
|
| |
middlename) Marangozov, patch coded by Greg Stein.
|
|
|
|
|
|
| |
is not an empty string, this means that you have arrived at the
end of the stream of compressed data, and the contents of .unused_data are
whatever follows the compressed stream.
|
|
|
|
| |
Fix comments about zlib version and URL.
|
|
|
|
|
|
|
|
|
|
|
|
| |
data struct before calling gethostby{name,addr}_r(); (2) ignore the
3/5/6 args determinations made by the configure script and switch on
platform identifiers instead:
AIX, OSF have 3 args
Sun, SGI have 5 args
Linux has 6 args
On all other platforms, undef HAVE_GETHOSTBYNAME_R altogether.
|
| |
|
|
|
|
| |
with egcs (after setting EXE=.exe). Patch by Norman Vine.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Use HAVE_GETHOSTBYNAME_R_6_ARG instead of testing for Linux and
glibc2.
- If gethostbyname takes 3 args, undefine HAVE_GETHOSTBYNAME_R --
don't know what code should be used.
- New symbol USE_GETHOSTBYNAME_LOCK defined iff the lock should be used.
- Modify the gethostbyaddr() code to also hold on to the lock until
after it is safe to release, overlapping with the Python lock.
(Note: I think that it could in theory be possible that Python code
executed while gethostbyname_lock is held could attempt to reacquire
the lock -- e.g. in a signal handler or destructor. I will simply say
"don't do that then.")
|
|
|
|
|
|
|
|
| |
Here's a patch to fix the race condition, which wasn't fixed by Rob's
patch. It holds the gethostbyname lock until the results are copied out,
which means that this lock and the Python global lock are held at the same
time. This shouldn't be a problem as long as the gethostbyname lock is
always acquired when the global lock is not held.
|
|
|
|
|
| |
the end of loop was incorrect, and failed when the flushmode != Z_FINISH.
Logic cleaned up and commented.
|
| |
|
|
|
|
|
| |
hyperbolic cosine. Problem report via David Ascher by one of his
students.
|
|
|
|
| |
converntion for gethostbyname_r() etc. than Solaris!
|
|
|
|
|
|
|
|
|
|
| |
He writes:
I had an off-by-1000 error in floatsleep(),
and the problem with time.clock() is that it's not implemented properly
on QNX... ANSI says it's supposed to return _CPU_ time used by the
process, but on QNX it returns the amount of real time used... so I was
confused.
|
| |
|
|
|
|
|
| |
-- someone tried to pass in sys.maxint and got bitten by the bogus
calculations.
|
|
|
|
|
|
|
|
| |
guessing what happened when strftime() returns 0. Is it buffer
overflow or was the result simply 0 bytes long? (This happens for an
empty format string, or when the format string is a single %Z and the
timezone is unknown.) if the buffer is at least 256 times as long as
the format, assume the latter.
|
| |
|
|
|
|
| |
should be in the range [0-59]. Noted by Tadayoshi Funaba.
|
|
|
|
|
|
| |
converted was a "digit" -- use isalnum(). This test is there only to
guard against "+" or "-" being interpreted as a valid int literal.
Reported by Takahiro Nakayama.
|
|
|
|
| |
actual code does not allow such an argument. (Finn Bock.)
|
|
|
|
| |
PyInt_Check(), use PyInt_AS_LONG() instead (two places).
|
| |
|
|
|
|
| |
underscore after all, for consistency with the O_* symnbols.
|
|
|
|
| |
os.times().
|
|
|
|
|
|
| |
was just an alias for PyExc_OSError and the way we were doing it was
causing a (small) memory leak anyway. Just use PyExc_OSError
everywhere.
|
|
|
|
|
|
| |
up the _tkinter main loop. Not clear why; the _kbhit() call _tkinter
makes probably confuses the stdio library when buffering isn't set to
whatever it is by default.
|
|
|
|
| |
wrong variable.
|
|
|
|
| |
The test code is now accessed as a package.
|
|
|
|
|
|
| |
(including a docstring saying "blah"). Fixed all this.
(Please review for potential memory leaks!)
|
| |
|
|
|
|
|
|
| |
f_fsid field, since it's not a scalar on all systems supporting this
call (in particular, it's a tuple of two longs on AIX). Since it's
not particularly useful, just nuke it. Adapted the doc strings too.
|
|
|
|
|
| |
and besides Toby Dickenson sent me a more functional
(if lower level) wrapper around PlaySound.
|
|
|
|
| |
a process exit status as a parameter.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
was appended to a list. Lists are reference count neutral, so the
string must be DECREF'd. Also added some checks for the return value
of PyList_Append().
Note: there are still some memory problems reported by Purify (I get
two Array Bounds Reads still and an Unitialized Memory Read). Also,
in scanning the code, there appears to be some potential problems
where return values aren't checked. To much to attack now though.
|
|
|
|
| |
this doesn't exist everywhere, so go back to using #ifdef NeXT.
|