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
In practice, I came across this quirk whilst writing the conda-forge recipe for a package that depends on meshio in addition to other packages that require numpy<1.20.0. Pinning the numpy version in this example replicates the "other package" requirements.
Diagnose
I may ask you to cut and paste the output of the following command.
pip freeze | grep meshio
Output is meshio==5.3.4.
Did I help?
If I was able to resolve your problem, consider sponsoring my work on meshio, or buy me a coffee to say thanks.
The text was updated successfully, but these errors were encountered:
Describe the bug
The
numpy
dependency (min 1.20.0) formeshio
version 5.3.4 is not respected bypip
orconda
installs.As such, it is possible to obtain an environment in which the bug in #1283 is present and not flagged by tools such as
pip check
, for example.To Reproduce
Minimal steps to reproduce:
In a clean mamba/conda environment with python 3.9, running
will report a successful import of meshio version 5.3.4. However, then attempting to import meshio using the Python interpreter:
raises
ModuleNotFoundError: No module named 'numpy.typing'
, as per #1283.Attached is a log replicating this bug using
mamba install
and usingpip
.In practice, I came across this quirk whilst writing the
conda-forge
recipe for a package that depends onmeshio
in addition to other packages that requirenumpy<1.20.0
. Pinning the numpy version in this example replicates the "other package" requirements.Diagnose
I may ask you to cut and paste the output of the following command.
Output is
meshio==5.3.4
.Did I help?
If I was able to resolve your problem, consider sponsoring my work on meshio, or buy me a coffee to say thanks.
The text was updated successfully, but these errors were encountered: