8000 Deprecation warnings about object arrays in wheel build. · Issue #15044 · numpy/numpy · GitHub
[go: up one dir, main page]

Skip to content

Deprecation warnings about object arrays in wheel build. #15044

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

Closed
charris opened this issue Dec 4, 2019 · 9 comments
Closed

Deprecation warnings about object arrays in wheel build. #15044

charris opened this issue Dec 4, 2019 · 9 comments
Labels

Comments

@charris
Copy link
Member
charris commented Dec 4, 2019

See https://travis-ci.org/MacPython/numpy-wheels/jobs/620443138 for examples.

Reproducing code example:

import numpy as np
<< your code here >>

Error message:

Numpy/Python version information:

@charris
Copy link
Member Author
charris commented Dec 4, 2019

Not sure why these warnings are not raising an error.

EDIT: They also don''t show up on my machine with runtests.py.

@mattip 8000
Copy link
Member
mattip commented Dec 4, 2019

The CI logs say it is using a wheel from this directory but I do not see the wheel there. I wanted to try it out locally. Is it somehow removed?

@charris
Copy link
Member Author
charris commented Dec 4, 2019

You need the pre-release builds: https://7933911d6844c6c53a7d-47bd50c35cd79bd838daf386af554a83.ssl.cf2.rackcdn.com/.

I'm thinking this might an artifact of using Python3.6 on bionic as the driving python. I'm testing the release branch now, it uses the old setup with Python3.5 on trusty.

@mattip
Copy link
Member
mattip commented Dec 4, 2019

Thanks for the link, the wheel used in CI shows up there.

In CI, it seems multibuild short-curciuts pip install and uses a file on the local filesystem see multibuild/common_utils/install_wheel (which calls python to find the local file)

In any case I would be surprised if the driving python and OS play any part, since this is all supposed to happen inside a multibuild docker

@charris
Copy link
Member Author
charris commented Dec 4, 2019

Yep, the warnings don't show up on the release branch. Hmm...

8000

@rgommers
Copy link
Member
rgommers commented Dec 4, 2019

That CI log is plain confusing. The daily wheel job simply builds a wheel locally, installs it (see here), runs the tests and only uploads it in the after_success step.

@charris
Copy link
Member Author
charris commented Dec 4, 2019

I'm off to bed, at least the release branch is not troublesome.

@mattip
Copy link
Member
mattip commented Dec 4, 2019

Found it: the test is creating a ragged array sorter here. That test has been there since 2013 or so. There must be some interaction with assert_raises masking the warning.

@seberg
Copy link
Member
seberg commented Jul 14, 2021

This issue was specitic to the 1.18 release and seemed to be fixed by revert. Closing.

@seberg seberg closed this as completed Jul 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
0