Thank you everyone who has contributed to this discussion.
My question has been answered. Unless there are additional questions, along the same topic, consider this thread closed.
Welcome to the Python community on the programming.dev Lemmy instance!
Past
November 2023
October 2023
July 2023
August 2023
September 2023
Thank you everyone who has contributed to this discussion.
My question has been answered. Unless there are additional questions, along the same topic, consider this thread closed.
I do the same. The exception is test data, which sometimes is too large to not dominate the sdist size, so I choose to not include it.
If your talking about a source distribution archive, generally it is the project in the 'distclean' state. This is decribed in GNU documentation. I think for GNU Make. Not sure if the git specific files should technically be included but maybe these days they should. The 'distclean' state is generally the same code as from the VCS tree but with hard to build files pre-built but probably not platform specific files. The 'maintainerclean' state is basically the clean VCS snapshot nothing pre-built.
Edit: The reason to prebuild some not platform specific files is to minimize the tools needed for installing from source.
Thank you. Took me awhile to internalize your very generous and detailed advice
target spelling correction: maintainerclean --> maintainer-clean
Here is the docs covering the topic
In Makefile, separate GNU Make standard targets from other target categories
Rename make coverage
--> make check
. This would require including tests/
in tarball
Consider creating targets distclean and maintainer-clean
In MANIFEST.in
, remove git related files: .gitignore, .github/**/*
Removed config files: codecov.yml, .readthedocs.yml
By the way. The only files you mentioned I am less sure about are configs. Specifically if these configs are system specific, probaby only examples or templates should be included but the configs should be built by the build process on the target system.
Edit: It should contain tests. Running some equivalent to 'make check' on the target system is pretty standard.
Edit: Not sure what .github folder tree file contains so cannot say.