Skip to content
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

Use is to compare with None in backend_pdf #3718

Merged
merged 1 commit into from
Oct 26, 2014

Conversation

jenshnielsen
Copy link
Member

Fixes some of the Numpy future warnings raised with numpy 1.9

The remaining ones are thrown from the Capi inside _tri.cpp and are likely related to the use of PyCXX. I don't think that there is much point in fixing them if the plan is to replace the use of PyCXX with the pure Python Capi

@ianthomas23
Copy link
Member

@jenshnielsen: I am working on removing PyCXX from _tri and will hopefully issue a PR tomorrow.

@jenshnielsen
Copy link
Member Author

@ianthomas23 Great stuff. This was not to put any pressure on you. Just to say that it was a waste of time to investigate the warnings in the present code.

tacaswell added a commit that referenced this pull request Oct 26, 2014
ENH : Use is to compare with None in backend_pdf
@tacaswell tacaswell merged commit bf29166 into matplotlib:master Oct 26, 2014
@jenshnielsen jenshnielsen deleted the numpy_None_warnings branch October 28, 2014 17:35
tacaswell added a commit that referenced this pull request Dec 12, 2014
ENH : Use is to compare with None in backend_pdf
@tacaswell
Copy link
Member

backported as 431edb7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants