Repository navigation
Keep Python bytecode caches out of workspace Git status - #7
Merged
Merged
Conversation
Running the application writes __pycache__ directories next to the source. Dependencies already live in .wodby-workspace, which the image excludes itself.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Running a Python application in a workspace writes
__pycache__directories next to the source, so they showed up as untracked in Git status for projects that don't ignore them. This adds aworkspace.ignorelist with__pycache__/. The pattern goes to the checkout's local.git/info/exclude, so the repository itself doesn't change. Django, Flask and FastAPI inherit it. Dependencies already live in.wodby-workspace, which the image excludes itself.Validation
Merge order
The Wodby platform now accepts
workspace.ignorein service manifests, so this can merge.