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
{{ message }}
Repository navigation
Commit 6f0ce9e
Browse filesBrowse the repository at this point in the historyBrowse files
Version 1.6.1: install the numpy and MeshPy the package works with (#120)
setup.py asked for numpy>=1.22.2 and meshpy>=2018.2.1, so pip
installed microstructpy 1.6.0 with numpy 2.5 and MeshPy 2026.1, while
the continuous integration installs requirements.txt, which pins numpy
below 2 and MeshPy 2022.1.3. With those newest versions, 13 of the 224
tests fail. With numpy 2, the text files of the meshes cannot be read
back (numpy writes integers as np.int64(4)) and tangent_sphere fails.
With MeshPy 2026, TetGen lets 3D elements exceed max_volume.
setup.py now asks for numpy<2 and meshpy<2026. Installed that way, pip
takes numpy 1.26.4 and MeshPy 2025.1.1 (2022.1.3 on Python 3.9), and
all 224 tests pass. numpy below 2 has no wheels for Python 3.13 and
later, but pip builds it from source there; on Python 3.14 that takes
under a minute, and all the tests pass.
One more CI job, Python 3.12 on Ubuntu, skips requirements.txt and
installs the package alone, as pip install microstructpy does, so that
the tests see the dependency versions that users get. It does not
upload coverage, which the pinned job of the same Python and system
already reports. Suggested by Kip Hart in the review.
The changelog has a 1.6.1 section, __version__ is 1.6.1, and the example
digest of the documentation is updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0 commit comments