vscode-python: Symbol navigation unpredictable and slow when using PySide
Issue Type: Bug
- Save this as a .py file:
from PySide import QtCore, QtGui
class Something():
def __init__(self):
pass
def main():
pass
obj = Something()
- Press ctrl+shift+O
- On the first try it usually symbols load fast and as expected
- Now press ctrl+shift+O again
- Message ‘no symbol information for the file’ appears in lineEdit but symbols load within 2-6 seconds
- If you make a change to e.g. the vscode settings at this point it works again once and then you can basically repeat the above pattern
- If you remove the ‘from PySide import QtCore, QtGui’ line, everything works fine This issue affects code completion as well.
Extension version: 2018.4.0 VS Code version: Code 1.23.1 (d0182c3417d225529c6d5ad24b7572815d0de9ac, 2018-05-10T17:11:17.614Z) OS version: Windows_NT x64 10.0.17134
System Info
| Item | Value |
|---|---|
| CPUs | Intel® Core™ i5-3550 CPU @ 3.30GHz (4 x 3293) |
| GPU Status | 2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: disabled_software video_decode: enabled video_encode: enabled vpx_decode: enabled webgl: enabled webgl2: enabled |
| Memory (System) | 15.97GB (9.45GB free) |
| Process Argv | C:\Program Files\Microsoft VS Code\Code.exe |
| Screen Reader | no |
| VM | 0% |
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 19 (4 by maintainers)
@fynnay specifically what issues with 64-bit Python on Windows? The core dev in charge of the Windows build is a teammate of ours so I’m sure he would like to know. 😄
@DonJayamanne the ‘easiest’ way of installing PySide on Mac seems to change for every major OSX update. Here are a couple of solutions that worked for me on Yosemite and Sierra in the past: A) Use pip and force a version
B) Use homebrew