-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
gh-121160: Note that readline libraries using different history formats. #121327
Conversation
… formats. This is not something we can do too much about, without help from the underlying libraries.
@Yhg1s, you're the readline expert. Does this look good? |
I'll merge next week. |
Eehh, "expert"... But yeah, I think this is the only thing we can do here. |
Thanks! Expert just means you've signed up for notifications about tricky or controversial changes :) |
Thanks @encukou for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12. |
Thanks @encukou for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry, @encukou, I could not cleanly backport this to
|
… formats. (pythonGH-121327) This is not something we can do too much about, without help from the underlying libraries. (cherry picked from commit 709db44) Co-authored-by: Petr Viktorin <encukou@gmail.com>
GH-122030 is a backport of this pull request to the 3.13 branch. |
GH-122031 is a backport of this pull request to the 3.12 branch. |
…history formats. (pythonGH-121327) This is not something we can do too much about, without help from the underlying libraries. (cherry picked from commit 709db44) Co-authored-by: Petr Viktorin <encukou@gmail.com>
This is not something we can do too much about, without help from the underlying libraries.
The file formats seem to be treated as implementation details, hidden behind API calls.
readline.set_history_length
corrupts history files when used in a libedit build #121160📚 Documentation preview 📚: https://cpython-previews--121327.org.readthedocs.build/