Run check_manifest in one of the CI setups
See original GitHub issueAs per https://github.com/scikit-learn/scikit-learn/issues/13859#issuecomment-491688835, we are at risk of missing files from our MANIFEST.in and only noticing it upon release. We could use the check-manifest Python package as an additional check alongside, say linting (which is configured in .circleci/config.yml)
Issue Analytics
- State:
 - Created 4 years ago
 - Comments:8 (8 by maintainers)
 
Top Results From Across the Web
check-manifest - PyPI
Copy the source tree to a temporary directory before running python setup.py sdist to avoid side effects from setuptools plugins or stale *.egg-info/SOURCES.txt ......
Read more >Including files in source distributions with MANIFEST.in
The following files are included in a source distribution by default: all Python source files implied by the py_modules and packages setup() arguments....
Read more >mgedmin/check-manifest - GitHub
Are you a Python developer? Have you uploaded packages to the Python Package Index? Have you accidentally uploaded broken packages with some files...
Read more >Deploying with App Manifests | Cloud Foundry Docs
Deploy an App with a Manifest · Create a manifest.yml file in the root directory of your app. Note: By default, the cf...
Read more >Tutorial: Create and run your first GitLab CI/CD pipeline
To view available runners: Go to Settings > CI/CD and expand Runners. As long as you have at least one runner that's active,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I think we’d benefit from it, thanks.
@jnothman I’ll pick this up if the check is still required