I understand what your saying and I do use that approach at times but I don't think it is ideal for what I'm looking at. Maybe I should explain further.
While developing an application I might create a module in the applications modules directory. Then working on another application I see a need for that module from the first app. I could copy the module to the second application's module directory but that would create duplicate code. Instead I created an application called 'shared' used solely for it's modules directory. It acts as a library of these utility modules. All applications import from the shared modules as needed. It's working but feels a bit of a hack. With the changes to the import in 1.96.x, I thought there might be a better approach. I wonder if I should be using the site-packages directory instead of a shared app.
