Open kloczek opened 4 years ago
@kloczek I checked version 4.20.0, 4.8.0 from 2018 and 4.0.0 from 2015 and they are all the same, so this appears intentional.
For every release I run this (which complains a bit about using twine instead), the second command has been in the readme for 4 years or so now.
git clean -xdf
python setup.py sdist bdist_wheel upload
I suppose something of the packaging tooling automatically cleans up the source tree during packaging to only retain the actual Python source code. Whether this is convention for Python or PyPI I do not know, that would be something to have a look at.
@kloczek As for GitHub tarball, from your logs:
fatal: not a git repository (or any parent up to mount point /home/tkloczko)
Some of the scripts used to generate documentation probably assume we are always building from the git repo, it likely uses this to fetch version (tag/commit sha) information.
Some of the scripts used to generate documentation probably assume we are always building from the git repo, it likely uses this to fetch version (tag/commit sha) information.
That message was generated by sphinx-build -b man -d python-breathe documentation/source .
command.
Autogenerated by gitlab/githug tar ball dowloaded from git tag does not contain git metadata.
@kloczek To clarify, the documentation building problem from source tarballs is indeed a bug, will label and update title to reflect this. Patches are welcome as usual.
Edit: as for the contents of the PyPI source package, I consider this intentional at this point unless I get some specific info on this.
In case od https://files.pythonhosted.org/packages/source/b/breathe/breathe-4.21.0.tar.gz there is no
documentation/
andexamples/
directories. In case if tagged tar ball https://github.com/michaeljones/breathe//archive/v4.21.0/python-breathe-4.21.0.tar.gz looks like some files are missig and sphinx cannot generate documentation