Skip to content

Simple import completion bug #846

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.

Sign up for GitHub

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

Jump to bottom
Closed
thomasballinger opened this issue Aug 23, 2020 · 1 comment
Closed

Simple import completion bug #846

thomasballinger opened this issue Aug 23, 2020 · 1 comment

Comments

@thomasballinger
Copy link
Member

Import completion of numpy isn't working for me, I tried Python 3.7 and 3.6. However I bet this is cause by #845 and I just haven't gotten to the directory that numpy is in yet.

tomb ~$ virtualenv importest
Using base prefix '/usr/local/Cellar/python/3.7.7/Frameworks/Python.framework/Versions/3.7'
New python executable in /Users/tomb/importest/bin/python3.7
Also creating executable in /Users/tomb/importest/bin/python
Installing setuptools, pip, wheel...done.
tomb ~$ source importest/bin/activate
(importest) tomb ~$ pip install --quiet bpython numpy
(importest) tomb ~$ bpython
bpython version 0.19 on top of Python 3.7.7 /Users/tomb/importest/bin/python3.7
>>> import num<tab>

numpy doesn't complete!
@sebastinas sebastinas added the bug label Oct 11, 2020
@sebastinas sebastinas added this to the release-0.21 milestone Oct 11, 2020
@sebastinas
Copy link
Contributor

Indeed, at the point import completion hasn't discovered numpy. Once it has, everything works as expected.

@sebastinas sebastinas removed this from the release-0.21 milestone Oct 11, 2020
@sebastinas sebastinas removed the bug label Oct 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sebastinas @thomasballinger