[issue6965] tmpnam should not be used if tempfile or mkstemp are available

Florent Xicluna added the comment: Then close it as duplicate of issue486434, which was closed for the same reason. -- resolution: -> duplicate status: open -> closed ___ Python tracker ___

[issue6965] tmpnam should not be used if tempfile or mkstemp are available

Mark Dickinson added the comment: The os.tmpnam and os.tempnam functions are already removed from Python 3.x: see issue 1318 for the discussion leading to that removal. I don't see a way to remove them from 2.7 without breaking backwards compatibility. -- nosy: +mark.dickinson

[issue6965] tmpnam should not be used if tempfile or mkstemp are available

Changes by Florent Xicluna : -- type: -> compile error ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue6965] tmpnam should not be used if tempfile or mkstemp are available

Florent Xicluna added the comment: I get similar warnings while building on Debian AMD64: (...) libpython2.7.a(posixmodule.o): In function `posix_tmpnam': ./Modules/posixmodule.c:7193: warning: the use of `tmpnam_r' is dangerous, better use `mkstemp' libpython2.7.a(posixmodule.o): In function

[issue6965] tmpnam should not be used if tempfile or mkstemp are available

New submission from djc : I have a bug report in the Gentoo tracker (http://bugs.gentoo.org/show_bug.cgi?id=221183): "This is a rather strange request, but please bear me. While building Posix module, python checks (among others) for tmpfile, tmpnam and tmpnam_r however man pages state explicitl