[New-bugs-announce] [issue26203] nesting venv in virtualenv segfaults

[André Caron]

New submission from André Caron:

When trying to create a new virtual environment using Python 3.5's venv package from a virtual environment created by the popular 3rd-party virtualenv  package, I get a segfault.

Nested virtual environments work fine both with venv and virtualenv, but using one inside the other doesn't work.  This suggests a subtle incompatibility between the two implementations.

I'm not sure whether compatibility between the implementations is a goal or not at the moment, but there is extensive tooling that uses the 3rd party virtualenv implementation.  For example, I run tests with Tox, which uses virtualenv.  I cannot test any package that uses the standard venv because everything crashes.  As a result of this, I will avoid moving to the standard implementation.

I put up some sample scripts up on GitHub to show how to reproduce the issue.  I hope they can help explain the issue.

https://github.com/AndreLouisCaron/nested-venv-bug

Cheers,

André

----------
components: Library (Lib)
messages: 258923
nosy: André Caron
priority: normal
severity: normal
status: open
title: nesting venv in virtualenv segfaults
type: crash
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26203>
_______________________________________