-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
DOC: Move ecosystem.rst to getting started section #52944
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
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.
The ecosystem page is duplicated, we have a copy in the website and this one in the docs. Not sure which one is more updated, or if additions arbitrarily go to any of them.
Personally I think we should only keep the website one. The reason we've got independent website and docs is that we want to have the release specific documentation versioned, while having the website being updated immediately once there is a change. I think the ecosystem is an obvious case where we want have a single updated ecosystem page, and not one per pandas release.
No objection to this PR, just saying that maybe a good time to remove this page instead of moving it?
Agreed with only keeping the website version of the ecosystem docs. I unioned the two and fixed the old references we had to the |
Going to merge this cleanup, but happy to address any followups |
* DOC: Move ecosystem.rst to getting started section * Also error on ipython warnings * Migrate existing ecosystem to web and fix references
* DOC: Move ecosystem.rst to getting started section * Also error on ipython warnings * Migrate existing ecosystem to web and fix references
* DOC: Move ecosystem.rst to getting started section * Also error on ipython warnings * Migrate existing ecosystem to web and fix references
So it makes
ecosystem
discoverable from the docs navigation.Also removes an unused tips.csv and
ipython_warning_is_error
(which is enforced by our build error on warnings)