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
readline update #50083
Comments
Attached is a patch file that will update the readline functionality of |
This bug was reported in Arch (http://bugs.archlinux.org/task/15548) and |
The patch should be broken into several, one for each bug fix or Remarks and questions:
|
Some clarification about the rest of the patch: -- We tested the readline fix with version 5.2 and it seemed to work, we -- When I supplied the patch I supplied the patch that we use when -- We put this here since it never really seemed to be an advanced If you would like me to resubmit the patch as smaller components I can |
Arch Linux devs have split the patch and applied only the extra-space |
I've committed the readline 6.0 fix to trunk, py3k and 3.1. I'll commit |
Now backported to py3k in r75747. |
msg94560 should read "backported to the 2.6 branch". can we close the |
Well there's something else in the original patch, although I don't care |
How should we move forward with this issue? I can also try to split the patch, but what branch should I target: py3k? |
As mentioned above, the readline 6 compatibility code was checked in. |
I have no problem splitting the patch into multiple files. When I do so, do I place them here or open separate tickets for each component? Or if you guys want to just close out the ticket since the actual bug was fixed, I am okay with that too. We will probably continue to use the patched version of tabexpand for our users since the filename expansion is used quite heavily. And since we will not be transitioning to py3k anytime in the next several years, we have no issue with what is (or is not) implemented there. |
Bug was fixed. Enhancements are out of date for 2.x and OP will not pursue for 3.x, and should be a separate issue anyway. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: