-
Notifications
You must be signed in to change notification settings - Fork 81
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
Tab completion under pew? #150
Comments
Confirmed here. |
the following code activates tab completion: import rlcompleter, readline
readline.parse_and_bind('tab: complete') |
The above
Maybe we have different arrangements for accessing a readline library on our respective machines even though we are both using macOS. |
This reminds me of #90 :/ Unfortunately, this is another bit of behavior due to virtualenv (and that would be solved by a rewrite) (there might be actually another option to prevent this, but it's late and I haven't looked deeply into this) Apparently the rewrite is not happening 😞 . But maybe a minimal rewrite of virtualenv, with just the few features required by us, might be feasible (we wouldn't have this concern, since we could invoke it directly as a library, and avoid conflicts/pollution in the PATH) |
@berdario Want to vendorize virtualenv? |
You mean vendorize and trying to patch this ourselves? I'd rather try to fix it upstream, and add a version bound on the patch that fixed this would be better Or is there another advantage to vendorizing it that I'm missing? |
No, vendorizing just lets us have more control I suppose, but it prevents us from merging any fixes the maintainers put in place. You way makes sense. |
Is this fixed upstream now? I can't reproduce it. Using Ubuntu 20.04, Python 3.8.10, Pew 1.2.0, I do pew mktmpenv
python
imp<TAB> and it autocompletes to |
please add tab completion like |
macOS 10.12.6 Python 3.6.2 pew 0.1.26
When I run the CPython REPL from a standard shell tab completion is operative. When I run it in a sub-shell invoked by pew tab completion is not operative.
Is this a bug, or a configuration failure on my part?
The text was updated successfully, but these errors were encountered: