PS - this is the pyenv / tox compatibility issue I had in mind: https://github.com/pyenv/pyenv-virtualenv/issues/202
And this I have found is the simplest workaround: https://github.com/pyenv/pyenv-virtualenv/issues/202#issuecomment-284728205 On Thu, Jan 18, 2018 at 1:04 PM, Chris Jerdonek <chris.jerdo...@gmail.com> wrote: > [Oops, my phone weirdly sent that email prematurely.] > > I haven’t yet seen pyenv mentioned in this discussion. Having the > ability to switch between Python versions for interactive exploration > seems like an important piece for library development, and pyenv makes > this really easy. My only complaint is that I've had problems with tox > and pyenv playing nice together. (IIRC, you need to create a pyenv > virtualenv a certain way for tox to be able to use it, and I think > there are some pyenv issues about this that have always been marked as > "wontfix.") > > --Chris > > > On Thu, Jan 18, 2018 at 12:57 PM, Chris Jerdonek > <chris.jerdo...@gmail.com> wrote: >> >> I haven’t yet seen pyenv mentioned in this discussion. Having the ability to >> switch between Python versions for interactive exploration seems like an >> important piece for >> >> On Thu, Jan 18, 2018 at 11:18 AM Barry Warsaw <ba...@python.org> wrote: >>> >>> Nick Coghlan wrote: >>> > The tox model is the one we decided to natively support in Fedora as >>> > well - while there's only ever one "full" Python 3 stack in the main >>> > repos (with all the distro API bindings, etc), there are also >>> > interpreter-only packages for other still supported and/or still >>> > popular Python X.Y branches, and "dnf install tox" will bring in all >>> > of them as weak dependencies. >>> > >>> > Hence my preference for where I think it would make sense to take >>> > pipenv in this regard: better *enable* the tox model, without >>> > *duplicating* the tox model. >>> >>> I'm a big fan of the tox model. It works great on Debian/Ubuntu where >>> you can have multiple Python 3 interpreters (with some shared >>> infrastructure) during transitions, and macOS development where you >>> might have multiple versions of Python installed from brew/fink/macports >>> and from-source installations, including the current Python development >>> versions. It also works well for things like >>> https://gitlab.com/python-devs/ci-images/tree/master >>> >>> tox provides a nice, easy to invoke and remember CLI, good separation of >>> concerns (e.g. runtime deps in setup.py, test deps in tox.ini), and >>> convenient management of venvs. >>> >>> Cheers, >>> -Barry >>> >>> >>> _______________________________________________ >>> Distutils-SIG maillist - Distutils-SIG@python.org >>> https://mail.python.org/mailman/listinfo/distutils-sig _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
