Metadata for patches: how?
David Goodger
dgoodger at bigfoot.com
Sat Aug 5 18:11:29 EDT 2000
I've just submitted a couple of patches (my first) and I would like to
include some commentary to point out certain areas. How is this done? Should
I have included comments inside the patches themselves (I was loathe to do
so, fearing the comments wouldn't be removed)? Or should I send email to
somebody? (I've resisted the urge to send this to python-dev. Should I
have?) Ideally there would be a more spacious comments/summary field on the
submission form at SourceForge :>
The patches are nos. 101085 and 101086, extensions to calendar.py and
libcalendar.tex (the associated documentation), respectively. The commentary
I'd have included would be:
Extended calendar.py: (1) To allow any weekday to start a week, not
just Monday as hardcoded. (2) Added functions which return month
and year calendars as strings (e.g. prmonth() prints, month() returns
string), so we aren't forced to play with stdout when we don't want to
print. Had to modify some names in prmonth() & prcal()'s
signatures.
Extended libcalendar.tex: I don't have TeX, and am not fluent, so I
hacked the doc code, and can't guarantee it is without error.
--
David Goodger dgoodger at bigfoot.com Open-source projects:
- The Go Tools Project: http://gotools.sourceforge.net
(more to come!)
More information about the Python-list
mailing list