Expose Python standard module __file__ and __name__ to rezconfig #636
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.
Now users can fetch the absolute path to a given
rezconfig
like from any other module.rezconfig.py
The
__name__
is computed rather than hardcoded, to account forREZ_CONFIG_FILE
being able to take any arbitrary file name, along with avoiding anything hardcoded.This is expected but missing behavior I think, but additionally one specific usecase was having my
rezconfig.py
at the root of my Rez packages, and wanting to set paths up relative this file.Oh, and I explicitly did not let these get carried into the resulting
Config
object, as that would make less sense, considering it is a result of potentially many different rezconfig.py files. Hence, writing a test for this was challenging.. if you have any ideas, I'd be happy to add some.