[IPython-dev] Introduction to Contributing workshop (Python Sheffield)

Aaron Meurer asmeurer at gmail.com
Wed Feb 29 15:22:30 EST 2012

I agree with this.  Virtualenv is for more hardcore development than
was likely to be encountered at something like this.  It's useful if
you want to completely isolate yourself from your work, either because
you want to test dependencies (or lack thereof), or because you need
to keep a working environment even while you develop.  For something
like this, I would think that in most cases, installing would not be
necessary at all, but it should be sufficient to just work straight
out of the git directory.

Aaron Meurer

On Wed, Feb 29, 2012 at 12:46 PM, Fernando Perez <fperez.net at gmail.com> wrote:
> On Wed, Feb 29, 2012 at 11:28 AM, Thomas Kluyver <takowl at gmail.com> wrote:
>> No problem. I've just put the slides (ODP) here:
>> http://archive.ipython.org/media/Contributing%20to%20IPython.odp
> quick question: isn't it easier to run 'setup.py develop' than
> 'install' in the venv?  I don't use venv for ipython development and
> instead run straight from the git repo, so I'm not sure.  But my
> understanding was that this would help people shorten the edit/test
> cycle by not requiring re-installation in the venv after any changes.
> f
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev

More information about the IPython-dev mailing list