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

Fix deprecations from NumPy #1122

Merged
merged 2 commits into from
Sep 25, 2018
Merged

Conversation

QuLogic
Copy link
Member

@QuLogic QuLogic commented Sep 25, 2018

This fixes several deprecation warnings from NumPy when running the tests:

cartopy/lib/cartopy/tests/test_polygon.py:257: DeprecationWarning: In future, it will be an error for 'np.bool_' scalars to be interpreted as an index
  for i in range(boundary[0], regions.max(), 2):

cartopy/lib/cartopy/img_transform.py:76: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  endpoint=False)
cartopy/lib/cartopy/img_transform.py:78: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  endpoint=False)

cartopy/lib/cartopy/img_transform.py:76: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  endpoint=False)
cartopy/lib/cartopy/img_transform.py:78: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  endpoint=False)
cartopy/lib/cartopy/img_transform.py:76: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  endpoint=False)
cartopy/lib/cartopy/img_transform.py:78: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  endpoint=False)

cartopy/lib/cartopy/img_transform.py:76: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  endpoint=False)

cartopy/lib/cartopy/img_transform.py:76: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  endpoint=False)

cartopy/lib/cartopy/img_transform.py:76: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  endpoint=False)

cartopy/lib/cartopy/img_transform.py:78: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  endpoint=False)

cartopy/lib/cartopy/img_transform.py:76: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  endpoint=False)

cartopy/lib/cartopy/img_transform.py:76: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  endpoint=False)

cartopy/lib/cartopy/img_transform.py:76: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  endpoint=False)

cartopy/lib/cartopy/vector_transform.py:63: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  x_grid, y_grid = np.meshgrid(np.linspace(0, 1, nx),

code/cartopy/lib/cartopy/vector_transform.py:63: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  x_grid, y_grid = np.meshgrid(np.linspace(0, 1, nx),

cartopy/lib/cartopy/vector_transform.py:63: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  x_grid, y_grid = np.meshgrid(np.linspace(0, 1, nx),

code/cartopy/lib/cartopy/vector_transform.py:63: DeprecationWarning: object of type <class 'numpy.float64'> cannot be safely interpreted as an integer.
  x_grid, y_grid = np.meshgrid(np.linspace(0, 1, nx),

@QuLogic QuLogic added this to the 0.17 milestone Sep 25, 2018
@ajdawson ajdawson merged commit d9c2373 into SciTools:master Sep 25, 2018
@QuLogic QuLogic deleted the fix-deprecations branch September 25, 2018 19:52
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.

2 participants