Repository navigation
Version 1.6.1: install the numpy and MeshPy the package works with #120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -81,8 +81,8 @@ def find_version(*fname): | |
| 'pybind11', # must come before meshpy for successful install | ||
| 'lsq-ellipse', | ||
| 'matplotlib>=3.4.0', | ||
| 'meshpy>=2018.2.1', | ||
| 'numpy>=1.22.2', | ||
| 'meshpy>=2018.2.1,<2026', # TetGen of 2026 exceeds max_volume | ||
| 'numpy>=1.22.2,<2', # numpy 2 breaks the mesh text files | ||
|
Owner
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The ceilings are right and I confirmed the problem they fix. A clean Worth saying out loud how visible the first group is. Three of the seven I also checked that both ceilings are needed. With numpy held below 2, One thing to add while you are here. This package has no numpy below 2 has no releases for Python 3.13 or later, as you note. With python_requires='>=3.9,<3.13',turns that into one readable line, and it matches the classifiers. It also |
||
| 'pygmsh>=7.0.2', | ||
| 'pyquaternion', | ||
| 'pyvoro-rimoli>=1.4.0', # pyvoro with the current Voro++ | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,4 +4,4 @@ | |
| import microstructpy.seeding | ||
| import microstructpy.verification | ||
|
|
||
| __version__ = '1.6.0' | ||
| __version__ = '1.6.1' | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the unpinned CI job you suggest doing after this release: I would land
it with this PR instead.
The argument is this release itself. 1.6.0 went to PyPI with 224 tests
passing and was broken for every user who installed it the normal way.
Nothing in the pipeline was capable of noticing, because every job installs
requirements.txtfirst and the pins there hide whatinstall_requiresresolves to. The ceilings in this PR fix the versions we know about today.
They do not give CI the ability to see the next pair.
The gap is narrow and so is the job. One matrix entry that skips
requirements.txt:with an
unpinned: trueentry added to the matrix, andcontinue-on-errorif you would rather it warns than blocks at first. Even as a warning it
would have caught this one, since the failure is 13 tests and not a
subtlety.
The reason I would not defer it is that the cost of the miss is already
known. A broken release is public, it needs a second release to undo, and
the people who hit it are the ones who installed the package for the first
time.