When executing the build_wheel.py script locally, i.e. python3 setup.py bdist_wheel, the tests package is included as a top level package in the generated tritonclient python wheel. In general, it is best practice to only include production code required by users to run the software.
The current packages found in the produced top_level.txt package are:
tests
tritonclient
tritonclientutils
tritongrpcclient
tritonhttpclient
tritonshmutils
It appears the wheel available on pypl does not include the tests package.
To align local builds with what is available on pypl, the tests package should be excluded from the find_packages() call in setup.py:
find_packages(exclude=['tests'])
When executing the
build_wheel.pyscript locally, i.e.python3 setup.py bdist_wheel, the tests package is included as a top level package in the generated tritonclient python wheel. In general, it is best practice to only include production code required by users to run the software.The current packages found in the produced
top_level.txtpackage are:It appears the wheel available on pypl does not include the
testspackage.To align local builds with what is available on pypl, the
testspackage should be excluded from thefind_packages()call in setup.py: