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 methane
Recipients Carl Osterwisch, Gabi.Davar, chary314, dabrahams, davide.rizzo, dlenski, eric.araujo, eric.smith, eryksun, ethan smith, ethan.furman, ev2geny, jaraco, jwilk, martin.panter, methane, ncoghlan, njs, paul.moore, piotr.dobrogost, pitrou, r.david.murray, sbt, steve.dower, tim.golden, zach.ware
Date 2021-05-01.01:32:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
+1 to Eryk.

> Hence my newbie questions are:

1) What problem are you trying to solve by this "unlinking trick"?

Same to TempoaryFile in Unix.

2) Do we need to have a separate issue raised for this problem?

I don't think so. We didn't unlink because wi didn't have separate implementation for TemporaryFile and NamedTemporaryFile.
When we have two implementations for them, it is straightforward and natural to use unlink trick.

3) Is this "unlinking trick" using some documented features of Windows? (will it not stop working after some Windows patch)?

I am not sure. But it is "POSIX function" in windows. I believe MS won't break compatibility.

4) Will we need to create separate unit tests for this issue?

We already have tests for TemporaryFile.

5) Do we also need to reach a consensus on implementing of this "unlinking trick"?

If anyone against it. But I think Eryk's proposal is the most reasonable.
Date User Action Args
2021-05-01 01:32:52methanesetrecipients: + methane, paul.moore, jaraco, ncoghlan, pitrou, eric.smith, tim.golden, jwilk, eric.araujo, r.david.murray, njs, dabrahams, ethan.furman, davide.rizzo, sbt, Gabi.Davar, martin.panter, piotr.dobrogost, zach.ware, dlenski, eryksun, steve.dower, Carl Osterwisch, ethan smith, ev2geny, chary314
2021-05-01 01:32:51methanesetmessageid: <>
2021-05-01 01:32:51methanelinkissue14243 messages
2021-05-01 01:32:51methanecreate