I am creating a Python package which wraps (and bundles) a DLL. I'm planning on shipping prebuilt sphinx based docs within the wheel and perhaps add an entry point as a convenience to launch a browser to view them.
After some googling I haven't found much information on this approach.
Is this not a recommended approach? Note that this is for an in house package that is not for public consumption and I want the package user to always have the appropriate version of the docs for the DLL release.
What I'm looking for is a way to include the built html files by referencing them within the setup.py file. I know that I can use package_data
and include_package_data
keyword arguments to setup
within setup.py
but I believe that these work with packages as the name implies so I think using this approach would be messy for this application.
If this is not the right approach, I'm keen to hear of better alternatives!