It seemed to me that the whole point of distinguishing between built-in modules
and other modules here was that one does not want to invoke the the existing
URI resolution mechanisms. Wanting to keep this spirit of the existing code, I
proposed this solution. If that's not needed, then that's fine with me.
(The one thing that I'm not extremely fond of is that we would invoke
exceptions to find the answer to a simple question, but I can live with that.)
Obviously going through the URIMapper mechanism would have the great advantage
of not forcing the user of the API to find out which modules are "internal" and
which ones aren't. This would also make programs written agains this API more
robust wrt. to changes in the internal/external classification of modules.
Your team Zorba Coders is subscribed to branch lp:zorba.
Mailing list: https://launchpad.net/~zorba-coders
Post to : email@example.com
Unsubscribe : https://launchpad.net/~zorba-coders
More help : https://help.launchpad.net/ListHelp