[Numpy-discussion] Appveyor Testing Changes

[G Young]

With regards to testing numpy, both Conda and Pip + Virtualenv work quite
well.  I have used both to install master and run unit tests, and both pass
with flying colors.  This chart here
<http://conda.pydata.org/docs/_downloads/conda-pip-virtualenv-translator.html>
illustrates
my point nicely as well.

However, I can't seem to find / access Conda installations for slightly
older versions of Python (e.g. Python 3.4).  Perhaps this is not much of an
issue now with the next release (1.12) being written only for Python 2.7
and Python 3.4 - 5.  However, if we were to wind the clock slightly back to
when we were testing 2.6 - 7, 3.2 - 5, I feel Conda falls short in being
able to test on a variety of Python distributions given the nature of Conda
releases.  Maybe that situation is no longer the case now, but in the long
term, it could easily happen again.

Greg


On Mon, Jan 25, 2016 at 10:50 PM, Nathaniel Smith <njs at pobox.com> wrote:

> On Mon, Jan 25, 2016 at 2:37 PM, G Young <gfyoung17 at gmail.com> wrote:
> > Hello all,
> >
> > I currently have a branch on my fork (not PR) where I am experimenting
> with
> > running Appveyor CI via Virtualenv instead of Conda.  I have build
> running
> > here.  What do people think of using Virtualenv (as we do on Travis)
> instead
> > of Conda for testing?
>
> Can you summarize the advantages and disadvantages that you're aware of?
>
> -n
>
> --
> Nathaniel J. Smith -- https://vorpus.org
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20160125/c3561327/attachment.html>