-
Notifications
You must be signed in to change notification settings - Fork 133
Go to reference is not working for a relative import * #730
Comments
@tmab2003 - could you please list structure of your workspace. Is "python.analysis.downloadChannel": "beta" |
@MikhailArkhipov - I added that setting string to the settings.json file for my workspace - will that be adequate?
The structure is as follows: ../RootFolderForProject/Folder_1/Folder_2/Folder_3/Folder_4/scenarios/module_1.py file_1 which is here: ../RootFolderForProject/Folder_1/Folder_2/Folder_3/Folder_4/Folder_5/Folder_6/file_1.py which is why I have to import with three dots, from ...scenarios import * (which should import all modules_*.py).. |
I assume you are opening |
Yes RootFolderForProject is the workspace folder. The code works and other Python IDEs seem to navigate this just fine. |
@AlexanderSher , @MikhailArkhipov - I am not sure if the issue was fixed...but the relative import doesn't seem to be working for relative paths with |
Are you saying the imports don't work, or go to references? The latter is not in the language server until #819 is merged. |
Go to references indeed. Thanks for the update @jakebailey! |
@tmab2003 commented on Mon Mar 11 2019
I have the following in my main module:
file_1
#file_1.py
from ...scenarios import *
module_1.method_1()
Where I have a module called 'module_1' in the
scenarios
package which has a method defined 'method_1'and I cannot seem to F12 in to any of these modules or methods.
The text was updated successfully, but these errors were encountered: