Non ASCII characters in path cause problems

[camillem]

Hi,
It seems that Ubuntu 17.10 is not currently supported.
Any plans to add it ?
Thanks,
Camille

[pombredanne]

@camillem Always at the vanguard! Can you tell me what problems you have encountered? And error message you got? Normally it should run on it OK, but I never tried it.

[camillem]

@pombredanne I'm prolly missing something obvious :-/

scancode-toolkit-2.2.1$ ./scancode --help
./scancode: ligne 114: scancode-toolkit-2.2.1/bin/scancode: Aucun fichier ou dossier de ce type

[pombredanne]

@camillem did you take the release archive for 2.2.1? and do you have Python 2.7 available on your distro?

[camillem]

the release archive for 2.2.1

yes

do you have Python 2.7 available

Looks like it:

scancode-toolkit-2.2.1$ python --version
Python 2.7.14

[pombredanne]

hum... Let me try to debug this is a VM or container

[camillem]

Ooops, I think I got it. I tried on 16.04 and had the same problem, so...
It happens when you have an non ASCII character in your path. Like ~/Téléchargements/...

[camillem]

So, I should may be rename the issue to Python 3 support ;-) ?

[pombredanne]

@camillem non ASCII character in your path. Like ~/Téléchargements/... is not a Python3 issue, but a plain bug. Let me fix this!

[camillem]

@pombredanne Thanks. Let me know if I can help testing.

[pombredanne]

The root cause is this bug pypa/virtualenv#457 and indeed the problem does not happen with virtualenv on Python 3. At this stage and until we either complete the migration to Python 3 or the bug is fixed upstream, there is no way out but to use a path that contains only ASCII characters

[pombredanne]

I added a FAQ entry and details in the comprehensive installation doc.
I will keep this open until fixed.
@camillem Thank you ++ for this report and sorry for the inconvenience!