Go to file
dependabot[bot] e6beb94085
Bump jsonschema from 4.17.0 to 4.22.0 in /tests (#24331)
Bumps [jsonschema](https://github.com/python-jsonschema/jsonschema) from
4.17.0 to 4.22.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/python-jsonschema/jsonschema/releases">jsonschema's
releases</a>.</em></p>
<blockquote>
<h2>v4.22.0</h2>
<!-- raw HTML omitted -->
<h2>What's Changed</h2>
<ul>
<li>Improve <code>best_match</code> (and thereby error messages from
<code>jsonschema.validate</code>) in cases where there are multiple
<em>sibling</em> errors from applying <code>anyOf</code> /
<code>allOf</code> -- i.e. when multiple elements of a JSON array have
errors, we now do prefer showing errors from earlier elements rather
than simply showing an error for the full array (<a
href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1250">#1250</a>).</li>
<li>(Micro-)optimize equality checks when comparing for JSON Schema
equality by first checking for object identity, as <code>==</code>
would.</li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/shinnar"><code>@​shinnar</code></a> made
their first contribution in <a
href="https://redirect.github.com/python-jsonschema/jsonschema/pull/1224">python-jsonschema/jsonschema#1224</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/python-jsonschema/jsonschema/compare/v4.21.1...v4.22.0">https://github.com/python-jsonschema/jsonschema/compare/v4.21.1...v4.22.0</a></p>
<h2>v4.21.1</h2>
<!-- raw HTML omitted -->
<ul>
<li>Slightly speed up the <code>contains</code> keyword by removing some
unnecessary validator (re-)creation.</li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/python-jsonschema/jsonschema/compare/v4.21.0...v4.21.1">https://github.com/python-jsonschema/jsonschema/compare/v4.21.0...v4.21.1</a></p>
<h2>v4.21.0</h2>
<!-- raw HTML omitted -->
<h2>What's Changed</h2>
<ul>
<li>Fix the behavior of <code>enum</code> in the presence of
<code>0</code> or <code>1</code> to properly consider <code>True</code>
and <code>False</code> unequal (<a
href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1208">#1208</a>).</li>
<li>Special case the error message for
<code>{min,max}{Items,Length,Properties}</code> when they're checking
for emptiness rather than true length.</li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/otto-ifak"><code>@​otto-ifak</code></a>
made their first contribution in <a
href="https://redirect.github.com/python-jsonschema/jsonschema/pull/1208">python-jsonschema/jsonschema#1208</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/python-jsonschema/jsonschema/compare/v4.20.0...v4.21.0">https://github.com/python-jsonschema/jsonschema/compare/v4.20.0...v4.21.0</a></p>
<h2>v4.20.0</h2>
<ul>
<li>Properly consider items (and properties) to be evaluated by
<code>unevaluatedItems</code> (resp. <code>unevaluatedProperties</code>)
when behind a <code>$dynamicRef</code> as specified by the 2020 and 2019
specifications.</li>
<li><code>jsonschema.exceptions.ErrorTree.__setitem__</code> is now
deprecated. More broadly, in general users of <code>jsonschema</code>
should never be mutating objects owned by the library.</li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/python-jsonschema/jsonschema/compare/v4.19.2...v4.20.0">https://github.com/python-jsonschema/jsonschema/compare/v4.19.2...v4.20.0</a></p>
<h2>v4.19.2</h2>
<!-- raw HTML omitted -->
<ul>
<li>Fix the error message for additional items when used with
heterogeneous arrays.</li>
<li>Don't leak the <code>additionalItems</code> keyword into JSON Schema
draft 2020-12, where it was replaced by <code>items</code>.</li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/python-jsonschema/jsonschema/compare/v4.19.1...v4.19.2">https://github.com/python-jsonschema/jsonschema/compare/v4.19.1...v4.19.2</a></p>
<h2>v4.19.1</h2>
<!-- raw HTML omitted -->
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/python-jsonschema/jsonschema/blob/main/CHANGELOG.rst">jsonschema's
changelog</a>.</em></p>
<blockquote>
<h1>v4.22.0</h1>
<ul>
<li>Improve <code>best_match</code> (and thereby error messages from
<code>jsonschema.validate</code>) in cases where there are multiple
<em>sibling</em> errors from applying <code>anyOf</code> /
<code>allOf</code> -- i.e. when multiple elements of a JSON array have
errors, we now do prefer showing errors from earlier elements rather
than simply showing an error for the full array (<a
href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1250">#1250</a>).</li>
<li>(Micro-)optimize equality checks when comparing for JSON Schema
equality by first checking for object identity, as <code>==</code>
would.</li>
</ul>
<h1>v4.21.1</h1>
<ul>
<li>Slightly speed up the <code>contains</code> keyword by removing some
unnecessary validator (re-)creation.</li>
</ul>
<h1>v4.21.0</h1>
<ul>
<li>Fix the behavior of <code>enum</code> in the presence of
<code>0</code> or <code>1</code> to properly consider <code>True</code>
and <code>False</code> unequal (<a
href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1208">#1208</a>).</li>
<li>Special case the error message for
<code>{min,max}{Items,Length,Properties}</code> when they're checking
for emptiness rather than true length.</li>
</ul>
<h1>v4.20.0</h1>
<ul>
<li>Properly consider items (and properties) to be evaluated by
<code>unevaluatedItems</code> (resp. <code>unevaluatedProperties</code>)
when behind a <code>$dynamicRef</code> as specified by the 2020 and 2019
specifications.</li>
<li><code>jsonschema.exceptions.ErrorTree.__setitem__</code> is now
deprecated.
More broadly, in general users of <code>jsonschema</code> should never
be mutating objects owned by the library.</li>
</ul>
<h1>v4.19.2</h1>
<ul>
<li>Fix the error message for additional items when used with
heterogeneous arrays.</li>
<li>Don't leak the <code>additionalItems</code> keyword into JSON Schema
draft 2020-12, where it was replaced by <code>items</code>.</li>
</ul>
<h1>v4.19.1</h1>
<ul>
<li>Single label hostnames are now properly considered valid according
to the <code>hostname</code> format.
This is the behavior specified by the relevant RFC (1123).
IDN hostname behavior was already correct.</li>
</ul>
<h1>v4.19.0</h1>
<ul>
<li>Importing the <code>Validator</code> protocol directly from the
package root is deprecated.
Import it from <code>jsonschema.protocols.Validator</code> instead.</li>
<li>Automatic retrieval of remote references (which is still deprecated)
now properly succeeds even if the retrieved resource does not declare
which version of JSON Schema it uses.
Such resources are assumed to be 2020-12 schemas.
This more closely matches the pre-referencing library behavior.</li>
</ul>
<h1>v4.18.6</h1>
<ul>
<li>Set a <code>jsonschema</code> specific user agent when automatically
retrieving remote references (which is deprecated).</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="9882dbeb1a"><code>9882dbe</code></a>
Add / ignore the new specification test suite property.</li>
<li><a
href="ebc90bb2df"><code>ebc90bb</code></a>
Merge commit '8fcfc3a674a7188a4fcc822b7a91efb3e0422a20'</li>
<li><a
href="8fcfc3a674"><code>8fcfc3a</code></a>
Squashed 'json/' changes from b41167c74..54f3784a8</li>
<li><a
href="30b7537944"><code>30b7537</code></a>
Pin pyenchant to pre from below until <a
href="https://redirect.github.com/pyenchant/pyenchant/issues/302">pyenchant/pyenchant#302</a>
is released.</li>
<li><a
href="c3729db732"><code>c3729db</code></a>
Enable doctests for the rest of the referencing page.</li>
<li><a
href="70a994ceab"><code>70a994c</code></a>
Remove a now-unneeded noqa since apparently this is fixed in new
ruff.</li>
<li><a
href="e6d0ef1cff"><code>e6d0ef1</code></a>
Fix a minor typo in the referencing example docs.</li>
<li><a
href="bceaf41a7d"><code>bceaf41</code></a>
Another placeholder benchmark for future optimization.</li>
<li><a
href="b20234e86c"><code>b20234e</code></a>
Consider errors from earlier indices (in instances) to be better
matches</li>
<li><a
href="41b49c68e5"><code>41b49c6</code></a>
Minor improvement to test failure message when a best match test
fails.</li>
<li>Additional commits viewable in <a
href="https://github.com/python-jsonschema/jsonschema/compare/v4.17.0...v4.22.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=jsonschema&package-manager=pip&previous-version=4.17.0&new-version=4.22.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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>
2024-05-02 15:53:25 +00:00
.github Run dependency review workflow on merge group event (#24350) 2024-05-02 19:53:05 +04:00
cmake Manually define CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION (#24343) 2024-05-02 19:50:48 +04:00
docs [DOCS] Fix links to components (#24339) 2024-05-02 11:15:13 +00:00
licensing copyright year update (#23370) 2024-03-14 09:37:02 +00:00
samples [DOCS] New notebooks update for master (#24134) 2024-04-29 13:29:29 +04:00
scripts Supported Ubuntu 24.04 (#23905) 2024-04-16 14:26:41 +00:00
src Fix h5py issue in GHA test jobs (#24338) 2024-05-02 19:50:59 +04:00
tests Bump jsonschema from 4.17.0 to 4.22.0 in /tests (#24331) 2024-05-02 15:53:25 +00:00
thirdparty Intel compiler support (#24217) 2024-04-27 14:03:28 +00:00
tools Fix h5py issue in GHA test jobs (#24338) 2024-05-02 19:50:59 +04:00
.gitattributes [CI] [GHA] Introduce GHA pipeline rerunner (#23865) 2024-04-16 14:52:12 +00:00
.gitignore [DOCS] Bump Sphinx and Pydata versions (#24083) 2024-04-18 09:56:42 +00:00
.gitmodules [Snippets] TPP FP32 MHA support (#22210) 2024-04-22 14:52:42 +00:00
CMakeLists.txt Use latest Windows SDK by default (#24326) 2024-05-02 01:49:40 +04:00
CONTRIBUTING.md [DOCS] Readme changes (#20818) 2024-04-25 14:48:00 +00:00
CONTRIBUTING_DOCS.md [DOCS] contributing guidelines (#19218) 2023-08-18 17:59:31 +02:00
CONTRIBUTING_PR.md Update GFI template and docs with information about linking PRs to issues (#23409) 2024-03-12 21:55:21 +00:00
Jenkinsfile Beautify Jenkinsfile a little bit 2021-05-31 15:24:56 +03:00
LICENSE Publishing R3 2018-10-16 13:45:03 +03:00
README.md [DOCS] Fix links to components (#24339) 2024-05-02 11:15:13 +00:00
SECURITY.md Added SECURITY.md back (#3177) 2020-11-17 16:44:44 +03:00
conan.lock Updated pybind11 to 2.12.0 (#24140) 2024-04-22 15:03:02 +04:00
conanfile.txt Updated pybind11 to 2.12.0 (#24140) 2024-04-22 15:03:02 +04:00
cspell.json Add file via upload (#19605) 2023-09-19 17:16:16 +04:00
install_build_dependencies.sh Supported Ubuntu 24.04 (#23905) 2024-04-16 14:26:41 +00:00
vcpkg.json Removed ade from vcpkg.json and conanfile.txt (#22823) 2024-02-14 10:43:10 +04:00

README.md

PyPI Status Anaconda Status brew Status

PyPI Downloads Anaconda Downloads brew Downloads

Welcome to OpenVINO™, an open-source software toolkit for optimizing and deploying deep learning models.

  • Inference Optimization: Boost deep learning performance in computer vision, automatic speech recognition, generative AI, natural language processing with large and small language models, and many other common tasks.
  • Flexible Model Support: Use models trained with popular frameworks such as TensorFlow, PyTorch, ONNX, Keras, and PaddlePaddle.
  • Broad Platform Compatibility: Reduce resource demands and efficiently deploy on a range of platforms from edge to cloud.
  • Community and Ecosystem: Join an active community contributing to the enhancement of deep learning performance across various domains.

Check out the OpenVINO Cheat Sheet for a quick reference.

Installation

Get your preferred distribution of OpenVINO or use this command for quick installation:

pip install openvino

Check system requirements and supported devices for detailed information.

Tutorials and Examples

OpenVINO Quickstart example will walk you through the basics of deploying your first model.

Learn how to optimize and deploy popular models with the OpenVINO Notebooks📚:

Here are easy-to-follow code examples demonstrating how to run PyTorch and TensorFlow model inference using OpenVINO:

PyTorch Model

import openvino as ov
import torch
import torchvision

# load PyTorch model into memory
model = torch.hub.load("pytorch/vision", "shufflenet_v2_x1_0", weights="DEFAULT")

# convert the model into OpenVINO model
example = torch.randn(1, 3, 224, 224)
ov_model = ov.convert_model(model, example_input=(example,))

# compile the model for CPU device
core = ov.Core()
compiled_model = core.compile_model(ov_model, 'CPU')

# infer the model on random data
output = compiled_model({0: example.numpy()})

TensorFlow Model

import numpy as np
import openvino as ov
import tensorflow as tf

# load TensorFlow model into memory
model = tf.keras.applications.MobileNetV2(weights='imagenet')

# convert the model into OpenVINO model
ov_model = ov.convert_model(model)

# compile the model for CPU device
core = ov.Core()
compiled_model = core.compile_model(ov_model, 'CPU')

# infer the model on random data
data = np.random.rand(1, 224, 224, 3)
output = compiled_model({0: data})

OpenVINO also supports CPU, GPU, and NPU devices and works with models in TensorFlow, PyTorch, ONNX, TensorFlow Lite, PaddlePaddle model formats. With OpenVINO you can do automatic performance enhancements at runtime customized to your hardware (preserving model accuracy), including: asynchronous execution, batch processing, tensor fusion, load balancing, dynamic inference parallelism, automatic BF16 conversion, and more.

OpenVINO Ecosystem

Check out the Awesome OpenVINO repository to discover a collection of community-made AI projects based on OpenVINO!

Documentation

User documentation contains detailed information about OpenVINO and guides you from installation through optimizing and deploying models for your AI applications.

Developer documentation focuses on how OpenVINO components work and describes building and contributing processes.

Contribution and Support

Check out Contribution Guidelines for more details. Read the Good First Issues section, if you're looking for a place to start contributing. We welcome contributions of all kinds!

You can ask questions and get support on:

Additional Resources

License

OpenVINO™ Toolkit is licensed under Apache License Version 2.0. By contributing to the project, you agree to the license and copyright terms therein and release your contribution under these terms.


* Other names and brands may be claimed as the property of others.