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 r.david.murray
Recipients brian.curtin, dabrahams, eric.araujo, eric.smith, jaraco, ncoghlan, pitrou, r.david.murray, tim.golden
Date 2012-04-10.13:42:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334065367.33.0.05253526615.issue14243@psf.upfronthosting.co.za>
In-reply-to
Content
Well, fixing NamedTemporaryFile in either of the ways we've discussed isn't going to fix people writing non-portable code.  A unix coder isn't necessarily going to close the file before reading it.  However, it would at least significantly increase the odds that the code would be portable, while the current situation *ensures* that the code is not portable.
History
Date User Action Args
2012-04-10 13:42:47r.david.murraysetrecipients: + r.david.murray, jaraco, ncoghlan, pitrou, eric.smith, tim.golden, eric.araujo, brian.curtin, dabrahams
2012-04-10 13:42:47r.david.murraysetmessageid: <1334065367.33.0.05253526615.issue14243@psf.upfronthosting.co.za>
2012-04-10 13:42:46r.david.murraylinkissue14243 messages
2012-04-10 13:42:46r.david.murraycreate