1. 24 Dec, 2002 10 commits
  2. 23 Dec, 2002 22 commits
  3. 22 Dec, 2002 5 commits
    • Tim Peters's avatar
      I give up: unless I write my own strftime by hand, datetime just can't · d6844155
      Tim Peters authored
      be trusted with years before 1900, so now we raise ValueError if a date or
      datetime or datetimetz .strftime() method is called with a year before
      1900.
      d6844155
    • Tim Peters's avatar
      Python's strftime implementation does strange things with the year, · 83b85f1d
      Tim Peters authored
      such that the datetime tests failed if the envar PYTHON2K was set.
      This is an utter mess, and the datetime module's strftime functions
      inherit it.  I suspect that, regardless of the PYTHON2K setting, and
      regardless of platform limitations, the datetime strftime wrappers
      will end up delivering nonsense results (or bogus exceptions) for
      any year before 1900.  I should probably just refuse to accept years
      earlier than that -- else we'll have to implement strftime() by hand.
      83b85f1d
    • Tim Peters's avatar
      classify_object(): Renamed more meaningfully, to classify_utcoffset(). · 14b69411
      Tim Peters authored
      Also changed logic so that instances of user-defined subclasses of date,
      time, and datetime are called OFFSET_NAIVE instead of OFFSET_UNKNOWN.
      14b69411
    • Tim Peters's avatar
      Implemented a Wiki suggestion: · 855fe88b
      Tim Peters authored
      {timetz,datetimetz}.{utcoffset,dst}() now return a timedelta (or None)
      instead of an int (or None).
      
      tzinfo.{utcoffset,dst)() can now return a timedelta (or an int, or None).
      
      Curiously, this was much easier to do in the C implementation than in the
      Python implementation (which lives in the Zope3 code tree) -- the C code
      already had lots of hair to extract C ints from offset objects, and used
      C ints internally.
      855fe88b
    • Kurt B. Kaiser's avatar
      Add configuration for packaging. · 18091540
      Kurt B. Kaiser authored
      18091540
  4. 21 Dec, 2002 3 commits
    • Kurt B. Kaiser's avatar
      When IDLE is installed and run from a startup script, the script's · ff002b93
      Kurt B. Kaiser authored
      directory becomes sys.path[0].  What is wanted is the directory from which
      IDLE was called.
      
      Insert the current working directory in the path if it isn't there
      already.
      ff002b93
    • Kurt B. Kaiser's avatar
      M PyShell.py · dd70e1be
      Kurt B. Kaiser authored
      M idle
      M setup.py
      
      To be able to run from the source directory or from an installed version
      of IDLE, and also to allow the subprocess to find run(), Python needs to
      have the idlelib package on its path.
      
      1. Modify setup.py to supply a .pth file living at same level as idlelib
      2. Move boolcheck to PyShell.py
      3. Remove boolcheck and path setting code from the "idle" script
      dd70e1be
    • Martin v. Löwis's avatar
      9c36c291