Martin v. Löwis added the comment:
Ubik: this issue is closed, as we believe that it does not exist anymore. If
you still think there is a bug surrounding mkdtemp, please make a new full bug
report. Structure your report as follows:
1. this is what you did
2. this is what happened
3. this is
Ubik added the comment:
As detailed in this SO question:
http://stackoverflow.com/questions/28101187/deal-with-unicode-usernames-in-python-mkdtemp
I still see the issue in 2.7.8.
I use a unicode prefix and changing this is not an option (editing legacy code
which expects unicode everywhere)
STINNER Victor added the comment:
The best fix is to use Python 3. In 2015, it's maybe time to use Python 3 which
has a very good Unicode support.
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1681974
Ezio Melotti added the comment:
On Win 7 with a non-ASCII username, this seems to work fine on both 2.7 and
3.3. 2.7 returns str or unicode depending on the type of the prefix=,
whereas 3.3 only accepts str (I think this is expected).
I'm going to close this as out of date, feel free to
Mark Lawrence breamore...@yahoo.co.uk added the comment:
I can't reproduce this problem on Windows Vista with any of the current
maintainance branches of Python using the interactive prompt from the command
line.
--
nosy: +BreamoreBoy
___
Python
Changes by Tim Golden m...@timgolden.me.uk:
--
nosy: +tim.golden
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1681974
___
___
Python-bugs-list
Georg Brandl ge...@python.org added the comment:
Why are you using a unicode string as your temp directory prefix? Does
it raise something different if you don't?
--
assignee: - loewis
nosy: +loewis
___
Python tracker rep...@bugs.python.org
Changes by Daniel Diniz aja...@gmail.com:
--
components: +Windows
stage: - test needed
type: - behavior
versions: +Python 2.6 -Python 2.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1681974
