[issue5211] Fix complex type to avoid coercion in 2.7.
Mark Dickinson
report at bugs.python.org
Wed Feb 11 09:56:55 CET 2009
Mark Dickinson <dickinsm at gmail.com> added the comment:
Comment by gumtree copied from issue3734 discussion:
> While Mark Dickinson's patch fixes the documentation, it does not
offer
> a solution to the original problem, which was rooted in a need to
> provide special behaviour based on the numeric types. I made the
> original posting because I hoped that this problem could be resolved.
gumtree, would you be interested in working on a patch for this feature-
request? As mentioned above, the necessary changes are already present
in 3.x, so all that's entailed is figuring out which bits of the
Object/complexobject.c in the py3k source need to be transferred to the
trunk, and making sure that everything's properly tested.
Alternatively, could you explain in a little more detail why this change
is important to you? Subclassing complex doesn't seem like a very
common thing to want to do, so I'm curious about your use case.
----------
nosy: +gumtree
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5211>
_______________________________________
More information about the Python-bugs-list
mailing list