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 skip.montanaro
Recipients berker.peksag, lsowen, r.david.murray, rhettinger, skip.montanaro, vstinner, zach.ware
Date 2016-07-14.10:01:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1468490491.98.0.296360931193.issue27497@psf.upfronthosting.co.za>
In-reply-to
Content
I agree writeheader() should have returned the value of writerow(), but have no opinion on the more esoteric stuff you're discussing. I think you could argue that adding the "return" would be a bug fix.

Personally, I long ago got in the habit of using the writerow(dict(zip(fh, fh))) idiom, didn't catch on at the time that writeheader() was even available in 2.7, and still just use the idiom most of the time. It's a one-liner. The OP could easily use that in contexts where writeheader() doesn't do the right thing.
History
Date User Action Args
2016-07-14 10:01:32skip.montanarosetrecipients: + skip.montanaro, rhettinger, vstinner, r.david.murray, berker.peksag, zach.ware, lsowen
2016-07-14 10:01:31skip.montanarosetmessageid: <1468490491.98.0.296360931193.issue27497@psf.upfronthosting.co.za>
2016-07-14 10:01:31skip.montanarolinkissue27497 messages
2016-07-14 10:01:31skip.montanarocreate