Update chatgpt.py: fix open() char encoding bug
#58
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
orsnaro
added a commit
to orsnaro/Keyboard-Event-Recorder-tool
that referenced
this pull request
Jun 19, 2024
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.
regarding issue #57
Although I set all open() default encodings to "utf-8" explicitly
here is the main lines in
chatgpt.pythat directly caused the bug:#139
Also in case you asked GPT something like 'what was my last prompts' (given you opened using
python chatgpt.py -r lastswitch for example) this line may cause the same bug if yourGPT-clicould actually resume the previous session and see previous prompts and resend them to you!#107