local.cwd doesn't work if cwd changes by non-plumbum means #207
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.
This patch makes the
local.cwd
the current working directory, not just the current working directory when Plumbum loaded, so code like this now works:The
cwd
is now a descriptor in the local machine (and works from class or object access). Added a test similar to the lines above to verify that it works.(Example of use case: This is a common problem when working with Plumbum in IPython and trying to use
local.cwd
to find files after changing the directory withcd
.)