Ask Your Question

Update from to will cause the source analysis failed to work.

asked 2020-03-31 01:20:16 -0600

hongyi-zhao's avatar

updated 2020-04-01 13:43:47 -0600


I use the package generated from here to update wingide from to But after the upating, I find that the source analysis failed to work and all of the previously resolved completions for the same project were disabled.

I tried to remove all of the caches and change the python interpreter to others and then change it back. But all of my tries are in vain for solving this problem. Finally I revert the update to the original installed version and the problem disappear immediately.

I don't know whether this is a bug of this update.


edit retag flag offensive close merge delete


Are you saying the auto-completer is never showing up or all analysis is failing? You can tell by doing goto-definition on something or seeing if clicking on things and looking at Source Assistant is showing information. If those work but auto-completion does not then please try to see if changing the Editor > Auto-Completion > Non-Latin Script Display preference to Always Display changes the behavior. It may then end up showing the completer when it shouldn't during character composition but it would tell us where the problem lies. Thanks for reporting this!

Wingware Support's avatar Wingware Support  ( 2020-03-31 07:13:53 -0600 )edit

No, the problem is caused by the following: after applying the patch, the auto generating cache for that project will failed to work. And I cannot see any cached stuff for that project under the folder ~/.cache/wingpro7. I check it with the following command in this directory:

# The aiida is the project's virtualenv name whose python interpreter is used by wing for the project:
$ grep -rl 'aiida' *


hongyi-zhao's avatar hongyi-zhao  ( 2020-03-31 09:03:41 -0600 )edit

I'm unclear why you expect the name of your virtualenv to appear in Wing's cache. I don't think it would unless maybe in the autosave area. What is the functionality that is not working in Wing?

Wingware Support's avatar Wingware Support  ( 2020-03-31 09:09:54 -0600 )edit

Could you please submit a bug report from Wing's Help menu and attach the log? Please also include the names of extension modules that are not being scraped.

Wingware Support's avatar Wingware Support  ( 2020-03-31 09:11:50 -0600 )edit

The deep level completions will be unavailable. I use the grep command to confirm the packages/modules belong to the env which have been indexed by wing, so it need the env's name. See the example output shown following if the packages/modules have been indexed corectly by wing:

werner@ubuntu-01:~/.cache/wingpro7$ grep -rl 'aiida' * | head 
pi-cache/3.7/home/werner/.pyenv ...
hongyi-zhao's avatar hongyi-zhao  ( 2020-03-31 09:24:20 -0600 )edit

4 Answers

Sort by ยป oldest newest most voted

answered 2020-04-01 13:43:35 -0600

Update should fix this problem. You can get it with Check for Updates in the Help menu. Thanks for reporting this, and please let us know if you see other issues.

edit flag offensive delete link more

answered 2020-04-01 22:46:12 -0600

hongyi-zhao's avatar

updated 2020-04-01 22:50:34 -0600

Thanks, I've applied this update and all things seem work smoothly till now.


edit flag offensive delete link more

answered 2020-03-31 06:09:01 -0600

Michael's avatar

updated 2020-03-31 06:09:35 -0600

There seems to be more (I'm skipping for the moment an extra bug report):

After updating to on Windows 10 my project cannot longer find any imports( for example: builtins.ModuleNotFoundError: No module named 'cv2'). But the python environment with OpenCV installed seems to be still the same correct one as yesterday (before the update).

edit flag offensive delete link more


Can you please check if sys.executable is the right Python? Also, what Python version/distribution is it and are you using virtualenv or conda envs or the base install? I'm wondering if what you are seeing is not the same as the original question above, which might be explained by a change in our attempts at not showing the auto-completer during character composition. Thanks for reporting this!

Wingware Support's avatar Wingware Support  ( 2020-03-31 07:15:58 -0600 )edit


Yep, my mistake. A parallel new installation of Julia at the same time as the Wing update installed a separate conda environment, making it the default one. All is back to normal now here.

Michael's avatar Michael  ( 2020-03-31 08:01:11 -0600 )edit

Great, thanks for letting us know.

Wingware Support's avatar Wingware Support  ( 2020-03-31 08:09:40 -0600 )edit

answered 2020-03-31 06:50:57 -0600

updated 2020-03-31 07:43:57 -0600

We'll look into this. One idea is to download 7.2.2 from rather than applying an update, in case it's an issue in the update manager. Thanks for reporting this problem!

edit flag offensive delete link more


I installed this one and the problem disappear. In this case, for my project, it will generate a rather large cache file. See the following:

werner@ubuntu-01:~/.cache/wingpro7$ du -BM cache/db/analysis-store-21.sqllite
174M    cache/db/analysis-store-21.sqllite

And if I apply the patch, remove the above cache file and then restart wing, then this file will be regenerated but so small, see the following:

werner@ubuntu-01:~/.cache/wingpro7$ du -BM cache/db/analysis-store-21.sqllite
15M cache/db/analysis-store-21.sqllite


hongyi-zhao's avatar hongyi-zhao  ( 2020-03-31 09:46:06 -0600 )edit

Did you install 7.2.2 from the installer? The log we received was from a 7.2.1 install with an update. The analysis cache file can grow up to the maximum size specified in the Source Analysis page of the Preferences dialog as Wing is used.

Wingware Support's avatar Wingware Support  ( 2020-03-31 11:34:04 -0600 )edit

I send the bug report using a original install of 7.2.1 on which the 7.2.2 update pack was applied. Only in this case, the problem reported here happened.

When I say install 7.2.2, I always mean to install using the original installer of 7.2.2 version.

The default maximum cache file size used by the analysis cache file is 2000M and I always leave it as it is for both test cases reported here. When I check the size of the analysis cache file, I always first remove the old one, and then restart wing let it automatically re-create it.

And I also find that for the case of fresh 7.2.2 install, in order to let it works correctly, I must first remove the update package here: ~/.wingpro7/updates/, otherwise the problem reported here will still happen.


hongyi-zhao's avatar hongyi-zhao  ( 2020-03-31 19:12:37 -0600 )edit

We are working on an update that will fix this issue.

Wingware Support's avatar Wingware Support  ( 2020-04-01 08:54:53 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools



Asked: 2020-03-31 01:20:16 -0600

Seen: 631 times

Last updated: Apr 01 '20