On 23/03/2015 01:46, Glenn Linderman wrote:
> On 3/22/2015 8:12 AM, Tim Golden wrote:
>> I'll create a £££ user (which is the easiest non-ASCII name to create
>> on a UK keyboard) to see how cleanly the latest installer works.
>
> You can also copy/paste. A path with a Cyrillic, Greek, Chinese,
On 3/22/2015 8:12 AM, Tim Golden wrote:
I'll create a £££ user (which is the easiest non-ASCII name to create
on a UK keyboard) to see how cleanly the latest installer works.
You can also copy/paste. A path with a Cyrillic, Greek, Chinese,
Tibetan, Japanese, Armenian, and Romanian character,
On 23 Mar 2015 00:45, "Paul Moore" wrote:
>
> Something that hit me today, which might become a more common issue
> when the Windows installers move towards installing to the user
> directory, is that there appear to be some bugs in handling of
> non-ASCII paths.
>
> Two that I spotted are a failu
On 22 March 2015 at 19:34, Victor Stinner wrote:
> Please open an issue, I can take a look. Please describe a scenario to
> reproduce the issue.
The "issue" with the launcher seems to have bee a red herring. When I
set up a test case properly, it worked. I suspect I messed up writing
the shebang
Hi Paul,
Please open an issue, I can take a look. Please describe a scenario to
reproduce the issue.
Victor
2015-03-22 15:44 GMT+01:00 Paul Moore :
> Something that hit me today, which might become a more common issue
> when the Windows installers move towards installing to the user
> directory,
On 22/03/2015 15:12, Tim Golden wrote:
On 22/03/2015 14:44, Paul Moore wrote:
On which note, I'm assuming neither of the issues I've found are major
blockers. "pip.exe doesn't work if Python is installed in a directory
with non-ASCII characters in the name" can be worked around by using
python -
On 22/03/2015 14:44, Paul Moore wrote:
On which note, I'm assuming neither of the issues I've found are major
blockers. "pip.exe doesn't work if Python is installed in a directory
with non-ASCII characters in the name" can be worked around by using
python -m pip, and the launcher issue by using a
Something that hit me today, which might become a more common issue
when the Windows installers move towards installing to the user
directory, is that there appear to be some bugs in handling of
non-ASCII paths.
Two that I spotted are a failure of the "script wrappers" installed by
pip to work wit
