openvino
fbcd8dfd - Update h5py requirement from <3.14.0,>=3.1.0 to >=3.1.0,<3.15.0 in /tests (#30898)

Commit
309 days ago
Update h5py requirement from <3.14.0,>=3.1.0 to >=3.1.0,<3.15.0 in /tests (#30898) Updates the requirements on [h5py](https://github.com/h5py/h5py) to permit the latest version. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/h5py/h5py/blob/master/docs/release_guide.rst">h5py's changelog</a>.</em></p> <blockquote> <p>.. _release_guide:</p> <h1>Release Guide</h1> <p>Steps to make an h5py release:</p> <ol> <li> <p>Have a look for any open issues or PRs which we might want to solve/merge before the release.</p> </li> <li> <p>Prepare a new branch, e.g. <code>git switch -c prepare-3.14</code></p> </li> <li> <p>Prepare the release notes. The goal is to describe changes visible to users &amp; repackagers of h5py in a form that doesn't assume 'internal' development knowledge. If something breaks, or behaviour changes unexpectedly, the release notes should let someone make a good guess which change is involved.</p> <ul> <li>Check for recent <code>merged PRs with no milestone &lt;https://github.com/h5py/h5py/pulls?q=is%3Amerged+is%3Apr+no%3Amilestone&gt;</code>_, and assign them to the current release milestone. We can ignore PRs which only touch CI with no consequences for users.</li> <li>Go to the milestone page. If there are open issues/PRs there, decide whether to include or defer them.</li> <li>Assemble the release notes in <code>docs/whatsnew</code> based on the list of merged PRs. Commit the changes.</li> </ul> </li> <li> <p>Update the version number &amp; commit the changes. The files that need changing are:</p> <ul> <li><code>setup.py</code></li> <li><code>h5py/version.py</code></li> <li><code>docs/conf.py</code></li> </ul> </li> <li> <p>Push the branch, open a PR, wait for the CI. Check the RTD build for the newly added release notes (formatting &amp; cross-links). Optionally, wait for other maintainers to check it as well.</p> </li> <li> <p>When everything looks good, merge the PR.</p> </li> <li> <p>Checkout the master branch, pull, make and push the tag, which will cause CI to build wheels &amp; make a GitHub release::</p> <p>git switch master git pull git tag 3.14.0 # &lt;-- change this git push --tags</p> </li> <li> <p>Prepare the sdist::</p> <p>git clean -xfdi python -m build --sdist</p> </li> <li> <p>Download the wheels: <code>gh release download 3.14.0 -D dist/</code></p> </li> <li> <p>Upload to PyPI: <code>twine upload dist/h5py-3.14.0*</code> - this requires a token from PyPI, which must be <code>supplied to twine &lt;https://twine.readthedocs.io/en/stable/#configuration&gt;</code>_.</p> </li> </ol> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/h5py/h5py/commit/07a5511a137f96159ee58b84d2b67318bc271482"><code>07a5511</code></a> Merge pull request <a href="https://redirect.github.com/h5py/h5py/issues/2591">#2591</a> from takluyver/prepare-3.14</li> <li><a href="https://github.com/h5py/h5py/commit/a70e013392b82fe2441d47247e421bbdf1dda9f5"><code>a70e013</code></a> Add versionadded box for numpy strings support</li> <li><a href="https://github.com/h5py/h5py/commit/6186edf1f0102074d1b084dde392882267c96b39"><code>6186edf</code></a> Version number -&gt; 3.14.0</li> <li><a href="https://github.com/h5py/h5py/commit/a9e2d46819657ef0d714e98c092e5a44664e2892"><code>a9e2d46</code></a> Add release notes for 3.14</li> <li><a href="https://github.com/h5py/h5py/commit/ab19424e0abe40846d99303577cbf9d8f187e186"><code>ab19424</code></a> Merge pull request <a href="https://redirect.github.com/h5py/h5py/issues/2585">#2585</a> from ArvidJB/fork_thread_phil</li> <li><a href="https://github.com/h5py/h5py/commit/60c5cd90e1338ea186b8238e0386feb994585682"><code>60c5cd9</code></a> Merge pull request <a href="https://redirect.github.com/h5py/h5py/issues/2590">#2590</a> from neutrinoceros/tst/bump-windows-image</li> <li><a href="https://github.com/h5py/h5py/commit/e3cc528864d5221ff140a06364d932498722b691"><code>e3cc528</code></a> MNT: bump windows image on azure (2019 -&gt; 2022)</li> <li><a href="https://github.com/h5py/h5py/commit/a51de9fc75cbd526c2bfa9ad59b52ed7554562f6"><code>a51de9f</code></a> Time out tests on deadlock instead of hanging and leaving zombie processes be...</li> <li><a href="https://github.com/h5py/h5py/commit/7c14cd94ce35191f55254c1d06373ef44785e5a6"><code>7c14cd9</code></a> Merge pull request <a href="https://redirect.github.com/h5py/h5py/issues/2586">#2586</a> from takluyver/h5d-write-chunk</li> <li><a href="https://github.com/h5py/h5py/commit/a92ab7ca182fdab99b11bde838dfcf06278328fc"><code>a92ab7c</code></a> Address review comments</li> <li>Additional commits viewable in <a href="https://github.com/h5py/h5py/compare/3.1.0...3.14.0">compare view</a></li> </ul> </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Parents
Loading