[issue21496] pyvenv activate_this.py

[couplewavylines]

New submission from couplewavylines:

Is there any plan to add an 'activate_this.py' to venv? The virtualenv package 
includes this script. Its purpose is to activate the environment "in-place," 
from other Python code.
One use-case is running multiple WSGI apps that each need a different virtual 
environment: https://www.pythonanywhere.com/wiki/VirtualEnvForNewerDjango

--
components: Library (Lib)
messages: 218455
nosy: couplewavylines
priority: normal
severity: normal
status: open
title: pyvenv activate_this.py
type: enhancement
versions: Python 3.4, Python 3.5

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

[issue9253] argparse: optional subparsers

[couplewavylines]

Changes by couplewavylines :


--
nosy: +couplewavylines

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

[issue21496] pyvenv activate_this.py

[couplewavylines]

couplewavylines added the comment:

"run the command directly...would run with the venv's environment":  I'm sorry 
I didn't realize this, the "You don’t specifically need to activate an 
environment..." part of the venv docs didn't sink in for me when I read it 
earlier.

So yes, using a subprocess will do what I'm after.

I don't know if the subprocess will cover the situation in that link where 
they're using execfile on activate_this, but I was just trying to find a 
common-looking use-case for activate_this.

--

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

[issue20423] io.StringIO newline param has wrong default

[couplewavylines]

New submission from couplewavylines:

In io.StringIO, the newline argument's default is currently documented as 
"newline=None" in the section header. However, it's described this way:  "The 
default is to do no newline translation."  The behavior of io.StringIO is 
consistent with this description (NO newline translation). 
The header should actually read "newline=''".
"newline=None" would mean there IS newline translation by default, which is not 
the case. Code sample attached as no_translation.py.

--
assignee: docs@python
components: Documentation
files: no_translation.py
messages: 209577
nosy: couplewavylines, docs@python
priority: normal
severity: normal
status: open
title: io.StringIO newline param has wrong default
type: behavior
versions: Python 3.3, Python 3.4
Added file: http://bugs.python.org/file33779/no_translation.py

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

[issue20423] io.StringIO newline param has wrong default

[couplewavylines]

Changes by couplewavylines :


Added file: http://bugs.python.org/file33780/no_translation_output.txt

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

[issue20423] io.StringIO newline param has wrong default

[couplewavylines]

couplewavylines added the comment:

Serhiy, you're right, I now see the default behavior is "newline='\n'".

So, the header is still wrong, and the text is "The default is to do no newline 
translation" may be incorrect too?  Or just unclear (to me anyway)?

--

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