Hi dev, Should we have a requirements.txt file for pip? Currently we require users who install via pip to have the required packages set up already (numpy, sympy, h5py, etc.), but if we had a requirements file then it would pick these up automatically if they weren’t already there. https://pip.pypa.io/en/latest/user_guide.html#requirements-files

John _______________________________________________ yt-dev mailing list yt-dev(a)lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org

Yes, we should. On Sat, Jan 17, 2015, 2:50 PM John ZuHone <jzuhone(a)gmail.com&gt; wrote: > > Hi dev, > > Should we have a requirements.txt file for pip? Currently we require users > who install via pip to have the required packages set up already (numpy, > sympy, h5py, etc.), but if we had a requirements file then it would pick > these up automatically if they weren’t already there. > > https://pip.pypa.io/en/latest/user_guide.html#requirements-files > > John > _______________________________________________ > yt-dev mailing list > yt-dev(a)lists.spacepope.org > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org _______________________________________________ yt-dev mailing list yt-dev(a)lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org

On Jan 18, 2015, at 6:24 PM, Nathan Goldbaum <nathan12343(a)gmail.com&gt; wrote: fair enough. it should also be possible to make h5py an on-demand import, like astropy.

Is this "yes, we should" to install_requires or to a requirements.txt? Nathan, after looking it over, I see that there are problems when you have to define the same package in setup_requires and install_requires, which we'd have to do for NumPy.

Having to depend on other C libraries doesn't bother me as much (isn't it strictly just HDF5?), because those failures will be related to those other packages (h5py) and not yt in particular. On Sat, Jan 17, 2015 at 4:04 PM, Matthew Turk <matthewturk(a)gmail.com&gt; wrote: > Yes, we should. > > > On Sat, Jan 17, 2015, 2:50 PM John ZuHone <jzuhone(a)gmail.com&gt; wrote: >> >> Hi dev, >> >> Should we have a requirements.txt file for pip? Currently we require users >> who install via pip to have the required packages set up already (numpy, >> sympy, h5py, etc.), but if we had a requirements file then it would pick >> these up automatically if they weren’t already there. >> >> https://pip.pypa.io/en/latest/user_guide.html#requirements-files >> >> John >> _______________________________________________ >> yt-dev mailing list >> yt-dev(a)lists.spacepope.org >> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org > > > _______________________________________________ > yt-dev mailing list > yt-dev(a)lists.spacepope.org > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org > -- John ZuHone Postdoctoral Researcher NASA/Goddard Space Flight Center jzuhone(a)gmail.com john.zuhone(a)nasa.gov _______________________________________________ yt-dev mailing list yt-dev(a)lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org

I think that's a great idea for moving forward with pip as a preferred method for installing yt. Cameron On Sat, Jan 17, 2015 at 11:48 AM, John ZuHone <jzuhone(a)gmail.com&gt; wrote: > Hi dev, > > Should we have a requirements.txt file for pip? Currently we require > users who install via pip to have the required packages set up already > (numpy, sympy, h5py, etc.), but if we had a requirements file then it would > pick these up automatically if they weren’t already there. > > https://pip.pypa.io/en/latest/user_guide.html#requirements-files > > John > > _______________________________________________ > yt-dev mailing list > yt-dev(a)lists.spacepope.org > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org > > -- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org _______________________________________________ yt-dev mailing list yt-dev(a)lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org