[python] Fix wrongly setting interpreter to nil #16837
Merged
+7
−7
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
|
I might be doing something wrong, but I tried this branch, and I still get the error "Wrong type argument: stringp, nil" |
|
Can you paste the backtrace here? |
|
My bad, long story short I am not well versed in pointing to different remotes so I wasn't testing what I thought I was testing. In short, this does seem to fix the issue for me, but I think it would be worth someone else validating that the fix works for them too. Thanks for your work on this! 👏 |
|
No problem. I think this should be fine to merge as-is (it worked on my machine as well). |
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.
Close #16836