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.
Changing
setup.py
file to check forMANIFEST.in
fileMANIFEST.in
file now includes and excludes correct files and directories for building source distributionTo test the source build, please run:
This will create a folder
dist/
which includes a tar file. From a Linux terminal, you can run:or to unpack it.
You should notice a couple of things:
The
examples/
,utilities/
,varsomdata/
, andvarsomscripts/
directories are included in the build. This means that theoutput/
andresources/
directories are not included, which was the point of setting up theMANIFEST.in
file.Additionally, the
experimental/
,config
,test
directories and thesetenvironment.py
file are not included. Theconfig
files are in the.gitignore
file, so it did not make sense to include thesetenvironment.py
file which uses those files. However, this would be easy to include if we wanted any of these files or directories for the first release to PyPI.