Tim Chase wrote: >>> ASIDE: I've started refactoring this bit out in my local >>> source...how would I go about contributing it back to the >>> Python code-base? I didn't get any feedback from posting to >>> the Optik site. >> >> You can post a patch to bugs.python.org, but it will probably >> just get forwarded to the optik site because the optparse >> module is supposed to be automatically generated from the >> current optik release. My impression is that optik is mostly >> unmaintained, which makes getting patches applied to optik >> difficult... > > What sorts of things are required? Just a patch? Or do I also > need to include some sort of collection of doctest/unittests or > documentation patches (and if so, against which documentation > source)?
Yes, your patch will need to include tests and docs as well. I would make the patch against the sources from the optik site (though I didn't see a CVS or SVN repository so you may just have to do it against the source release files). Add your tests to test/test_optik.py and your doc fixes to doc/reference.txt (or whichever doc/ file seems most appropriate). Thanks for taking this on, BTW. STeVe -- http://mail.python.org/mailman/listinfo/python-list