[NVIDIA] Prepare setup.py for PyPi

[redradist]

Description

Update setup.py to be usable for PyPi.
Create initial package for openvino-nvidia plugin in PyPi, see https://pypi.org/project/openvino-nvidia

[redradist]

@ilya-lavrenov @p-durandin Now cherry on cake - python package

[p-durandin]

build_jenkins

[p-wysocki]

While the README.md file makes sense, there are a lot of typos and its style could be aligned to the style of the rest of the file. Could you please correct it or at least run it through an LLM to improve formatting and typos?

[p-wysocki]

Calling bdist_wheel manually has been deprecated for a while, going as far as an official Python blog saying that they mustn't be run anymore. The recommended replacement is python -m build which requires build dependency. Could you please check if running it is compatible and works well? We shouldn't introduce functionality based on outdated, possibly broken command.

Same goes for setup.py install below.

[redradist]

The functionality could be done iteratively.
In my current python environment python -m build failed due to missed dependencies (probably because I have custom build for python)

[p-wysocki]

I'm not a fan of introducing a functionality which we know may be broken/is not only not recommended, but soft-forbidden by Python docs. These things tend to stick around as a "TODO" and later cause issues at the most inconvenient time.

I haven't maintained NVIDIA plugin before so IMO my opinion can be overridden if you wish to do so (cc @p-durandin). If we decide to merge it as-is at the very least let's create a ticket to update the build method.

[p-durandin]

@p-wysocki thanks, lets merge with creating github issue

[redradist]

While the README.md file makes sense, there are a lot of typos and its style could be aligned to the style of the rest of the file. Could you please correct it or at least run it through an LLM to improve formatting and typos?

@p-wysocki Looks like fixed all typos

[p-wysocki]

Overall LGTM if it wasn't for the outdated wheel build/install method I mentioned in one of my comments. I'd prefer it to be done properly to avoid problems in the future.

Should we update the CI somehow to test this? I'm not familiar with openvino_contrib pipelines.

@p-durandin, is there a designated maintainer for this repo?

[p-wysocki]

Perhaps we should be setting this dynamically based on openvino version, or at least set it to an upcoming 2025.4.0 if we plan to release it? I'm not sure how it should be done, @artanokhov do you know?

One way or another, if we'd like to set this dynamically, this is a topic for a different PR.

[redradist]

Perhaps we should be setting this dynamically based on openvino version, or at least set it to an upcoming 2025.4.0 if we plan to release it?

@p-wysocki Have not idea, I am not the official maintainer of NVIDIA plugin, I am the former developer of it and I know pretty good its architecture.
In future I expect Intel will publish packages for openvino-nvidia, but for this proper CI should be configured

[p-wysocki]

I'm not a fan of introducing a functionality which we know may be broken/is not only not recommended, but soft-forbidden by Python docs. These things tend to stick around as a "TODO" and later cause issues at the most inconvenient time.

I haven't maintained NVIDIA plugin before so IMO my opinion can be overridden if you wish to do so (cc @p-durandin). If we decide to merge it as-is at the very least let's create a ticket to update the build method.

[redradist]

@p-wysocki I've played with it little bit, it requires some changes here and there to implement it using python3 -m pip build
Maybe lets implement it as refactoring ?
Currently this PR mostly to fix some issues related to setup.py, to be able finally create PyPi package

[mlukasze]

build_jenkins

[p-wysocki]

Overall LGTM if it wasn't for the bdist_wheel thing. I'm leaving the decision to the openvino_contrib maintainers.

[p-durandin]

To be followed in #1011