Open GoogleCodeExporter opened 8 years ago
Thanks for reporting this! I'm glad that you could work around it for now.
We've been able to reproduce this on our end and will take a look at how to fix
it.
Original comment by z...@google.com
on 28 May 2015 at 3:10
+1 - the bug also exists if you have a windows username with latin characters.
this happened with some students on my class.
Original comment by ronoaldo
on 9 Jul 2015 at 2:01
Just letting you know that we haven't forgotten about this.
Original comment by z...@google.com
on 10 Jul 2015 at 3:12
This immediate issue is fairly easy to fix, but we think it'll just cause a lot
of other problems related to non-ASCII paths and the Cloud SDK. Once we have
some good tests in place and are comfortable that there are no obvious bugs
related to non-ASCII path installations we'll update here.
Original comment by z...@google.com
on 27 Aug 2015 at 5:20
Issue 274 has been merged into this issue.
Original comment by z...@google.com
on 1 Oct 2015 at 11:32
Issue 448 has been merged into this issue.
Original comment by z...@google.com
on 4 Jan 2016 at 5:03
Just to let you know this report is still with the engineering team and any
status updates will be posted here.
Original comment by abdull...@google.com
on 5 Apr 2016 at 7:27
Any advancement on that?
Currently, the installation fails when the path of the user has "Doublebytes" characters unless it is installed for all users, and bundled version of Python is not installed. An existing version of Python 2.7 must be installed and on PATH.
But even then, it's unusable, as it will sooner or later try to read from AppData.
Changing the user path is not possible on Windows 10.
Original issue reported on code.google.com by
rou...@gmail.com
on 27 May 2015 at 6:53