Re: [Distutils] library development patterns

On Thu, Jan 18, 2018 at 10:13 PM, Chris Jerdonek wrote: > 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: >

Re: [Distutils] library development patterns

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

Re: [Distutils] library development patterns

[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

Re: [Distutils] library development patterns

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 wrote: > Nick Coghlan wrote: > > The tox model is the one we

Re: [Distutils] library development patterns

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 >

Re: [Distutils] library development patterns

Chris Withers wrote: > For me, I use travis-ci coupled with a few local virtualenvs for canary > versions. Some people like tox here, I never got on with it. For me, tox is transformative. While there are a couple of usability issues that my clone army seems to be remiss in fixing, for the most

Re: [Distutils] library development patterns

On 17 January 2018 at 06:33, Jeremy Stanley wrote: > On 2018-01-16 19:13:31 + (+), Brett Cannon wrote: >> This is part of what I would want us to come to a consensus on. For >> example, do people just create a venv per Python version they want to >> test/support, do

Re: [Distutils] library development patterns

On 2018-01-16 19:13:31 + (+), Brett Cannon wrote: > On Tue, 16 Jan 2018 at 11:00 Chris Withers wrote: [...] > > I generally use pip install -e . in a checkout to set up a development > > environment but beyond this I think things branch out a lot: > > > > How do you do

Re: [Distutils] library development patterns

On Tue, 16 Jan 2018 at 11:00 Chris Withers wrote: > Okay, so lets be up front: pipenv is not for libraries or reusable apps, > it's for deployments of re-usable apps or development of single-use > application code. I think that's a great aim and covers *all* the end > use

Re: [Distutils] library development patterns

Okay, so lets be up front: pipenv is not for libraries or reusable apps, it's for deployments of re-usable apps or development of single-use application code. I think that's a great aim and covers *all* the end use cases of Python at its extreme. However, library devs, and I'd lump reusable