Richard Jolly wrote at 2004-2-4 12:20 +0000:
... Root A methx_search B methx_search
The methx's contain sql statements pointing to different databases, and the error messages I get are sql errors ( 'no column ...' ), which is why its pretty clear which one is being called.
I couldn't find any obvious reason why the wrong one was being called, but I found I could disambiguate the external methods by renaming them A_methx_search and B_methx_search in the ZMI, and saving the methods to reload them. This worked, albeit proving I don't understand the root of the problem, however...
You want to understand how acquisition works. Especially, you want to focus on "Containment before Context". Google to find relevant documents...
... Finally, when I have .py files only, no .pyc files are generated, which I find slightly confusing.
External Methods do not use Python's normal import facility but instead read in the methods. That's why no "*.pyc" files are generated. -- Dieter