[issue22343] Install bash activate script on Windows when using venv

[Kevin Christopher Henry]

New submission from Kevin Christopher Henry:

When I use venv to create a new virtual environment in Windows I'm given two 
activate scripts, a .bat file and a .ps1 file (which is consistent with the 
documentation).

However, bash (and probably the other shells as well) works just fine in 
Windows under Cygwin. Since you have these scripts anyway, please include them 
in the Windows virtual environment (as virtualenv did).

--
components: Windows
messages: 226452
nosy: marfire
priority: normal
severity: normal
status: open
title: Install bash activate script on Windows when using venv
type: enhancement
versions: Python 3.4

___
Python tracker 
<http://bugs.python.org/issue22343>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19111] 2to3 should remove from future_builtins import *

[Kevin Christopher Henry]

Kevin Christopher Henry added the comment:

I'm interested in working on this, but it's not clear to me if this has been 
accepted as a bug. I converted a large project recently and was shocked to find 
that all 100+ files were broken because of the needless "from 
future_builtins..." line. Perversely, this most hurts those who made the most 
effort to make their code forward-compatible with Python 3.

One complication is that you can't simply substitute a blank line, since that 
could produce invalid code if the import is inside a try/except block. (This 
doesn't affect "from __future__..." since that can only be at the start of a 
file.) Substituting a "pass" should work fine though. That would be a bit 
unsightly, but then again so is the blank line at the start of the file 
produced by removing "from __future__...". More important is to produce code 
that actually works under Python 3.

Another issue is that it's possible to simply "import future_builtins" and then 
use, for example, "future_builtins.zip(...)". So trying to fix that usage as 
well would be (I assume) a lot more complicated. Personally it seems fine with 
me to just fix the "from __future_builtins__..." usage.

--
nosy: +marfire
versions: +Python 3.5 -Python 3.3

___
Python tracker 
<http://bugs.python.org/issue19111>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22343] Install bash activate script on Windows when using venv

[Kevin Christopher Henry]

Kevin Christopher Henry added the comment:

I can confirm that LF endings work fine on Cygwin, and it's hard to imagine any 
bash implementation not handling that properly.

--

___
Python tracker 
<http://bugs.python.org/issue22343>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com