|
#1
|
|||
|
|||
Exception in module vizjoy
Dear all,
while modifying our scripts I ran into an exception from the vizjoy module. While it is not much of a problem because the exception is thrown when closing the simulation, I'd like to get rid of it because it could obscure a true error. The programming goes like this: script.py Code:
import A : A.go() Code:
import B import vizjoy : status = True : def go(): : B.start() status = ... : viz.go() Code:
import A def start(): """does some inits and install callbacks""" def react(): if A.status: : Exception TypeError: "'NoneType' object is not callable" in <bound method _JoystickCleanup_.__del__ of <vizjoy._JoystickCleanup_ instance at 0x04787418>> ignored Appreciate any hints, ideas and even solutions... BR Walter
__________________
21 is only half the truth. |
#2
|
|||
|
|||
The next release of Vizard should prevent this exception from occurring. Either way, it would be best if you could prevent the circular import. Can you place the status field in the B module?
|
#3
|
|||
|
|||
Hi farshizzo,
thanks for this idea. From a conceptual viewpoint, the status variable belongs to module A, as the status is updated there. Module B only references the status, and was designed to only be an optional module. Being practical, I agree that this should solve the problem. Thank you. BR Walter
__________________
21 is only half the truth. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
'module' object is not callable??? | tokola | Vizard | 2 | 11-21-2012 11:48 AM |
physics engine exception | ad_astra | Vizard | 3 | 03-25-2009 12:31 PM |
Free data table GUI module | Gladsomebeast | Vizard | 1 | 12-23-2008 12:30 PM |
Fading/lightening-Problem and viz.go in module | Johannes | Vizard | 6 | 09-02-2005 05:28 PM |
vhil module | vadrian | Vizard | 2 | 01-27-2005 12:52 PM |