ty resolves symlinks when going to source #2523

Activity

1. AlexWaygood

   added

   serverRelated to the LSP serverRelated to the LSP server

   on Jan 15, 2026
2. MichaReiser commented on Jan 16, 2026

   

   MichaReiser

   on Jan 16, 2026 · Hidden as resolved

   show commentMore actions
3. MichaReiser commented on Jan 16, 2026

   

   MichaReiser

   on Jan 16, 2026

   Member

   More actions

   Does this apply to project files or only to third-party files (pandas, etc)? We're very careful not to canonicalize paths and do so only in very few instances. But I'd have to take a closer look at what's happening.

   What steps should I use to reproduce this? E.g. is it something like:

   lib.py:

   class A: ...
   

   main.py:

   from lib import A
   
   a = A()
       ^ click here
4. Boon-in-Oz commented on Jan 27, 2026

   

   Boon-in-Oz

   on Jan 27, 2026

   Last edited by Boon-in-Oz

   Author

   More actions

   Ah, so it doesn't happen in a nice clean example like that. The key here seems to be that we also use a .pth file.

   In my workspace, my Python interpreter

   		"python.defaultInterpreterPath": "${workspaceFolder}/../python3.10.11/python.exe",
   

   has an associated .pth file in its Lib/site-packages dir, listing packages by relative path, eg

   ../../../packages/package_one/1.0/python
   ../../../packages/package_two/1.0/python
   

   (They are in version subdirectories because we use Rez most of the time now. The .pth file is hopefully on its way out but we're not there yet.)

   If lib.py and main.py are in the package_one/1.0/python/package_one directory, and main.py says

   from package_one.lib import A
   

   then clicking on A or lib and hitting F12 would take me out of my project files to lib.py in the physical location.
5. carljm

   added

   navigationGo-to definition, declaration, implementation, and type; find references, symbols, and hierarchiesGo-to definition, declaration, implementation, and type; find references, symbols, and hierarchies

   on Aug 4, 2026