You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
autoimport.sqlite uses the relative path as module name #823
Describe the bug
There seems to be a difference in the resolution of the module name in autoimport.sqlite and in autoimport.pickle. I don't know if this different logic was intentional when the new implementation was written.
In the sqlite implementation, the function starts at the root level of the project and goes down to the file. Along the way, all folder names are added to the modname.
Editor information (please complete the following information):
Project Python version: 3.13.7
Rope Python version: You can use rope as a lib to reproduce the behavior
Rope version: 1.14.0
Text editor/IDE and version: You can use rope as a lib to reproduce the behavior
Additional context
I know that the project structure is a little unusual. Perhaps the solution is that I need to change it and that the sqlite implementation is doing everything right.
Our project is an AWS Lambda function, and another folder contains a project with the code for an ECS task. Both should have access to the code in the shared folder, which is why the shared folder is included as an editable dependency.
Activity