fix: Move backwards-compatible logic before function source load - #152
Merged
Merged
Conversation
anniefu
approved these changes
Oct 11, 2021
anniefu
left a comment
Contributor
There was a problem hiding this comment.
[nit] Could you add a short explanation in the description? or attach a GitHub Issue if there is one
di
approved these changes
Oct 12, 2021
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Functions that rely on legacy Python 3.7 env vars (FUNCTION_NAME for example) cannot currently use them in the global scope, since the env var assignment is done after the function source is loaded. This changes the order of the env var assignment and the source load to allow functions access to the env vars even in global scope.