This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tim.peters
Recipients
Date 2004-06-05.23:43:19
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=31435

Assuming the current state of the proposal consists of the 
first two patches on the list ("patch for datetimemodule.c" 
and "patch for datetime.h"), I'm probably happy to commit 
them.  Can't say for sure right now, because SF CVS is dead, 
and can't get a current checkout to try them with.

The one necessary thing I don't see are docs:  how are users 
supposed to know this exists, let alone know how to use it?  
We need a new section for datetime objects in the Python/C 
API Reference Manual, in the Other Objects part of the 
Concrete Objects Layer section.  You don't have to write 
LaTeX, plain text is fine.  Look at the other sections in that 
chapter for what's needed (an overview, and a precise 
account of what's in the new C API and how to use it).

Don't let that discourage you -- you're very close!  If I don't 
force docs out of you now, docs will never get written.  
That's why I'm trying to force docs out of you now <wink>.
History
Date User Action Args
2007-08-23 15:31:58adminlinkissue876130 messages
2007-08-23 15:31:58admincreate