On Tue, Sep 25, 2018 at 01:12:51AM +0500, Andrey Rahmatullin wrote:
> On Mon, Sep 24, 2018 at 03:46:09PM -0400, Nicholas D Steeves wrote:
> > > > after upgrading system-wide Python installation (in my case from 3.5.3
> > > > to 3.5.4),
> > > > virtualenvs may break due to the outdated interpreter
On Mon, Sep 24, 2018 at 03:46:09PM -0400, Nicholas D Steeves wrote:
> > > after upgrading system-wide Python installation (in my case from 3.5.3 to
> > > 3.5.4),
> > > virtualenvs may break due to the outdated interpreter
> > > (somevirtualenv/bin/python3) inside the venv, trying to work with a
Hello,
This bug came to my attention because elpy -> pyvenv-el
-> virtualenvwrapper.
On Sat, Sep 22, 2018 at 12:18:33PM +0500, Andrey Rahmatullin wrote:
> On Thu, Dec 14, 2017 at 01:33:18PM +0100, Krzysztof Słychań wrote:
> > after upgrading system-wide Python installation (in my case from 3.5.3
On Thu, Dec 14, 2017 at 01:33:18PM +0100, Krzysztof Słychań wrote:
> after upgrading system-wide Python installation (in my case from 3.5.3 to
> 3.5.4),
> virtualenvs may break due to the outdated interpreter
> (somevirtualenv/bin/python3) inside the venv, trying to work with a newer
> stdlib.
Package: virtualenvwrapper
Version: 4.3.1-2
Severity: important
Dear Maintainer,
after upgrading system-wide Python installation (in my case from 3.5.3 to
3.5.4),
virtualenvs may break due to the outdated interpreter
(somevirtualenv/bin/python3) inside the venv, trying to work with a newer
5 matches
Mail list logo
