Allow even more dynamic instrumentation of pwd via os.dynamicPwdFunction
#299
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.
Follow up to #298, which it turns out was not flexible enough to do what we need in Mill. Mill uses references to the
pwdto create the.destfolder lazily, thus we cannot just assign a value to theos.pwdbut actually need to assign a lambda that can be replaced to implement the lazy evaluationI pulled the trigger too quickly on releasing 0.10.6 with
os.dynamicPwd, so this one has to be named differently. I choseos.dynamicPwdFunctionand will make sure to test it with an unstable release before releasing a stable tag