Hi Luke,
For day-to-day development and testing of numpy, I don't bother with
either inplace builds *or* installing it -- I just use the magical
"runtests.py" script that you'll find in the root of your git
checkout.
E.g., to build and then test the (possibly modified) source in your
current checkout, just do:
./runtests.py
That's all. This builds into a hidden directory and then sets up the
correct PYTHONPATH before running the tests etc. -- you don't have to
worry about any of it, it's magic.
There are also lots of options, see ./runtests.py --help. Try adding
-j for multi-core builds, or you can specify arbitrary options to pass
to nose, or you can run it under gdb (there's an example in --help),
or if you just want an interactive shell to futz around in manually
instead of running the test suite then try passing --ipython.
BTW, numpy has its own mailing list at numpy-discussion@scipy.org
(CC'ed), which is where numpy development discussions usually take
place -- this list is more for scipy-the-package itself. There's lots
of overlap in readership between the two lists, but numpy-discussion
will probably give you quicker and more useful answers to questions
like this in general :-)
-n
On Sat, Oct 17, 2015 at 4:03 PM, Luke Zoltan Kelley
<lkel...@cfa.harvard.edu> wrote:
> Thanks Nathan, I'll try that. Both without the inplace build, I'll have to
> rebuild and install everytime I want to test something, right?
>
> On Oct 17, 2015, at 6:42 PM, Nathan Woods <charlesnwo...@gmail.com> wrote:
>
> My best guess is to nuke and reclone Numpy, then do setup.py install without
> the inplace build. What you're doing seems like it should work, though, so
> I'm not sure what's going on.
>
> Nathan Woods
>
> On Oct 17, 2015, at 3:59 PM, Luke Zoltan Kelley <lkel...@cfa.harvard.edu>
> wrote:
>
> When trying to do that is when I get the error I described in the OP. i.e.
> I get an error when trying to install.
>
>
> On Oct 17, 2015, at 5:57 PM, Andrew Nelson <andyf...@gmail.com> wrote:
>
> It would get installed into whatever conda environment you had activated.
>
> _______________________________________________
> SciPy-Dev mailing list
> scipy-...@scipy.org
> https://mail.scipy.org/mailman/listinfo/scipy-dev
>
>
> _______________________________________________
> SciPy-Dev mailing list
> scipy-...@scipy.org
> https://mail.scipy.org/mailman/listinfo/scipy-dev
>
> _______________________________________________
> SciPy-Dev mailing list
> scipy-...@scipy.org
> https://mail.scipy.org/mailman/listinfo/scipy-dev
>
>
>
> _______________________________________________
> SciPy-Dev mailing list
> scipy-...@scipy.org
> https://mail.scipy.org/mailman/listinfo/scipy-dev
>
--
Nathaniel J. Smith -- http://vorpus.org
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion
