Skip to content

FutureWarning with Numpy 1.10 #5806

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.

Sign up for GitHub

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

Jump to bottom
Closed
divenex opened this issue Jan 6, 2016 · 1 comment
Closed

FutureWarning with Numpy 1.10 #5806

divenex opened this issue Jan 6, 2016 · 1 comment
Milestone
v2.1

Comments

@divenex
Copy link

divenex commented Jan 6, 2016

I found a couple of FutureWarning on Windows with Python 3.5.1, Numpy 1.10.1, Matplotlib 1.5.0. These were not present with Numpy 1.9.

Here is a minimal working example:

import numpy as np
import matplotlib.pyplot as plt

asp = np.array([1])
plt.subplot(111, aspect=asp)

mrk = np.array([[0, 0], [1, 0], [1, 1], [0, 1]])
plt.plot([0.3, 1.7, 0.6], marker=mrk, ms=30)

The resulting output is

Miniconda3\lib\site-packages\matplotlib\axes\_base.py:1209: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
    if aspect == 'normal':
Miniconda3\lib\site-packages\matplotlib\axes\_base.py:1214: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
    elif aspect in ('equal', 'auto'):
Miniconda3\lib\site-packages\matplotlib\lines.py:851: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
    if self._marker.get_marker() in ('.', ','):
Miniconda3\lib\site-packages\matplotlib\lines.py:801: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
    if marker.get_marker() != ',':
@jenshnielsen
Copy link
Member

Thanks there are a bunch of numpy warnings that we need to fix. There are also some in #5363 which are similar

@u55 u55 mentioned this issue May 26, 2016
Closed
@dstansby dstansby mentioned this issue Dec 21, 2016
Merged
@QuLogic QuLogic added this to the 2.1 (next point release) milestone Dec 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v2.1
Development

No branches or pull requests
3 participants
@QuLogic @jenshnielsen @divenex