Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update install options #221

Merged
merged 5 commits into from
Oct 19, 2021
Merged

Conversation

rjleveque
Copy link
Member

Add a warning about issues with pip install, and more details about
what this does.

I also added more description of the differences between PyClaw and
the Python modules used by Fortran versions to the pyclaw/index.rst page.

@ketch, @mandli: Please take a look at the diffs and the draft rendered pages at

and let me know if these look ok.

I also removed the conda install discussion from the main pyclaw page, but it is still here:

I assume this should be removed?

You might also take a look at

We still recommend Anaconda and Enthought. Should this be updated?

Add a warning about issues with pip install, and more details about
what this does.
I also added more description of the differences between PyClaw and
the Fortran versions.
@rjleveque
Copy link
Member Author

I also just updated the recommended pip install command with --use-deprecated=legacy-resolver as suggested in clawpack/clawpack#203.

@xyleme
Copy link

xyleme commented Aug 24, 2021

Hello Randall,
just in case it can help, I run clawpack on a debian 11 box and had the same install issue as #203 trying to upgrade from 5.7 to 5.8. Adding the --use-deprecated argument to pip instruction solved my problem.
Thanks for this!
Vincent.

@ketch
Copy link
Member

ketch commented Aug 24, 2021

Thanks for adding the new argument. I think that we should also suggest something like "if you only plan to use PyClaw and/or Visclaw", you may wish to simply do

pip install --user clawpack

since that avoids some of the issues you are referring to. I would include this in the "warning" on installing.html. Or we could just suggest the python-only and fortran-only installation methods first (not as a warning) with the "everything" installation line as a secondary option, since it is the problematic one. I think it's rather discouraging to start the installation instructions with a warning, and I believe there are very few people in the world who care about installing both parts.

@rjleveque
Copy link
Member Author

@ketch
Copy link
Member

ketch commented Oct 5, 2021

The new version looks great to me. Thanks for doing this.

@rjleveque rjleveque merged commit 52f26f0 into clawpack:dev Oct 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants