When using SSH launcher on machine A and machine B. if machine a is missing module x and machine b has it: I do dv.execute('import x') the exception lists [n:apply]: ImportError: No module named x where n is the engine number. n should only encompass engine numbers from machine A. But the import error is raised by all engines even though some can import the package.
example:
CompositeError: one or more exceptions from call to method: _execute
[0:apply]: ImportError: No module named tardis
[1:apply]: ImportError: No module named tardis
[2:apply]: ImportError: No module named tardis
[3:apply]: ImportError: No module named tardis
[4:apply]: ImportError: No module named tardis
[5:apply]: ImportError: No module named tardis
[6:apply]: ImportError: No module named tardis
[7:apply]: ImportError: No module named tardis
[8:apply]: ImportError: No module named tardis
[9:apply]: ImportError: No module named tardis
[10:apply]: ImportError: No module named tardis
[11:apply]: ImportError: No module named tardis
[12:apply]: ImportError: No module named tardis
[13:apply]: ImportError: No module named tardis
although rc[13].execute('import tardis') works fine, whereas rc[1].execute('import tardis') throws an error as it should.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4