Message139777
| Author |
vinay.sajip |
| Recipients |
alexis, eric.araujo, tarek, vinay.sajip |
| Date |
2011年07月04日.14:38:49 |
| SpamBayes Score |
2.6797514e-05 |
| Marked as misclassified |
No |
| Message-id |
<1309790329.53490.YahooMailRC@web25805.mail.ukl.yahoo.com> |
| In-reply-to |
<1309788662.12.0.695151862591.issue12391@psf.upfronthosting.co.za> |
| Content |
> Éric Araujo <merwok@netwok.org> added the comment:
> 2 and 3: Alexis most probably added that behavior as a convenience. Unless
>I’m mistaken, the point of $TMP/$TMPDIR is that the OS itself will clean it up,
>for example on shutdown, so programs that leave stuff here are not strictly
>wrong. However, given the realities of Windows behavior (I recall seeing
>"temporary" directories with tons of stuff never cleaned up) and the low cost
>of a change ("It's not asking a lot to be given an explicit path to install to"
>+1), my opinion is that we should take your patch as it is.
Great. Although /tmp is cleaned up on restart (on Linux at least), waiting for
that can lead to problems. For example, I came across this problem when I (for
test purposes) installed every single one of the 400+ packages on PyPI which
claim to be Py3 compatible, into a virtual env, using "pysetup3 install". I then
noticed some (slight) performance slowdown and sudden disappearance of free disk
space ... it was all those archives (and their unpacked contents) in /tmp that
was the reason. |
|