Skip to content

Conversation

@jaraco
Copy link
Contributor

@jaraco jaraco commented Jan 3, 2017

These two commits attempt to better document and communicate the subtle and rare condition where add_metaclass is not suitable. It doesn't solve #127, but it does at least attempt to help alleviate the mystery and surprise.

but in the rare case where the parent has a metaclass that is a
superclass of the metaclass used with the decorator, this approach will
fail with a TypeError. See `issue 127
<https://github.com/benjaminp/six/issues/127>`_ for details.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 I have wondered about this myself. I've never actually encountered the scenario directly but I had considered it. This is worth warning about.

@jaraco
Copy link
Contributor Author

jaraco commented Dec 29, 2018

I've resolved the conflicts in the PR.

@embray
Copy link
Contributor

embray commented Jan 10, 2019

I'm not positive but I think this might superseded by #211. Nevermind, maybe not.

@jaraco jaraco closed this by deleting the head repository Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants