-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
DOC: Update install docs for Spyder #12716
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
Conversation
|
Updated pages: installers and IDEs. |
drammock
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but @hoechenberger should probably have the final say.
|
Thanks @larsoner Also I think having the VS Code instructions in installer.rst emphasizes that we consider VS Code the IDE of choice, even for installer users 🤔 |
So our old / current instructions have this on the main page: Is this what you mean? What is there now is: I don't think this is appreciably harder for the user, and it's more general (works on Windows!). But I guess I could add a note that the prompt might already tell you this information on some systems.
Sure but having duplicated instructions isn't great. I'll rephrase to emphasize / suggest |
|
@hoechenberger is this better? If so I'll push, if not let me know how you think it could be improved And instructions |
I don't think we should be too forceful/opinionated here. Lots of folks like Spyder and PyCharm, and for some users, the best reason for picking a particular IDE is that someone else in your lab / department / institute uses it and can help you if you get stuck. I'm OK with @larsoner's suggestion of:
but I don't think we should get any more forceful than that. |
|
@hoechenberger is this version okay? |
|
I like this consolidated view, thanks Eric |




The bulk of this has to do with us no longer packaging Spyder in our installers and adjusting the install docs (mostly) minimally to comply with this change. #10707 and #11615 for example ask for something more comprehensive and aren't meant to be addressed here. This does help a tiny bit (maybe!) with #10707 in the sense that it deduplicates some stuff. I also snuck in a couple of tiny single-digit-line changes to close three other issues:
numpy<3compute_rankoperates on data channels@hoechenberger for the Spyder stuff, think this is good enough?
Closes #12672
Closes #12705
Closes #11540
Closes #11482