I agree this check is a pain and often useless, but why not just bump slurm and pyslurm atomically in PRs, as upstream intends? NixPkgs is ideally suited to be able to do this without too much hassle.

I agree that the version check might be a bit too strict for patch-level updates but removing it maybe won't help for major version jumps of slurm.
By removing the check we also bypass the QA of pyslurm.
I am not convinced that just removing it is the best solution.

Maybe @giovtorres can give some more insight, why pyslurm uses this version check the way it does?

I agree this check is a pain and often useless, but why not just bump slurm and pyslurm atomically in PRs, as upstream intends? NixPkgs is ideally suited to be able to do this without too much hassle.
You mean upgrading both packages at the same time?

This has been on my backlog for a while. I think it would be better to refactor the version check to instead check against MAJOR.MINOR version and ignore the check for the trailing .MICRO, which I concur has become unnecessary in the past couple Slurm releases. Would this help with your packaging?

See: PySlurm/pyslurm#137

@giovtorres Not checking the micro versions would certainly help. Would that also work for the minor version?

If I remember correctly, there's usually a small to fair amount of changes between releases, so much so that I think we would want to keep checking the minor version.

@giovtorres thanks for the fix.

@veprbl we can take PySlurm/pyslurm@d3703f2 instead.

@markuskowa Done: #55677

@giovtorres Thank you. I hope this won't create inconvenience for you.