Your message dated Sat, 09 May 2020 13:31:33 -0400
with message-id <1956155.rIvXOp8RvC@sk-desktop>
and subject line Bug #795011: virtualenv does not work with a path containing
special characters
has caused the Debian Bug report #795011,
regarding virtualenv does not work with a path containing special characters
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
795011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795011
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: virtualenv
Version: 1.11.6+ds-1
Severity: normal
Hello,
virtualenv does not work when the path contains special characters:
Running virtualenv with interpreter /usr/bin/python2
New python executable in venv/bin/python2
Not overwriting existing python script venv/bin/python (you must use
venv/bin/python2)
Traceback (most recent call last):
File "<string>", line 1, in <module>
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 14:
ordinal not in range(128)
ERROR: The executable venv/bin/python2 is not functioning
ERROR: It thinks sys.prefix is
u'/home/pierre/T\xe9l\xe9chargements/letsencrypt' (should be
u'/home/pierre/T\xe9l\xe9chargements/letsencrypt/venv')
ERROR: virtualenv is not compatible with this system or executable
It does work correctly with a path containing only ascii characters.
Regards,
-- System Information:
Debian Release: 8.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages virtualenv depends on:
ii python3 3.4.2-2
ii python3-virtualenv 1.11.6+ds-1
virtualenv recommends no packages.
virtualenv suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 09 Aug 2015 15:41:20 +0200 Pierre Rudloff <[email protected]> wrote:
> Package: virtualenv
> Version: 1.11.6+ds-1
> Severity: normal
>
> Hello,
>
> virtualenv does not work when the path contains special characters:
>
> Running virtualenv with interpreter /usr/bin/python2
> New python executable in venv/bin/python2
> Not overwriting existing python script venv/bin/python (you must use
> venv/bin/python2)
> Traceback (most recent call last):
> File "<string>", line 1, in <module>
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 14:
> ordinal not in range(128)
> ERROR: The executable venv/bin/python2 is not functioning
> ERROR: It thinks sys.prefix is
> u'/home/pierre/T\xe9l\xe9chargements/letsencrypt' (should be
> u'/home/pierre/T\xe9l\xe9chargements/letsencrypt/venv')
> ERROR: virtualenv is not compatible with this system or executable
>
> It does work correctly with a path containing only ascii characters.
This was likely a result of python2 not being natively UTF-8 aware. Now that
virtualenv is python3 (which is), I believe this is resolved, so I am closing
the bug. This should no longer be an issue on any supported Debian release.
If this happens again, please file a new bug with instructions on how to
reproduce the issue.
Scott K
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
_______________________________________________
Python-modules-team mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
