comment on module loading in nameko.cli.run about nameko HOT 5 OPEN

Yes, this will be great,
but...
for python 2 we need a lot of code, because we need to aquire import lock, call find_module for each submodule in 'module1.module2.module3'
for python 3 imp is deprecated, and the best choice is to use importlib's find_spec and then load_module, but importlib module has changed between 3.3 and 3.4 (new methods was added, some became deprecated).
So if implement this then there will be deprecated code or a lot of code to handle different import libraries for different python version.
IMHO current solution is hackish, but works and doesn't require a lot of code. so it's more robust

from nameko.

what about werkzeug.utils.import_string?

from nameko.

@rochacbruno, werkzeug.utils.import_string looks ideal

from nameko.

from what i can see, import_string doesn't help distinguishing missing modules from existing modules with bad imports

from nameko.

Ah, I had misremembered what the problem was here. Sadly, werkzeug.utils.import_string doesn't help. You still just get an ImportError.

from nameko.