Support OTIO_PLUGIN_MANIFEST_PATH being set to an empty string #1253
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 restores the ability to set OTIO_PLUGIN_MANIFEST_PATH to an empty string
to indicate no local custom manifest file.
Link the Issue(s) this Pull Request is related to.
Fixes #1252
Summarize your change.
This changes a truthy check on the env var OTIO_PLUGIN_MANIFEST_PATH to skip any false value and not explicitly
is None
. This will allow OTIO_PLUGIN_MANIFEST_PATH='' to be equivalent to that env var not being set.Reference associated tests.
Added a test specifically for this. Also updated all tests in
test_adapter_plugin.py
to always un-set custom env vars or manifests on exceptions due to test failures so as to not pollute subsequent tests.