You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pdftotree-0.5.0/tests> ls
__init__.py test_basic.py test_table_detection.py
As a reult, running the tests from the PyPI sdist isnt currently possible.
The usual/old solution is to create a MANIFEST.in , which can be generated using check-manifest , but there are newer ways and tools if you do not want another metadata file in the repo.
The text was updated successfully, but these errors were encountered:
I see your point. One concern I would have is that the test data can be quite large. I'm not sure we actually want to bundle that together. Is there a good best practice to follow here?
Best practise is to distribute wheels which only include the minimum needed to use the package, and a sdist which is a version snaphot of the 'source' which includes whatever is considered useful, e.g. docs, tests, test data, etc.
Would you happen to have the time to put together a PR for this? If not, it may be some time before I can get around to looking into this. I'll need to read up on the trade-offs of MANIFEST.in compared to what the more recent methods are.
As a reult, running the tests from the PyPI sdist isnt currently possible.
The usual/old solution is to create a MANIFEST.in , which can be generated using
check-manifest
, but there are newer ways and tools if you do not want another metadata file in the repo.The text was updated successfully, but these errors were encountered: