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 mark.dickinson
Recipients georg.brandl, mark.dickinson, rhettinger
Date 2009-02-22.09:34:52
SpamBayes Score 2.7222437e-05
Marked as misclassified No
Message-id <1235295360.2.0.356768504387.issue5341@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks, Georg.  And yes, I was indeed wondering why I found so few wayward 
apostrophes!

Applied in r69846, r69847.  I'm not sure whether it's worth backporting 
these to 2.6 and 3.0.

> Please do not change builtin to built-in.  In a python context, it reads
> fine as one word.

"built-in" seems to be the more common spelling within the documentation.
Personally, in the context of Python I find "builtin" acceptable as a noun 
("don't shadow builtins"), but it still looks wrong when used as an 
adjective ("the builtin function open").  Anyway, I'll refrain from making 
any more of these changes.
History
Date User Action Args
2009-02-22 09:36:00mark.dickinsonsetrecipients: + mark.dickinson, georg.brandl, rhettinger
2009-02-22 09:36:00mark.dickinsonsetmessageid: <1235295360.2.0.356768504387.issue5341@psf.upfronthosting.co.za>
2009-02-22 09:34:53mark.dickinsonlinkissue5341 messages
2009-02-22 09:34:52mark.dickinsoncreate