summaryrefslogtreecommitdiff
path: root/numpy
diff options
context:
space:
mode:
authorSebastian Berg <sebastianb@nvidia.com>2022-11-21 09:10:02 +0100
committerSebastian Berg <sebastianb@nvidia.com>2022-11-21 09:10:02 +0100
commitd41658143d15dfe2f17ad7fd11467dcdba9c3070 (patch)
tree3f131cdc79d5afc26412aa8034b594babba02c43 /numpy
parent424cb3fa1fd7c1aa10aaa55c195f0ef7091fc71f (diff)
downloadnumpy-d41658143d15dfe2f17ad7fd11467dcdba9c3070.tar.gz
DOC: Adjust comments on deprecated/future scalar alias based on review
Diffstat (limited to 'numpy')
-rw-r--r--numpy/__init__.py8
1 files changed, 5 insertions, 3 deletions
diff --git a/numpy/__init__.py b/numpy/__init__.py
index a756d07a8..bdea595ed 100644
--- a/numpy/__init__.py
+++ b/numpy/__init__.py
@@ -159,7 +159,7 @@ else:
_msg = (
"`np.{n}` is a deprecated alias for `{an}`. (Deprecated NumPy 1.24)")
- # Some of these are awkard (since `np.str` may be preferable in the long
+ # Some of these are awkward (since `np.str` may be preferable in the long
# term), but overall the names ending in 0 seem undesireable
_type_info = [
("bool8", bool_, "np.bool_"),
@@ -173,8 +173,10 @@ else:
"`object` can be used instead. (Deprecated NumPy 1.24)")]
# Some of these could be defined right away, but most were aliases to
- # the Python objects before. When defined, these should possibly not
- # be added to `__all__` to avoid import with `from numpy import *`.
+ # the Python objects and only removed in NumPy 1.24. Defining them should
+ # probably wait for NumPy 1.26 or 2.0.
+ # When defined, these should possibly not be added to `__all__` to avoid
+ # import with `from numpy import *`.
__future_scalars__ = {"bool", "long", "ulong", "str", "bytes", "object"}
__deprecated_attrs__.update({