-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
MNT skip preprocessing.rst when pandas is not installed #19016
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
Out of curiosity do you have a direct URL of the CI failure? |
https://app.circleci.com/jobs/github/scikit-learn/scikit-learn/127838 Uhm it seems that we don't launch pypy on the PR. I have to find the flag then. |
We do not have a flag for scikit-learn/.circleci/config.yml Lines 159 to 165 in 38b7155
to test the PR. |
Thanks, I was starting the read the documentation. |
Uhm why do we have the following: - pypy3:
filters:
branches:
only:
- 0.20.X I mean this is weird to only test branches only on 0.20.X |
AFAIK, we do not have information in the documentation of how to trigger the
FYI: #13023. |
This was my feeling. Pandas does not work well in PyPy |
we should probably skip the line then |
So I marked to skip to part where Pandas is required. |
I change the strategy to be consistent with the current pattern that is to skip the |
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.
It is slightly disappointing that we have to turn off doctests because there was a new section using pandas.
Codewise this LGTM
Be aware that it happens only on some of the builds. Basically, we still test the doctests and this file on the build where pandas is installed. |
I am aware, especially when writing docs. I have been trying to avoid using new optional dependencies when writing the docs because of the need to skip. However, I think it's not too bad to skip for this PR. |
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!
We could move the new section to a dedicated |
BTW, I think we should not run the doctests on the pypy build. The pypy build is already much to slow. It's just a waste of resource. The primary goal of the doctests it to make sure that the inline examples are up to date with respect of the rest of the code base and this is already checked by running the doctests on the default CPython jobs. |
I agree.
…On Fri, 18 Dec 2020 at 11:19, Olivier Grisel ***@***.***> wrote:
BTW, I think we should not run the doctests on the pypy build. The pypy
build is already much to slow. It's just a waste of resource.
The primary goal of the doctests it to make sure that the inline examples
are up to date with respect of the rest of the code base and this is
already checked by running the doctests on the default CPython jobs.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#19016 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABY32P3XZC2TYNZJB725ZJDSVMUDJANCNFSM4U5UAWMA>
.
--
Guillaume Lemaitre
Scikit-learn @ Inria Foundation
https://glemaitre.github.io/
|
Try to fix master by installing pandas.