- 05 Mar, 2002 4 commits
-
-
Andreas Jung authored
-
Andreas Jung authored
-
Andreas Jung authored
- minor code cleanup (striping of unused spaces)
-
Andreas Jung authored
-
- 04 Mar, 2002 9 commits
-
-
Evan Simpson authored
-
Andreas Jung authored
-
Andreas Jung authored
-
Andreas Jung authored
-
Andreas Jung authored
-
Andreas Jung authored
-
Andreas Jung authored
-
Andreas Jung authored
the Julian day and the week in the current year based on the Julian calendar.
-
Andreas Jung authored
files during installation. Fixed.
-
- 01 Mar, 2002 4 commits
-
-
matt@zope.com authored
wrapped objects (caching wrapped objects being a bad thing)
-
matt@zope.com authored
-
matt@zope.com authored
-
Andreas Jung authored
support for reading gzipped detailed logfiles
-
- 28 Feb, 2002 10 commits
-
-
Fred Drake authored
in all cases; provide a version that is not magical if we are not in Zope. Tested with Python 2.1.1 and 2.2.1 (CVS).
-
Amos Latteier authored
-
Evan Simpson authored
-
Andreas Jung authored
-
Shane Hathaway authored
-
Andreas Jung authored
-
Andreas Jung authored
-
Andreas Jung authored
-
Andreas Jung authored
unicode support for the GlobbingLexicon
-
Andreas Jung authored
-
- 27 Feb, 2002 2 commits
-
-
Evan Simpson authored
-
Fred Drake authored
module. My *hope* is that this takes care of the single deprecation warning produced when running the regression tests on the trunk with Python 2.2.
-
- 26 Feb, 2002 3 commits
-
-
Fred Drake authored
Shane, I'm going to beg you to help me get my test setup cleaned up tomorrow!
-
Barry Warsaw authored
original checkin message: DateTime.__init__() and DateTime.__str__(): When a fractional number of seconds is passed in or derived, round it to the nearest millisecond. Also changed str() to produce no more than three digits after the second's decimal point (if any). This ensures that DateTime->string->DateTime loses no information. Before this change, platform rounding errors in float<->string conversion could lose information in both conversion steps, so a DateTime object converted to string and back again didn't always reproduce the input object's value. That's bad on its own, and testDateTime.py's testConstructor3() failed about 1% of the time on Linux as a result. It doesn't fail after this patch. CAUTION: Note that DateTime objects have at finest millisecond resolution now, even if the platform time.time() happens to have resolution finer than that. Note that he also had to fiddle with the function that returned system time, so he's got a wrapper around time.time() that rounds to 3 places the float returned by system time. All the testing I've done indicates that this intermittent fixes the comparison failures.
-
Fred Drake authored
-
- 25 Feb, 2002 5 commits
-
-
Amos Latteier authored
-
Evan Simpson authored
-
Evan Simpson authored
-
Andreas Jung authored
as text to be represented as underline. - updated tests and HTML references
-
Andreas Jung authored
-
- 22 Feb, 2002 1 commit
-
-
Fred Drake authored
Python 2.2.
-
- 21 Feb, 2002 2 commits
-
-
Andreas Jung authored
-
Andreas Jung authored
changed --today option to use localtime() instead of gmtime() (BigM logs are written using localtime())
-