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 | gvanrossum |
|---|---|
| Recipients | christian.heimes, gvanrossum, loewis |
| Date | 2007年10月23日.22:37:40 |
| SpamBayes Score | 0.014350571 |
| Marked as misclassified | No |
| Message-id | <1193179061.39.0.0551924883913.issue1318@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Martin, why do we need to keep these when we already have tempfile.py? I don't see that they solve any particular POSIX compatibility requirement. And they *are* unsafe. (Admitted, sometimes there's no alternative -- even tempfile.py still provides unsafe APIs by necessity.) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2007年10月23日 22:37:41 | gvanrossum | set | spambayes_score: 0.0143506 -> 0.014350571 recipients: + gvanrossum, loewis, christian.heimes |
| 2007年10月23日 22:37:41 | gvanrossum | set | spambayes_score: 0.0143506 -> 0.0143506 messageid: <1193179061.39.0.0551924883913.issue1318@psf.upfronthosting.co.za> |
| 2007年10月23日 22:37:41 | gvanrossum | link | issue1318 messages |
| 2007年10月23日 22:37:41 | gvanrossum | create | |