Bugfix envision resource path #1682
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Gamenot
assigned Gamenot, saulfield and qianyi-sun and unassigned saulfield and qianyi-sun
qianyi-sun
approved these changes
Oct 26, 2022
saulfield
approved these changes
Oct 26, 2022
Gamenot
force-pushed
the
tucker/bugfix-envision_resource_path
branch
from
5dbfa94 to
03df75b
Compare
Gamenot
added a commit
that referenced
this pull request
Oct 26, 2022
* Fix envision resource path * Format log message better * Change log to debug * Update changelog * Remove duplicate file * Fix directory resolution in scenario construction
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix an issue where
importlib.resources.path()was incorrectly attempting to create a file named"."and operated in a different way depending on python version.