Skip to content
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

Fix anytree version upgrade issues #6072

Closed
vorpal-buildbot opened this issue Feb 13, 2019 · 8 comments
Closed

Fix anytree version upgrade issues #6072

vorpal-buildbot opened this issue Feb 13, 2019 · 8 comments
Assignees
Labels
+ bug * monolith Concerns the repo as a whole / upstream

Comments

@vorpal-buildbot
Copy link
Contributor

Reported on Discord by bakert#2193

@triage-new-issues triage-new-issues bot added the triage Used by bot to label unlabeled tasks, will be removed automatically upon labeling label Feb 13, 2019
@bakert bakert self-assigned this Feb 17, 2019
@bakert bakert added + bug / upstream * monolith Concerns the repo as a whole labels Feb 17, 2019
@triage-new-issues triage-new-issues bot removed triage Used by bot to label unlabeled tasks, will be removed automatically upon labeling labels Feb 17, 2019
@bakert
Copy link
Member

bakert commented Feb 17, 2019

/usr/local/lib/python3.7/site-packages/py/_path/local.py:668: in pyimport
    __import__(modname)
decksite/__init__.py:38: in <module>
    from . import api as API, admin # isort:skip # pylint: disable=wrong-import-position, unused-import
decksite/api.py:5: in <module>
    from decksite import APP, auth, league
decksite/league.py:10: in <module>
    from decksite.data import competition, deck, match, person, query
decksite/data/competition.py:6: in <module>
    from decksite.data import archetype, deck, query
decksite/data/archetype.py:15: in <module>
    class Archetype(Container, NodeMixin):
E   TypeError: multiple bases have instance lay-out conflict

@bakert
Copy link
Member

bakert commented Feb 17, 2019

Asked the anytree devs at c0fec0de/anytree#77

@bakert
Copy link
Member

bakert commented Feb 18, 2019

I raised this with the Munch devs, too – Infinidat/munch#39 – although I'm less hopeful that they'll see it as anything to do with them than anytree.

@bakert
Copy link
Member

bakert commented Feb 19, 2019

Much devs believe that because Munch derives from dict it uses __slots__ and NodeMixin probably now does same. I wonder if the right answer here is to freeze anytree version forever.

@bakert
Copy link
Member

bakert commented Feb 20, 2019

Got a reply from anytree too but no path forward better than freezing anytree version so far.

Can also make the node behavior hang off a Container.node attribute instead of being mixed in but that's an irritating rewrite.

@bakert
Copy link
Member

bakert commented Mar 17, 2019

Nothing from anytree. Not really any good paths forward here. Everything works at least.

@bakert
Copy link
Member

bakert commented Aug 6, 2019

No anytree release since 2.6.0.

@bakert
Copy link
Member

bakert commented Oct 31, 2019

anytree devs fixed it in 2.7.0!

@bakert bakert closed this as completed Oct 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
+ bug * monolith Concerns the repo as a whole / upstream
Projects
None yet
Development

No branches or pull requests

2 participants