-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
interactive() readline history chokes on UTF-8 characters #1004
Comments
Yup. Welcome to Python2! If you are sending Alternately, I recommend setting a default encoding for your system, and setting an appropriate header. https://stackoverflow.com/questions/2276200/changing-default-encoding-of-python |
so you don't think that pwntools should catch this error ? |
Technically this introduces issues with e.g. 'unhex ffdf | python foo.py' if foo.py uses .interactive(). However, that was already broken for other reasons. Fixes Gallopsled#1004
After some sleep, I see that the issue you're reporting is different than I was expecting. |
Technically this introduces issues with e.g. 'unhex ffdf | python foo.py' if foo.py uses .interactive(). However, that was already broken for other reasons. Fixes #1004
great, ty ! |
Technically this introduces issues with e.g. 'unhex ffdf | python foo.py' if foo.py uses .interactive(). However, that was already broken for other reasons. Fixes Gallopsled#1004 (cherry picked from commit ebbe917)
I haven't tried replicating this, but from the commit log, it seems to have only been fixed for dev? |
Hmm, nope. It just didn't go through a PR when pushed into stable. |
test.py (doesn't work from inside REPL):
löl
<ENTER>
.The text was updated successfully, but these errors were encountered: