[Py OV] Initialize op and opset*/ops.py explicitly #28296
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Details:
openvino.runtime.utils
(PR28062). Onopenvino
import,op
was initialized here alongside utils. I propose to initializeop
explicitly inopenvino/runtime/__init__.py
andopenvino/__init__.py
runtime/opset*/
as they are present in thesys.modules
for2024.6-openvino
and some users may access operators directly from there.Tickets: