Exclude pycache when copying packet inputs and outputs. #45
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.
Python tends to produce a lot of
__pycache__
folders. These can be found both in a report's source directory, if the user ran the entrypoint script outside of an orderly context, and in the packet's working directory after executing the packet.There is never a good reason to include these in packets and we can exclude them unconditionally, both when copying files in and out of a packet's working directory.
As a side-effect of now using the same function to copy files in and out of a packet, this commit also fixes the use of directory in a report's source directory. Previously we were attempting to call
shutil.copy2
on every entry, which would fail on directories.