Question

[Jon Ribbens]

On 2016-03-08, Ian Kelly <ian.g.kelly at gmail.com> wrote:
> On Mon, Mar 7, 2016 at 6:41 PM, Jon Ribbens
><jon+usenet at unequivocal.co.uk> wrote:
>> It's not activate.bat, it's activate (no file extension) the posix
>> shell script. I installed Git for Windows which provides bash (or
>> something that looks like it). Python venv doesn't cope with this
>> situation at all.
>
> Well, running bash on Windows is decidedly non-standard. This is like
> installing a Python package on a Linux system and then complaining
> that it won't run under wine.

I would agree with this, except that git seems to think it *is*
standard, and git itself seems pretty standard these days, so if
git thinks it's standard then disagreeing with them seems a bit
pointless.

> I don't think that Python should be expected to provide an activate
> script for all possible shells the user might conceivably want to
> use.

I would agree with this too, except that the shell script clearly
is already implemented for Unix purposes and would do no harm if
written to the directory, so presumably all 'venv' needs to do is to
stop preventing itself doing something it already knows how to do.

>> $ virtualenv test
>> Using base prefix 'd:\\program files (x86)\\python35-32'
>> New python executable in D:\Users\Jon Ribbens\Documents\Python\test\Scripts\python.exe
>> ERROR: The executable "D:\Users\Jon Ribbens\Documents\Python\test\Scripts\python.exe" could not be run: [WinError 5] Access is denied
>
> Ah, I probably never tried using it inside a user dir. On Windows I
> typically do development in a path close to the drive root, e.g.
> C:\dev.

The only things I can think of that are at all 'weird' are that there
are spaces in the filenames, and there's more than one drive. But
the former of those is utterly standard for Windows, and the latter
doesn't really even rise to the level of 'uncommon', let alone truly
unusual. If I'm seeing these problems then thousands of other people
must have already seen them before me.