You should confirm that the python executable in the venv is actually
Python 2.7, which you can do by running
~/env_dir/python -V
~/env_dir/python2.7 -V
(both of those files should exist, and you can run the above without
activating the virtualenv, as you're specifying the exact path).
If either
A quick check of PyPI doesn't show a wheel for fastdtw 0.3.0. Have you
perhaps got an extra index configured somewhere? And if so, did you
only configure it for the "install" command, and not for the
"download" command?
On 19 January 2017 at 16:11, Diego Costantini
wrote:
> Hi,
> on pip version 8
On 11 August 2017 at 16:06, wrote:
> I just installed virtualenv and am getting an error trying to create an
> environment. Based on some print statements I added, sys.prefix seems to be
> getting lowercased somewhere within virtualenv.exe, before runpy.py starts.
> And that leads to an error in
filesystem for your home directory, do you?)
Sorry I can't offer more help...
Paul
On 11 August 2017 at 20:58, wrote:
> It's just a batch file that wraps virtualenv.exe. I get the same output,
> less the first print statement, when I call virtualenv.exe directly.
>
>
problem, unless you've already spotted it.
Paul
On 11 August 2017 at 22:08, wrote:
> The error isn't coming from the OS, there's case-sensitive logic in
> virtualenv.pl.
>
> On Friday, August 11, 2017 at 1:07:39 PM UTC-7, Paul Moore wrote:
>>
>>
I've seen your reports. Personally, I haven't responded because I'm a
Windows developer and I don't really have the knowledge of Unix to
reliably assess fixes like this. Normally, I'd be wiling to make some
level of common-sense judgement, but virtualenv is something of a
special case. Specifically
