-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[core] Remove deprecated ov::element:undefined #32573
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
[core] Remove deprecated ov::element:undefined #32573
Conversation
|
please, do not merge before the 25.4 code freeze |
8a32021 to
e6e34de
Compare
|
Ok for core and c-api parts. |
|
@build_jenkins |
olpipi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Just fix the formatting please
src/bindings/c/src/ov_tensor.cpp
Outdated
| {ov_element_type_e::STRING, ov::element::string}, | ||
| {ov_element_type_e::F4E2M1, ov::element::f4e2m1}, | ||
| {ov_element_type_e::F8E8M0, ov::element::f8e8m0}, | ||
| {ov_element_type_e::DYNAMIC, ov::element::dynamic}, {ov_element_type_e::BOOLEAN, ov::element::boolean}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please return enumeration of types to 1 column? It seems confusing to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i tried this, but clang format reported this as an issue on CI and locally as well. should i get it back to 1 column again anyway?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Try // clang-format off line before and on again afterwards
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
|
@Aliczi @Retribution98 Could you check if there is any update required from bindings? |
almilosz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello, python api warning should be removed from here but it can be done separately.
JS part no changes needed
remove deprecated ov::element type undefined to have dynamic type used instead. Signed-off-by: Walid Aly <[email protected]>
remove deprecated undefined type and warning message Signed-off-by: Walid Aly <[email protected]>
e6e34de to
0081ae1
Compare
|
|
||
| Deprecated and to be removed in the future | ||
| -------------------------------------------- | ||
| * ``openvino.Type.undefined`` is now deprecated and will be removed with version 2026.0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section about 25.0 should be kept. Later, for 2026.0 we will add an entry that Type.undefined was removed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, i think this PR is targeted to be merged for 2026.0 release. should this change to inform that Type.undefined is removed already?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
afaik usually there is a big pr with updates to release-notes. It makes sense to remove this part, but I am not sure what other changes are necessary @tsavina
|
@build_jenkins |
|
build_jenkins |
remove deprecated ov::element type undefined to have dynamic type used instead.
Tickets: