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

NumPy deprecation #176

Open
pedrocamargo opened this issue May 29, 2023 · 1 comment · May be fixed by #177
Open

NumPy deprecation #176

pedrocamargo opened this issue May 29, 2023 · 1 comment · May be fixed by #177

Comments

@pedrocamargo
Copy link

There are two instances of the use of np.int , which has been deprecated:

  1. sub_control_totals = np.asanyarray(self.sub_controls_df).astype(np.int)

  2. sub_weights.shape, dtype=np.int),

according to NumPy's error message:

AttributeError: module 'numpy' has no attribute 'int'.
np.int was a deprecated alias for the builtin int. To avoid this error in existing code, use int by itself. Doing this will not modify any behavior and is safe. When replacing np.int, you may wish to use e.g. np.int64 or np.int32 to specify the precision. If you wish to review your current use, check the release note link for additional information.
The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at:
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations

@pedrocamargo pedrocamargo linked a pull request May 29, 2023 that will close this issue
@bettinardi bettinardi added this to the Phase 9 Priorities milestone Oct 6, 2023
@bettinardi
Copy link
Collaborator

It looks like this will be resolved by resolving the pull request - hoping this can be closed under a Phase 9 push.

@bettinardi bettinardi added the bug label Oct 6, 2023
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.

2 participants