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.

Sign up for GitHub

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

Jump to bottom

zope.proxy does not proxy __unicode__ #3

Closed
tseaver opened this issue Jan 19, 2015 · 1 comment · Fixed by #7
Closed

zope.proxy does not proxy __unicode__ #3

tseaver opened this issue Jan 19, 2015 · 1 comment · Fixed by #7
Labels
bug

Comments

@tseaver
Copy link
Member

tseaver commented Jan 19, 2015

In https://bugs.launchpad.net/zope.proxy/+bug/1262702, @mgedmin reported:

See the failing tests I committed in a branch: 03efa84

I'm not sure how to fix this. It appears that CPython's PyTypeObject doesn't have a tp_unicode slot. Can anyone with more C API experience chime in? How would you define a C class with a custom __unicode__ representation?
@tseaver tseaver added the bug label Jan 19, 2015
@tseaver
Copy link
Member Author

tseaver commented Jan 19, 2015

After the fix for http://bugs.python.org/issue2517 landed (2008), I believe Python no longer consults the instance for __unicode__ lookup, but only the instance's type.

@jamadden jamadden mentioned this issue May 7, 2015
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
1 participant
@tseaver