-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Pick and choose numpy version based on Python 2 or 3. #28511
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
Thanks for the PR! Hmm, there a couple of failures. Not directly related to your change, but related to the fact that we didn't run those tests (at the state of 0.24.2) for some time, and fixes have been made for changed dependencies. There also seem to be some actual failures with numpy 1.17, so an option could be to restrict it to lower versions also for python 3 ? |
Thanks for the quick response. Do you have documented versions of what the maximum versions pandas should have on Python 3? |
I haven't looked at the failures, but are they actual, noticeable bugs, or
just failures in the test?
If they're real issues then we can just have pandas 0.24.x require NumPy
<1.17 across the board.
…On Thu, Sep 19, 2019 at 12:44 PM Didip Kerabat ***@***.***> wrote:
Thanks for the quick response.
Do you have documented versions of what the maximum versions pandas should
have on Python 3?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#28511?email_source=notifications&email_token=AAKAOITOQJNDPWJTJBLZRO3QKO26PA5CNFSM4IYDXLM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7EIVHI#issuecomment-533236381>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKAOIUASZO5KC2EJDTIHATQKO26PANCNFSM4IYDXLMQ>
.
|
Part of them are certainly test failures, but it seems there are also actual bugs (although someone needs to investigate it more in detail to be sure):
But it might be more a corner case anyway. |
Actually, I was looking at the numpy dev build. Most of the other build failures seem to be problems getting the environment installed (missing packages etc), like the python 2.7 build on Azure:
Note sure how much effort we should do to get those CIs running again .. |
Yeah, numpydev can certainly be ignored.
For the rest, perhaps try adding back the `free` channel in each
environment that needs it?
…On Thu, Sep 19, 2019 at 1:54 PM Joris Van den Bossche < ***@***.***> wrote:
Actually, I was looking at the numpy dev build. Most of the other build
failures seem to be problems getting the environment installed (missing
packages etc), like the python 2.7 build on Azure:
Solving environment: ...working... failed
ResolvePackageNotFound:
- xlsxwriter=0.5.2
- pytz=2013b
- python-dateutil=2.5.0
- xlwt=0.7.5
Note sure how much effort we should do to get those CIs running again ..
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#28511?email_source=notifications&email_token=AAKAOIRXC2E4C3BPFKJZM5TQKPDFZA5CNFSM4IYDXLM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7EPEMA#issuecomment-533262896>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKAOIV27MQSLBV63ZUB6JLQKPDFZANCNFSM4IYDXLMQ>
.
|
Codecov Report
@@ Coverage Diff @@
## 0.24.x #28511 +/- ##
===========================================
- Coverage 92.39% 42.91% -49.49%
===========================================
Files 166 166
Lines 52430 52430
===========================================
- Hits 48443 22499 -25944
- Misses 3987 29931 +25944
Continue to review full report at Codecov.
|
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.
Thanks for the fixing this @didip. Can you remove the tailing whitespace that is breaking the CI, and check the styling comment?
|
||
numpy_install_rule = 'numpy >= {numpy_ver}'.format(numpy_ver=min_numpy_ver) | ||
if max_numpy_ver: | ||
numpy_install_rule += ', < {numpy_ver}'.format(numpy_ver=max_numpy_ver) |
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.
Just a style preference, but what fo you think about the less verbose option:
numpy_requires = 'numpy >= {min_numpy_ver}{max_numpy_rule}'.format(
min_numpy_ver=min_numpy_ver,
max_numpy_rule=', < {}'.format(max_numpy_ver_py2) if sys.version_info[0] < 3 else '')
Also, if you can please merge master into this branch. |
I think this is targeting 0.24.x directly, since we don't want these changes on master. |
Agree with @TomAugspurger |
We still need the linting issues fixed though.
…On Mon, Oct 7, 2019 at 11:41 AM Didip Kerabat ***@***.***> wrote:
Agree with @TomAugspurger <https://github.com/TomAugspurger>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#28511?email_source=notifications&email_token=AAKAOIWZ32LSX4LVKAQ5IELQNNRCBA5CNFSM4IYDXLM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEARAMAA#issuecomment-539100672>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKAOIQRLK3TQUGZNE7KR2TQNNRCBANCNFSM4IYDXLMQ>
.
|
Yes, I’ll try to find sometime today to address it. |
Where is the CI/CD output that shows failed linting? This one? https://github.com/pandas-dev/pandas/pull/28511/checks?check_run_id=229464786 |
yes, but the build is too old and is not available anymore. You can run |
There are tons of lint problems when running |
Not quite sure what's the problem with the docstrings, but you've also got this error in the CI Do you mind having a look @didip. We can't merge this until the CI is green. |
At this point we don't have any further plans for a 24.x release, so unfortunately I don't think this is something we will address (if anyone disagrees feel free to reopen) |
As far as I recall, we said to give the opportunity to interested contributors, so let's wait a bit more to see if @didip has time to update this. |
@didip it looks like some xfailed pytables tests need to be updated for the changes in this PR to work. can you take a look and update? |
…-end with 20 failures.
Upgraded |
Anything else I need to do? Is this good enough to merge? |
You'll need to get the tests passing. This can include xfailing if appropriate. |
@jbrockmendel They look unrelated though. Example:
|
Looking at azure, some of them seem to relate to numpy version and error messages. For the ones that are XPASS if this PR actually fixes those tests then you can un-xfail them. |
Ran All of them failed because the expectation and results are in the wrong order. Examples:
or another one:
|
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.
@didip happy to take this, but needs to pass the CI (and I know you tried to fix)
ping if you can get this too work.
@@ -31,7 +31,7 @@ nbsphinx | |||
numexpr>=2.6.8 | |||
openpyxl | |||
pyarrow>=0.9.0 | |||
tables>=3.4.2 | |||
tables>=3.5.2 |
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.
i don't think this would work because it would require a newer numpy than is allowed in this version (1.13)
@didip - thanks for the effort so far - do you still want to work on this? |
To be honest, I am running out of capacity to continue this work. I am completely unfamiliar with the build system to properly debug further problems. |
closing, but still happy for someone to push a PR to close this issue. |
black pandas
(not applicable,black setup.py
changes too many quotes, polluting the diff).git diff upstream/master -u -- "*.py" | flake8 --diff
cc @jorisvandenbossche