Message7822
Logged In: YES
user_id=21627
No. The usage of tmpnam is not dangerous; we are just
exposing it to the Python application. It may be reasonable
to produce a warning if tmpnam is called.
We cannot replace tempnam with mkstemp for the same reason
Posix couldn't: one produces a string, the other one a file
handle.
What we could do is to expose mkstemp(3) where available. I
don't see the value of that, though: it could be done only
on systems where mkstemp is available, and we already expose
tmpfile(3). In fact, the Linux man page for mkstemp(3) says
# Don't use this function, use tmpfile(3) instead. It's
# better defined and more portable.
If you still think there is a need for action, please
propose a patch. |
|
Date |
User |
Action |
Args |
2007-08-23 13:57:38 | admin | link | issue486434 messages |
2007-08-23 13:57:38 | admin | create | |
|