Conversation
tldahlgren
left a comment
There was a problem hiding this comment.
Confirmed the sha256.
|
Also being updated in #35195 |
|
@spackbot run pipeline |
|
I've started that pipeline for you! |
|
I'm fine with updating it separately but this PR is missing some of the changes in the other PR (upper bounds on dep versions, etc.). If you want to steal them from that PR go ahead. |
f95e61c to
a001ced
Compare
|
I've pushed a new version that should now also include the correct upper bounds. I've left the setuptools@61: dependency commented out since that seems to cause problems for @kwryankrattiger. |
a001ced to
7b7a46e
Compare
|
I am okay with it being separate, I wasn't too thrilled about updating it in #35195 since it is outside of the scope of the changes in there. |
7b7a46e to
4e641f1
Compare
4cd1d12 to
40c13ec
Compare
|
The pinning is kind of a workaround - we aim to ensure it builds with an
older version, and then it will be compatible with newer versions at
runtime. The pinned versions are roughly the first mpi4py versions that
will conveniently work for each python version. I imagine that Spack has
better ways to express this stuff.
Needless to say, our own package metadata is a compromise between a pure
description and making things work for python tools which use that metadata
directly.
…On Sat, 11 Mar 2023, 21:31 Adam J. Stewart, ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In var/spack/repos/builtin/packages/py-h5py/package.py
<#35960 (comment)>:
> depends_on("py-six", type=("build", "run"), when="@:2")
# Link dependencies (py-h5py v2 cannot build against HDF5 1.12 regardless
# of API setting)
***@***.***:1.11 +hl", when="@:2")
- ***@***.***:1.12 +hl", ***@***.***:")
+ ***@***.***:1.12 +hl", ***@***.***:3.7")
+ ***@***.***:1.14 +hl", ***@***.***:")
# MPI dependencies
depends_on("hdf5+mpi", when="+mpi")
mpi4py dep needs to be updated too:
RUN_REQUIRES.append('mpi4py >=3.0.2')
SETUP_REQUIRES.append("mpi4py ==3.0.2; python_version<'3.8'")
SETUP_REQUIRES.append("mpi4py ==3.0.3; python_version=='3.8.*'")
SETUP_REQUIRES.append("mpi4py ==3.1.0; python_version=='3.9.*' or python_version=='3.10.*'")
SETUP_REQUIRES.append("mpi4py ==3.1.4; python_version>='3.11'")
Honestly, this stuff is kinda annoying to track. Not sure why things need
to be pinned to a specific version for each Python release. Should we just
ignore this and say ***@***.***: for all versions? Curious what
@bryanherman <https://github.com/bryanherman> @takluyver
<https://github.com/takluyver> think.
—
Reply to this email directly, view it on GitHub
<#35960 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACQB5J3HTN2D3QVQJILOFDW3TVKXANCNFSM6AAAAAAVU4MAZI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
In that case I'll let @michaelkuhn decide what to do. It sounds like
I'm guessing this means the first version where wheels are available, not the first version that supports that Python version? If it was the latter I would add these to the py-mpi4py package so we can remove old versions when we deprecate Python versions. |
That would be my guess too, though I don't know that we've applied that rule completely consistently. |
40c13ec to
b6fe825
Compare
|
Sorry for dropping the ball on this. I've just pushed a new version that constrains |
b6fe825 to
1cdec63
Compare
adamjstewart
left a comment
There was a problem hiding this comment.
Looks fine to me as long as the other 2 maintainers don't see any issues.
|
LGTM. The precisely versioned dependencies on numpy and Cython could probably be simplified, like with mpi4py (discussed above). They're similar cases where we've found compromises between a pure theoretical description of dependencies, and what practically works for Python-native tooling. But if they're not causing an issue, you may just want to leave them as they are and not risk breaking anything. |
|
@spackbot run pipeline |
|
I've started that pipeline for you! |
|
if no objections in the next couple hours, I am going to merge this today. |
No description provided.