-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python modules are removed #781
Comments
Currently looking at the following areas for potential issues: builder/abstractcomponent.py: if not 'component_config.py' in bpymorse.get_texts().keys(): |
Hi David @battledj , after a bit of digging, this is a Blender bug: when appending a Blender object from an external file (see morse/src/morse/builder/abstractcomponent.py Line 650 in a64dcec
morse/src/morse/builder/abstractcomponent.py Line 714 in a64dcec
I have opened an issue on the Blender bug tracker: and I prefer to wait for their input before implementing a MORSE specific fix. The procedure to reproduce the bug outside of the MORSE scope is detailed in the bug report. |
That's some good detective work Jeremy. I saw no evidence of a Morse
issue either.
I'd be very interested in the feedback when you receive it.
Cheers,
David.
…On 31/01/18 22:20, Jeremy Nicola wrote:
Hi David @battledj <https://github.com/battledj> ,
after a bit of digging, this is a Blender bug: when appending a
Blender object from an external file (see
https://github.com/morse-simulator/morse/blob/a64dcec89931304c93ac0b18cbe1ec8f211619b7/src/morse/builder/abstractcomponent.py#L650
and
https://github.com/morse-simulator/morse/blob/a64dcec89931304c93ac0b18cbe1ec8f211619b7/src/morse/builder/abstractcomponent.py#L714
in morse/src/morse/builder/abstractcomponent.py), only the Python
scripts attached to the object are also imported, not the modules.
I have opened an issue on the Blender bug tracker:
https://developer.blender.org/T53960
and I prefer to wait for their input before implementing a MORSE
specific fix.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#781 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AiMSzVioU8WafTlLCZGOTN1yDJhrHd7Xks5tQExwgaJpZM4RujsW>.
|
So, according to the Blender developpers it is not a bug, but a feature :) So we'll go the MORSE specific patch way. |
On 01/02/18 20:22, Jeremy Nicola wrote:
So, according to the Blender developpers it is not a bug, but a feature :)
https://developer.blender.org/T53960
So we'll go the MORSE specific patch way.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#781 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AiMSzfuLnWv1wxctkxBy5vCsZ80kclLXks5tQYJFgaJpZM4RujsW>.
That's a bit unfortunate. I can't see how that could be construed as a
feature.
|
Following the issue reported by David Battle in https://sympa.laas.fr/sympa/arc/morse-users/2018-01/msg00013.html
It seems python modules are removed from Blender objects in MORSE.
Minimal builder file to reproduce the issue:
See attached simulation environment from david on the mailing list.
Todo:
The text was updated successfully, but these errors were encountered: