On Fri, 14 Jul 2017, Jeremy Hansen wrote:
Just so you know, unless there's binaries created outside of the
/usr/lib/python-*/ directories, you can safely compile both the python2
and python3 versions in the same SlackBuild.
You can just add a second line to run "python3 setup.py install
Just so you know, unless there's binaries created outside of the
/usr/lib/python-*/ directories, you can safely compile both the python2 and
python3 versions in the same SlackBuild.
You can just add a second line to run "python3 setup.py install
--root=$PKG" and each will be installed into their
On Fri, 14 Jul 2017, Audrius Kažukauskas wrote:
virtualenv is included in Python 3 Standard Library as venv[*] module. The
name of executable is pyvenv, but it was deprecated recently, although
it's still there and usable:
The pyvenv script has been deprecated as of Python 3.6 in favor of
On Fri, 2017-07-14 at 11:17:31 -0700, Rich Shepard wrote:
> On Fri, 14 Jul 2017, Larry Hajali wrote:
> > I don't know about all of the packages above but I think virtualenv comes
> > with python3.
>
> Not here. I just upgraded python3 from 3.6.0 to 3.6.1. There's no
> virtualenv in
On Fri, 14 Jul 2017, Larry Hajali wrote:
I don't know about all of the packages above but I think virtualenv comes
with python3.
Larry,
Not here. I just upgraded python3 from 3.6.0 to 3.6.1. There's no
virtualenv in /usr/lib/python3/site-packages/.
Rich
On Fri, Jul 14, 2017 at 9:14 AM, Rich Shepard
wrote:
> I installed the Python packages virtualenv, virtualenvwrapper,
> virtualenv-clone and their dependencies (e.g., tox, py, pluggy, stevedore)
> and they're all in /usr/lib/python2.7/site-packages/.
>
> I don't know
I installed the Python packages virtualenv, virtualenvwrapper,
virtualenv-clone and their dependencies (e.g., tox, py, pluggy, stevedore)
and they're all in /usr/lib/python2.7/site-packages/.
While I keep python2 installed for those applications built against it all
my new projects use