Skip to content

Conversation

@damienmarchal
Copy link
Contributor

I suspect this code to have been integrated in the SofaPython3 by mistake and to have never really worked.

By looking at it it may be an experiment to allow syntax like this

import Sofa.Components
Sofa.Components.MechanicalObject()  ...

So let's make it simple, remove this. Unless someone can explain what it does.

I suspect this code to have been integrated in the SofaPython3 by mistake and to have never
worked. By looking at it it may be an experiment to allow syntax like this

import Sofa.Components
Sofa.Components.MechanicalObject()  ...
…nows about them.

The problem:
Depending on the definition order of the binded classes, there may have
incorrect types if Base is useing BaseData... but BaseData is only binded after Base.

The PR propose a solution for that using a decidcated "forward" registration patter.
@hugtalbot hugtalbot changed the title Remove Sofa.Components. Remove Sofa.Components Oct 2, 2024
@damienmarchal
Copy link
Contributor Author

@hugtalbot ci pass...

@fredroy fredroy merged commit 9514a08 into sofa-framework:master Oct 15, 2024
4 checks passed
@alxbilger
Copy link
Contributor

I believe that some parts of this PR should have been in #457

@damienmarchal
Copy link
Contributor Author

I believe that some parts of this PR should have been in #457

I agree with you :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants