This project has moved and is read-only. For the latest updates, please go here.

Intellisense, PTVT 2.0 and PyQt4

Aug 25, 2013 at 1:51 AM
I have the following problem, when using PyQt4 the intellisense does not go deeper than PyQt4.QtCore or PyQT4.QtGui. I have seen there was a similar problem 1-2 years ago for an older version of PTVS, is there maybe something missing? Or should i look for particular settings in options?

Best wishes
Aug 25, 2013 at 6:20 AM
There was a major bug in beta that caused problems with pretty much all native modules (.pyd), including Qt - (this was probably the old bug that you're referring about, but it was reactivated for the new problem in beta because the symptoms were similar).

This has since been fixed, and the fix - along with a slew of other fixes that considerably improve overall code completion for PyQt and PySide - will be included in the upcoming 2.0 RC release.

The fix is also available in our source code repository, so if you get the most recent bits and build them yourself, you can try it out right away.
Sep 10, 2013 at 9:45 PM
RC is now out! We paid special attention to good code completion for PyQt and PySide there, so any feedback on how it works in real-world Qt apps would be highly appreciated.
Sep 13, 2013 at 1:33 PM
Edited Sep 13, 2013 at 1:34 PM
Thank you very much for the information. Unfortunately, i cannot give much information on PyQt4 right now, because i had to switch due to other reasons to wxPython for my current Project...

however, i found some other occasions were the code completion is not working in my current project:

in wxpython:
  • has no further completions - until wx.lib.pubsub it works perfectly
in matplotlib:
import matplotlib.pyplot as plt

test should be a list of matplotlib lines, however it does not give any code completion. Another issue is with axes. There seems to be general problems in crawling through the matplotlib api, but this probably also due to the strange architecture of this library:)

Anyway thank you for your response!
Sep 13, 2013 at 9:37 PM
Thanks for reporting these! I was able to reproduce both bugs, and created issues to track them: