Author jaraco
Recipients brian.curtin, dabrahams, eric.araujo, eric.smith, jaraco, ncoghlan, pitrou, r.david.murray, tim.golden
Date 2012-04-10.13:08:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <5A500C6B-914E-4380-868E-471DEA930177@jaraco.com>
In-reply-to <1334060760.5371.1.camel@localhost.localdomain>
Content
I agree. If the primary usage of the class does not work well on Windows, developers will continue to write code using the primary usage because it works on their unix system, and it will continue to cause failures when run on windows. Because Python should run cross-platform, I consider this a bug in the implementation and would prefer it be adapted such that the primary use case works well on all major platforms.

If there is a separate class method for different behavior, it should be for the specialized behavior, not for the preferred, portable behavior.

I recognize there are backward-compatibility issues here, so maybe it's necessary to deprecate NamedTemporaryFile in favor of a replacement.
History
Date User Action Args
2012-04-10 13:08:59jaracosetrecipients: + jaraco, ncoghlan, pitrou, eric.smith, tim.golden, eric.araujo, r.david.murray, brian.curtin, dabrahams
2012-04-10 13:08:58jaracolinkissue14243 messages
2012-04-10 13:08:58jaracocreate