Skip to content

Numpy deprecation warning in test_buffer.py #96742

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
pitrou opened this issue Sep 10, 2022 · 3 comments
Closed

Numpy deprecation warning in test_buffer.py #96742

pitrou opened this issue Sep 10, 2022 · 3 comments
Labels
type-bug An unexpected behavior, bug, or error

Comments

@pitrou
Copy link
Member

pitrou commented Sep 10, 2022

Bug report

When running test_buffer.py on the main branch with Numpy installed, the following warnings are displayed:

0:00:00 load avg: 0.29 Run tests sequentially
0:00:00 load avg: 0.29 [1/1] test_buffer
/home/antoine/cpython/default/Lib/test/test_buffer.py:2298: DeprecationWarning: tostring() is deprecated. Use tobytes() instead.
  self.assertEqual(b, na.tostring(order='C'))
/home/antoine/cpython/default/Lib/test/test_buffer.py:2321: DeprecationWarning: tostring() is deprecated. Use tobytes() instead.
  self.assertEqual(b, na.tostring(order='F'))
/home/antoine/cpython/default/Lib/test/test_buffer.py:2345: DeprecationWarning: tostring() is deprecated. Use tobytes() instead.
  self.assertEqual(b, na.tostring(order='A'))

== Tests result: SUCCESS ==

A clear and concise description of what the bug is.
Include a minimal, reproducible example (https://stackoverflow.com/help/minimal-reproducible-example), if possible.

Your environment

Numpy version 1.23.3, installed from source on a debug build of the CPython main branch.

@pitrou pitrou added the type-bug An unexpected behavior, bug, or error label Sep 10, 2022
@pitrou
Copy link
Member Author

pitrou commented Sep 10, 2022

cc @corona10

@corona10
Copy link
Member

corona10 commented Sep 10, 2022

Oops, I pushed the change to e8c1fed at #96738 already.
If you want to handle it separately please let me know.

@pitrou
Copy link
Member Author

pitrou commented Sep 10, 2022

No, it's fine to me. Thanks!

@pitrou pitrou closed this as not planned Won't fix, can't repro, duplicate, stale Sep 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

No branches or pull requests

2 participants