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 cheryl.sabella
Recipients cheryl.sabella, docs@python, rhettinger
Date 2017-06-03.15:33:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1496504011.02.0.0111244449509.issue30538@psf.upfronthosting.co.za>
In-reply-to
Content
Thank you.  I've added that.  

This may seem like an odd question, but should I assume that the docs should always match the code?  For example, in the Functional HOWTO, I wasn't sure if the arguments were left off purposely or if it was just something that hadn't been updated.  If the docs should always match, then I wouldn't have to ask so many questions if I see another place where this happens.

Also, the example for enumerate is this:

f = open('data.txt', 'r')
for i, line in enumerate(f):
    if line.strip() == '':
        print('Blank line at line #%i' % i)

Is it code churn to replace the old style string formatting or is that something else that should be done as clean-up?
History
Date User Action Args
2017-06-03 15:33:31cheryl.sabellasetrecipients: + cheryl.sabella, rhettinger, docs@python
2017-06-03 15:33:31cheryl.sabellasetmessageid: <1496504011.02.0.0111244449509.issue30538@psf.upfronthosting.co.za>
2017-06-03 15:33:31cheryl.sabellalinkissue30538 messages
2017-06-03 15:33:30cheryl.sabellacreate