[Zope3-checkins] CVS: Zope3/src/datetime - doc.txt:1.12

[Tim Peters]

Update of /cvs-repository/Zope3/src/datetime
In directory cvs.zope.org:/tmp/cvs-serv6944/src/datetime

Modified Files:
	doc.txt 
Log Message:
This is getting far enough out of synch with the LaTeX docs that it's
going to do more harm than good:  deleted the content, just leaving the
URL to the Python docs.


=== Zope3/src/datetime/doc.txt 1.11 => 1.12 === (1200/1300 lines abridged)
--- Zope3/src/datetime/doc.txt:1.11	Fri Jan  3 11:48:13 2003
+++ Zope3/src/datetime/doc.txt	Sat Jan  4 13:35:52 2003
@@ -7,1297 +7,3 @@
 
     http://www.python.org/dev/doc/devel/lib/module-datetime.html
 **************************************************************************
-
-
-
-TODO/OPEN
-=========
-- The Python implementation is missing docstrings in many places.
-
-
-CLOSED
-======
-- Pickle incompatibility?  It occurs to me that, because the
-  implementations are so different, a pickle created by the Python
-  implementation won't be unpicklable by the C implementation, or vice
-  versa.  If this is important, the Python implementation will have to
-  change, as the C implementation of pickling took days to get working
-  and has no wiggle room (TOOWTDI indeed <wink>).
-
-  Resolution:  Jim Fulton suggested adding various __reduce__ methods
-  to the Python implementation, and that did lead to pickles that the
-  C implementation groks.  I'm not sure why, and tzinfo subclasses must
-  have an __init__ that can be called without arguments now (if
-  they want to play with pickles).  It appears they must also set
-  class attr __safe_for_unpickling__ = True, but only if they want a
-  pickle written by the Python implementation to be readable by the C
-  implementation.
-
-- The test suite doesn't pass under 2.2.2, due to what Guido tracked
-  to a bug in 2.2.2's implementation of __cmp__ for new-style classes.
-  Later:  the test suite grew a version check to avoid provoking this
-  bug under 2.2.2.
-
-- What should str() do?  It generally acts like a synonym for isoformat()
-  now.  But
-
-    >>> print time(2)
-    02:00:00.000000
-    >>>
-
-  is arguably better as '2:00:00' or even '2:00'.  The Python
-  implementation has (overridden) "pretty __str__" according to one
-  person's idea of "pretty", for a couple types.  Rat hole.
-  Guido sez:  chop ".000000" when microseconds are 0, and that's it.
-  Tim sez:  and having a fixed-size string when they are will make
-  life easier for people implementing their own ideas of "pretty".

[-=- -=- -=- 1200 lines omitted -=- -=- -=-]

-    PyDateTime_DateTimeTZ
-    PyDateTime_Time
-    PyDateTime_TimeTZ
-    PyDateTime_Delta
-    PyDateTime_TZInfo
-
-Type-check macros:
-
-    PyDate_Check(op)
-    PyDate_CheckExact(op)
-
-    PyDateTime_Check(op)
-    PyDateTime_CheckExact(op)
-
-    PyDateTimeTZ_Check(op)
-    PyDateTimeTZ_CheckExact(op)
-
-    PyTime_Check(op)
-    PyTime_CheckExact(op)
-
-    PyTimeTZ_Check(op)
-    PyTimeTZ_CheckExact(op)
-
-    PyDelta_Check(op)
-    PyDelta_CheckExact(op)
-
-    PyTZInfo_Check(op)
-    PyTZInfo_CheckExact(op
-
-Accessor macros:
-
-All objects are immutable, so accessors are read-only.  All macros
-return ints:
-
-    For date, datetime, and datetimetz instances:
-        PyDateTime_GET_YEAR(o)
-        PyDateTime_GET_MONTH(o)
-        PyDateTime_GET_DAY(o)
-
-    For datetime and datetimetz instances:
-        PyDateTime_DATE_GET_HOUR(o)
-        PyDateTime_DATE_GET_MINUTE(o)
-        PyDateTime_DATE_GET_SECOND(o)
-        PyDateTime_DATE_GET_MICROSECOND(o)
-
-    For time and timetz instances:
-        PyDateTime_TIME_GET_HOUR(o)
-        PyDateTime_TIME_GET_MINUTE(o)
-        PyDateTime_TIME_GET_SECOND(o)
-        PyDateTime_TIME_GET_MICROSECOND(o)