DOC: better installation instructions #474
Conversation
| sudo python setup.py install | ||
| pip install --user . | ||
|
|
||
| or you work inside a virtualenv_. |
|
|
||
| To run an extended test suite that validates ``nibabel`` for long-running and resource-intensive cases, please see :ref:`advanced_testing`. | ||
| To run an extended test suite that validates ``nibabel`` for long-running and | ||
| resource-intensive cases, please see :ref:`advanced_testing`. |
There was a problem hiding this comment.
I didn't know... Need to read on ;-)
Current coverage is 94.24% (diff: 100%)@@ master #474 diff @@
==========================================
Files 161 161
Lines 21255 21255
Methods 0 0
Messages 0 0
Branches 2277 2277
==========================================
Hits 20032 20032
Misses 802 802
Partials 421 421
|
Don't advise sudo, it's a terrible idea. Make clear the difference between a "source" install and a "development" install.
matthew-brett
force-pushed
the
better-installation-advice
branch
from
8476cb2 to
24223f7
Compare
|
I'm not sure what to make of the Donald Stufft article - I guess that we should expect The datalad idea as I understand it is to add So, yes, maybe. I wish I had a clearer feeling for how |
|
On Sat, 06 Aug 2016, Matthew Brett wrote:
or more "to pin point specific versions in particular deployments"
yeap. This way, for instance, pip install nibabel could install the |
|
OK to leave better requirements handling for a later PR? |
|
if you mean "let's merge this one now and improve later with another PR", then +1 on my side ;) |
Don't advise sudo, it's a terrible idea.
Make clear the difference between a "source" install and a "development"
install.