enso doesn't work if username contains non-latin chars

Bug #725677 reported by Artem Tartakynov on 2011-02-26
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Enso Project

Bug Description

Enso doesn't works if username contains non-latin characters (in localized versions of Windows).
It seems that issue in /enso/platform/win32/system/Folders.py
The patch is attached

Artem Tartakynov (artem-tad) wrote :
blackdaemon (blackdaemon) wrote :

Hi Artem, thanks for posting this. Please could you also attach the log or paste the traceback? I would like to see where exactly this fails. Thanks

Changed in enso:
assignee: nobody → blackdaemon (blackdaemon)
blackdaemon (blackdaemon) wrote :

I am not able to reproduce this on Windows XP CZ.
What version of pywin32 do you have?
Please post the traceback.

Artem Tartakynov (artem-tad) wrote :

Windows 7, Russian
pywin32 215

enso runs but does not load commands (obviously from C:\Users\<UserName>\AppData\Local\Enso\commands).
soon i'll try to provide logs and traceback, too busy now...

blackdaemon (blackdaemon) wrote :

OK Iwas able to reproduce this on Windows 7 Czech.

This is major problem in standard Python os.path.expanduser() which uses 'environ' dict to get to the USERPROFILE variable.
'environ' dict contains non-unicode strings in mixed encodings and using getdefaultfileencoding() is not guaranteed to work in all
Windows national versions.

I work on general fix that will not use environment variable on Windows platform.

Changed in enso:
importance: Undecided → Critical
status: New → In Progress
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers