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
10: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 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.
Expected behavior
flytekit should work, either by pinning numpy or being compatible with 1.24.0
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Yes
Have you read the Code of Conduct?
Yes
The text was updated successfully, but these errors were encountered:
Describe the bug
In numpy 1.24.0 release note:
Expected behavior
flytekit should work, either by pinning numpy or being compatible with 1.24.0
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: