Issue with PYTHONPATH Resolution in git-sync 4.0.0
vgutkovsk opened this issue · 2 comments
When running a script that occasionally executes other scripts synchronized via git-sync
, there's an issue with PYTHONPATH
resolution in the latest version (4.0.0). Despite updating the symbolic link properly, the main script keeps triggering old files from the previous worktree. This problem doesn't occur with git-sync
version 3.6.9, suggesting a potential regression. A comparison between the code for symbolic link creation reveals a change in mechanism: git-sync
4.0.0 now uses os.Symlink
instead of the ln
command. Although the symbolic links created by both versions appear identical, the issue persists. Assistance in debugging this matter would be greatly appreciated.
os.symlink and ln call the same syscalls. I doubt very much that this is the issue.
Could it be a case of something which has a CWD in the old worktree maybe?
Can you help. Me boil down a repro case?