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 2: VisibleDeprecationWarning is no longer accessible in the top module #3216

Open
jvesely opened this issue Feb 25, 2025 · 1 comment · Fixed by #3173
Open

Numpy 2: VisibleDeprecationWarning is no longer accessible in the top module #3216

jvesely opened this issue Feb 25, 2025 · 1 comment · Fixed by #3173
Assignees
Labels
deps Dependency update fixed-in-devel The issue is fixed in 'devel' branch and will be included in the next release

Comments

@jvesely
Copy link
Collaborator

jvesely commented Feb 25, 2025

Warnings and exceptions present in numpy.exceptions (e.g, ComplexWarning, VisibleDeprecationWarning) are no longer exposed in the main namespace.

[0] https://numpy.org/devdocs/release/2.0.0-notes.html#numpy-2-0-python-api-removals

@jvesely jvesely linked a pull request Feb 25, 2025 that will close this issue
@jvesely jvesely self-assigned this Feb 25, 2025
@jvesely
Copy link
Collaborator Author

jvesely commented Feb 25, 2025

This was addressed in #3173, but regressed again in #3204

jvesely added a commit to jvesely/PsyNeuLink that referenced this issue Feb 26, 2025
Instead of opencoding the same functionality.

Closes: PrincetonUniversity#3216
Fixes: beebd2a
	("Add support for batching to AutoDiffCompostion in PyTorch mode. (PrincetonUniversity#3204)")

Signed-off-by: Jan Vesely <jan.vesely@rutgers.edu>
@jvesely jvesely added the deps Dependency update label Feb 26, 2025
@jvesely jvesely added the fixed-in-devel The issue is fixed in 'devel' branch and will be included in the next release label Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deps Dependency update fixed-in-devel The issue is fixed in 'devel' branch and will be included in the next release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant