[issue4568] Improved optparse "varargs" callback example

Georg Brandl added the comment: Yes, it will be merged to py3k automatically; we normally merge smaller changes in batches. ___ Python tracker ___

[issue4568] Improved optparse "varargs" callback example

Gregg Lind added the comment: This patch should also be applied into the py3k branch, probably. Good catch on updating rargs, btw. ___ Python tracker ___

[issue4568] Improved optparse "varargs" callback example

Georg Brandl added the comment: I've reformatted and rewritten your patch a bit and applied it as r67788. Thanks! -- resolution: -> accepted status: open -> closed ___ Python tracker __

[issue4568] Improved optparse "varargs" callback example

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: The 2.5 documentation is not in .rst, so I remove these versions. -- nosy: +loewis versions: -Python 2.5, Python 2.5.3 ___ Python tracker <[EMAIL PROTECTED]> __

[issue4568] Improved optparse "varargs" callback example

Changes by Gregg Lind <[EMAIL PROTECTED]>: -- versions: +Python 2.5, Python 2.5.3, Python 2.6, Python 2.7, Python 3.0, Python 3.1 ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue4568] Improved optparse "varargs" callback example

New submission from Gregg Lind <[EMAIL PROTECTED]>: In the trunk (r67617) documentation for *optparse* callback example 6 doesn't handle negative number arguments, and fixing it is "left as an exercise for the reader." Well, I'm a reader, and I've attached my stab at it. Caveat: It relies in tr