[docs] Fix the incorrect API docs generation steps in the release process #131
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.
Motivation
#126 adds the instruction to include the
_pulsar
C module when generating the API docs. However, it does not work when the library is installed frompip
. It only works when the wheel is installed fromdist/*.whl
that is generated by thepython3 setup.py bdist_wheel
command in the README.The reason is the official Python wheel uses
auditwheel
to package all dynamic libraries, so the_pulsar.so
depends on another dynamic library in the relative path. e.g.If we copy the
_pulsar.cpython-38-x86_64-linux-gnu.so
into the project directory, thelibpulsar-b6dad138.so
will not be found.In addition, the path of the static API docs changed after the refactoring of
pulsar-site
,Modifications
In
RELEASE.md
, specify the path of_pulsar.so
directly.