Systematic decompilation bug in _Framework?

[bolau]

Hi Julien,

first of all - thank you so much for your work on the remote scripts, this is incredible!

I think I've found a systematic bug in the decompilations of _Framework related to Assertions. For example: _Framework/MixerComponent.py:268
The lines below "raise AssertionError" should most probably be unintented one step, otherwise that code is never executed:

if not self._bank_up_button != None:
raise AssertionError
if self.is_enabled(): <<<<<< needs unintent?
new_offset = (value is not 0 or not ...

This seems to occur wherever a raise follows an if.
I guess this is not critical, since nobody will ever execute this. But it's confusing when trying to understand how the stuff works...