| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
a Py_BEGIN_ALLOW_THREADS/Py_END_ALLOW_THREADS block, but it
calls Py_BLOCK_THREADS anyway. The change moves Py_BLOCK_THREADS
to inside the if, so it's only executed when the function
actually returns unexpectedly.
|
|
|
|
| |
Also, wrap long line.
|
|
|
|
| |
PyArg_ParseTuple() format string arguments as possible.
|
|
|
|
|
|
| |
only. Through some mysterious interaction, they would take 9 separate
arguments as well. This misfeature is now disabled (to end a
difference with JPython).
|
| |
|
| |
|
|
|
|
|
|
|
| |
The test really wanted to distinguish between the two. So now we test
for __GLIBC__ instead. I have confirmed that this works for glibc and
I have an email from Christian Tanzer confirming that it works for
libc5, so it should be fine.
|
|
|
|
| |
#else/#endif are wrong, and that #if HAVE_TM_ZONE should be #ifdef.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"""
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.)
"""
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
comes first, the format second! Scott Cotton discovered this.
|
|
|
|
|
| |
conflict, and it should be declared in time.h anyway.
(Too bad if gcc -Wall won't be happy if it isn't declared...)
|
|
|
|
| |
on BeOS or Windows.
|
|
|
|
|
| |
(1) add dummy decl for strptime();
(2) move the code to set accept2dyear to the front of inittime().
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
2-digit years are now converted using rules that are (according to
Fredrik Lundh) recommended by POSIX or X/Open: 0-68 mean 2000-2068,
69-99 mean 1969-1999.
2-digit years are now only accepted if time.accept2dyear is set to a
nonzero integer; if it is zero or not an integer or absent, only year
values >= 1900 are accepted. Year values 100-1899 and negative year
values are never accepted.
The initial value of time.accept2dyear depends on the environment
variable PYTHONY2K: if PYTHONY2K is set and non-empty,
time.accept2dyear is initialized to 0; if PYTHONY2K is empty or not
set, time.accept2dyear is initialized to 0.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
effects, simply zero out the struct tm buffer before using it; this
should take care of the BSD folks' concern just as well.
|
|
|
|
| |
at least the build will now succeed). For Sony NEWS-OS, BSD 4.3 based.
|
|
|
|
| |
instead of dumping core.
|
|
|
|
| |
DosSleep().
|
|
|
|
|
|
| |
may set the timezone name for BSD systems...
(2) fake all of the timezone variables for the mac.
|
| |
|
| |
|
|
|
|
|
|
| |
to inside floatsleep(). This is necessary because floatsleep() does
the error handling and it must have grabbed the interpreter lock and
thread state before it can do so.
|
| |
|
| |
|
|
|
|
| |
Run the loop up to and including 8k.
|
| |
|
|
|
|
|
| |
a conflicting definition somewhere).
Resolved line wrap for error message in ins().
|
|
|
|
|
|
| |
PyDict_SetItemString.
GvR: note the long line > 80 chars. Wrapping suggestions?
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The timezone etc. overrides are win16 specific.
Hope I got this right now...
|
| |
|
| |
|
|
|
|
|
| |
Add mktime() overflow test and make it NeXT robust by initializing
the structure from localtime().
|
| |
|
| |
|
| |
|
| |
|
| |
|