Add QUATERNIONIC_DISABLE_CACHE environment variable. #47
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.
It may not always be desirable to cache the Numba-generated code, for example in a HPC environment where having lots of workers each compiling the code may be preferable to them all trying to load it from the cache.
This adds a QUATERNIONIC_DISABLE_CACHE environment variable. If set to 1, the
cache
parameter of thejit
andguvectorize
decorators is set to False. Default behaviour remains the same as before, i.e., to use the cache.For the record, I have also made a pull request to Numba (numba/numba#9702) adding a environment variable to disable all caching. I figured that having the option just to disable it in quaternionic may be useful (and also, quaternionic would be quicker to have a release containing it allowing me to use it in my application sooner!).