I used to be a huge advocate for the "develop" mode, but not anymore. I have run into way too many Heisenbugs that would clear up if I nuked my source tree and re-clone.

I should also note that there is currently an open issue with "pip install -e" and namespace packages. This has been reported to matplotlib with regards to mpl_toolkits. Essentially, if you have namespace packages, it doesn't get installed correctly in this mode, and python won't find them.

On Fri, Aug 14, 2015 at 12:12 PM, Chris Barker <chris.barker@noaa.gov> wrote:
On Thu, Aug 13, 2015 at 11:25 AM, Stefan van der Walt <stefanv@berkeley.edu> wrote:
>(for
> example "python setup.py develop", although suggested by
> setup.py itself, claims that "develop" is not a command).

develop is a command provided by setuptools, not distutils itself.

I find it absolutely invaluable -- it is THE way to go when actively working on any package under development.

if numpy doesn't currently use setuptools, it probably should (though maybe it's gets messy with numpy's distutils extensions...)

Nowadays, you can use

pip install -e .

pip "injects" setuptools into the mix -- so this may be develope mode with a different name. but yes, a fine option for a package that doesn't use setuptools out of the box.

-Chris

--

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker@noaa.gov

_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion