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 https://pip.pypa.io/en/latest/user_guide.html#requirements-files
John
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
On Sat, Jan 17, 2015 at 10:48 AM, John ZuHone jzuhone@gmail.com 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
I think we should specify only "loose" dependencies via install_requires. Requirements files are more usefull for "strict" dependencies, e.g. when building a web app based on libraries that don't guarantee API stability. See e.g. this blog post:
http://blog.miguelgrinberg.com/post/the-package-dependency-blues
I believe there's magic to get pip to automatically download dependencies based on install_requires whenever setup.py is invoked, but I could never figure out how to get it to work when I experimented with this in the past. This also doesn't necessarily do much for us, since our dependencies in turn depend on C libraries that we have no way to install from within pip.
John
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@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@gmail.com 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@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
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@gmail.com wrote:
Yes, we should.
On Sat, Jan 17, 2015, 2:50 PM John ZuHone jzuhone@gmail.com 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@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
On Sun, Jan 18, 2015 at 6:49 AM, John Zuhone jzuhone@gmail.com wrote:
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?),
freetype and libpng as well, through matplotlib
because those failures will be related to those other packages (h5py) and not yt in particular.
fair enough. it should also be possible to make h5py an on-demand import, like astropy.
On Sat, Jan 17, 2015 at 4:04 PM, Matthew Turk matthewturk@gmail.com wrote:
Yes, we should.
On Sat, Jan 17, 2015, 2:50 PM John ZuHone jzuhone@gmail.com 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@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- John ZuHone
Postdoctoral Researcher NASA/Goddard Space Flight Center
jzuhone@gmail.com john.zuhone@nasa.gov _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
On Jan 18, 2015, at 6:24 PM, Nathan Goldbaum nathan12343@gmail.com wrote:
fair enough. it should also be possible to make h5py an on-demand import, like astropy.
That would probably be pretty difficult, actually. I've had people ask for this, but their use cases are pretty corner. _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
On Sun, Jan 18, 2015 at 3:52 PM, John ZuHone jzuhone@gmail.com wrote:
On Jan 18, 2015, at 6:24 PM, Nathan Goldbaum nathan12343@gmail.com
wrote:
fair enough. it should also be possible to make h5py an on-demand
import, like astropy.
That would probably be pretty difficult, actually. I've had people ask for this, but their use cases are pretty corner.
I think making the top-level "yt" import not depend on h5py is definitely doable.
We import h5py a bunch of places, but we don't actually *need* it for anything besides reading certain data types and things like hdf5 sidecar files, which can just fail with an import error.
In fact, the only thing we use in the h5py namespace is "File", so we would just need to wrap that class.
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
On Sun, Jan 18, 2015 at 6:49 AM, John Zuhone jzuhone@gmail.com wrote:
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.
Apparently this was fixed in Setuptools 7.0, released late last year:
https://bitbucket.org/pypa/setuptools/pull-request/97/cache-eggs-required-fo...
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@gmail.com wrote:
Yes, we should.
On Sat, Jan 17, 2015, 2:50 PM John ZuHone jzuhone@gmail.com 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@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- John ZuHone
Postdoctoral Researcher NASA/Goddard Space Flight Center
jzuhone@gmail.com john.zuhone@nasa.gov _______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@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@gmail.com 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@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
If we have pip as the suggested method we absolutely need a very fast and predetermined release schedule. I think it will only be possible with a disciplined approach to bug fixes and the stable branch.
On Sat, Jan 17, 2015, 5:34 PM Cameron Hummels chummels@gmail.com wrote:
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@gmail.com 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@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@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ yt-dev mailing list yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-
Cameron Hummels -
John ZuHone -
John Zuhone
-
Matthew Turk -
Nathan Goldbaum