You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running test with python 3.12, I noticed various Deprecation Warnings, one outside the scope of pydap, and the others within pydap. These are
Within scope of pydap:
pkg_resources. Largely resolved by Solve pkg_resources DeprecationWarning #290, but care must be taken about the way namespaces are being discovered & imported with pydap (pydap/handlers/lib.py).
For package outside of scope of pydap: It will surely take sometime before python 3.13 arrives. It looks like the devs of webob are aware of this via webob#437. We should simply suppress this Deprecation warning on the pyproject.toml (otherwise the warning will appear in other packages that may depend on pydap).
For the other ones, I will spend some time. Some of them can be fixed easily. But two or more will require some effort.
The text was updated successfully, but these errors were encountered:
Description
Running test with python 3.12, I noticed various
Deprecation Warnings
, one outside the scope ofpydap
, and the others within pydap. These areWithin scope of pydap:
pydap/handlers/lib.py
).Outside scope of pydap
Solution method
For package outside of scope of pydap: It will surely take sometime before python 3.13 arrives. It looks like the devs of webob are aware of this via webob#437. We should simply suppress this
Deprecation warning
on the pyproject.toml (otherwise the warning will appear in other packages that may depend on pydap).For the other ones, I will spend some time. Some of them can be fixed easily. But two or more will require some effort.
The text was updated successfully, but these errors were encountered: