honnix
12/19/2022, 9:44 AM10:37:44.889 .tox/py38-test/lib/python3.8/site-packages/flytekit/__init__.py:195: in <module>
10:37:44.889 from flytekit.types import directory, file, numpy, schema
10:37:44.889 .tox/py38-test/lib/python3.8/site-packages/flytekit/types/schema/__init__.py:1: in <module>
10:37:44.889 from .types import (
10:37:44.889 .tox/py38-test/lib/python3.8/site-packages/flytekit/types/schema/types.py:314: in <module>
10:37:44.889 class FlyteSchemaTransformer(TypeTransformer[FlyteSchema]):
10:37:44.889 .tox/py38-test/lib/python3.8/site-packages/flytekit/types/schema/types.py:324: in FlyteSchemaTransformer
10:37:44.889 _np.bool: SchemaType.SchemaColumn.SchemaColumnType.BOOLEAN, # type: ignore
10:37:44.889 .tox/py38-test/lib/python3.8/site-packages/numpy/__init__.py:284: in __getattr__
10:37:44.889 raise AttributeError("module {!r} has no attribute "
10:37:44.889 E AttributeError: module 'numpy' has no attribute 'bool'
In numpy 1.24.0 release note:
The deprecation for the aliases np.object, np.bool, np.float,
np.complex, np.str, and <http://np.int|np.int> is expired (introduces NumPy
1.20). Some of these will now give a FutureWarning in addition to
raising an error since they will be mapped to the NumPy scalars in
the future.
bool
(and other built-in types) according to
_msg = (
"`np.{n}` is a deprecated alias for the builtin `{n}`. "
"To silence this warning, use `{n}` by itself. Doing this will not "
"modify any behavior and is safe. {extended_msg}\n"
"Deprecated in NumPy 1.20; for more details and guidance: "
"<https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations>")
Samhita Alla
Eduardo Apolinario (eapolinario)
12/19/2022, 4:35 PMhonnix
12/20/2022, 8:11 AMEduardo Apolinario (eapolinario)
12/20/2022, 3:02 PMVictor Gustavo da Silva Oliveira
01/13/2023, 3:24 PMEduardo Apolinario (eapolinario)
01/13/2023, 4:42 PM