-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: Add datatest package to list of third-party extension accessors. #38593
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
I'm not sure what to make of this. The changes I made don't seem to be an issue according to the "Build documentation" logs:
The successful build used Sphinx v3.3.1 and the failing build used Sphinx v3.4.0. In the successful build, there are warnings emitted after the success. But in the failing build, these same warnings are emitted during the process--causing it to fail. EDIT: Correction, there are additional warnings in the failing build that aren't in the passing build (see following comment). |
This seems to be happening for files totally unrelated to the change. The failing Build documentation step emits warnings that the passing build did not. This seems to have started with the newly published Sphinx v3.4.0 (released earlier today). The new warnings are as follows:
|
Here's the changelog for Sphinx 3.4.0: https://www.sphinx-doc.org/en/master/changes.html#release-3-4-0-released-dec-20-2020 |
e should pin sphinx to the earlier version want to do a PR? |
Sure. I'll post in a minute. |
thanks @shawnbrown |
This change adds the
datatest
package to the list of third-party extension accessors. Sincedatatest
supports more thanpandas
, I wasn't sure if it was appropriate to add it to the Data cleaning and validation section, so I only added it to the accessors list for now.Unfortunately, the "Classes" column was not wide enough--so this patch affects all rows in the table. This shouldn't happen again as the column is now wide enough to accommodate all of the classes that support extension accessors.