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 georg.brandl
Recipients BreamoreBoy, Phillip.M.Feldman@gmail.com, georg.brandl, gvanrossum, gward, jerith, mark.dickinson, mrabarnett, palfrey, terry.reedy, tlynn
Date 2010-11-23.07:50:26
SpamBayes Score 0.0005540306
Marked as misclassified No
Message-id <1290498628.18.0.591053433752.issue1859@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, please do apply.  You don't need to run a doc build for every small change; of course it is nice if you do, but errors will be caught by the daily build routine anyway and mailed to me.

As for the two blank lines: you'll see that the original conversion from LaTeX produced two blank lines after each description (function, class, ...), and I find this to be a little more readable than only one blank line, especially when the descriptions are longer; for short descriptions leaving only one blank line saves space.  Syntactically, both are fully equivalent.
History
Date User Action Args
2010-11-23 07:50:28georg.brandlsetrecipients: + georg.brandl, gvanrossum, gward, terry.reedy, mark.dickinson, tlynn, palfrey, jerith, mrabarnett, Phillip.M.Feldman@gmail.com, BreamoreBoy
2010-11-23 07:50:28georg.brandlsetmessageid: <1290498628.18.0.591053433752.issue1859@psf.upfronthosting.co.za>
2010-11-23 07:50:26georg.brandllinkissue1859 messages
2010-11-23 07:50:26georg.brandlcreate