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
NodeMixin - TypeError: multiple bases have instance lay-out conflict #77
Comments
The Munch folks believe that it's probably because Munch derives from |
Yes.
As |
Thanks for taking a look. Sadly the above code gives the same error.
|
Reading up at https://stackoverflow.com/questions/472000/usage-of-slots and https://docs.python.org/3/reference/datamodel.html#notes-on-using-slots it sounds like including |
I had the same exception the other day when I tried to mix wxPython and the
NodeMixin class. Did not really expect it to work anyway, as wxPython
heavily uses the attribute name parent.
…On Wed, Feb 20, 2019 at 5:15 PM Thomas David Baker ***@***.***> wrote:
Reading up at https://stackoverflow.com/questions/472000/usage-of-slots
and
https://docs.python.org/3/reference/datamodel.html#notes-on-using-slots
it sounds like including __slots__ in something designed to be inherited
from/mixed in might be something you want to revisit? I'm a total ignoramus
so I'm all ears if you have any ideas other than freezing the anytree
version at 2.4.3. Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#77 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFkmCtntGITKeg23zUarK0PgTcmeXIIxks5vPXS8gaJpZM4a_Wyo>
.
|
I am not sure yet, which is the best way to go. Leave |
slots will be removed |
Works: 2.4.3
Breaks: 2.6.0
Where munch is https://github.com/Infinidat/munch
Googling around a bit this seems to be about conflicts in C implementations of classes on
__foo__
attributes. So I did this:but it didn't make me feel much smarter.
Does this mean anything to you anytree peeps? I came here because obviously NodeMixin is meant to be mixed in so this feels like a bug rather than just a stupid thing I should not be attempting to do. Especially as it used to work until this version.
The text was updated successfully, but these errors were encountered: