Error message on startup: Warning: a callable with the name 'X' has already been registered. This is probably not what you want

[stucork]

This looks like a false positive after implementing this feature request:

[Done] Print warning when two server callables have the same name

I think so. In the meantime, note that the Anvil name of a table is global, across your entire account. Change it in one App, and that change is visible across all your Apps. This is independent of its local (per-database) Python name. So changing the global name shouldn’t break any code. I have a standing Feature Request for access to the Account’s complete set of Tables, across all Apps and Databases. Without it, you can’t get a complete picture anywhere. I suppose one could manually c…

The issue I think is that your code is using absolute imports instead of relative imports in a couple of places

Changing code that looks like this:

from ServerModule1 import say_hello

to a relative import

from .ServerModule1 import say_hello

should remove those warnings.

---

More details:
when you do the absolute import python handles it differently to the relative import

it looks inside sys.modules for ServerModule1 which it doesn’t think it has.
(When you do the relative import it looks for MyAppName.ServerModule1 which was already loaded)

Since python doesn’t know it has the module already in memory, it goes and finds it, then re-executes the module, this leads to duplicate functions registered with the same name, hence the warnings.