Message11644

Author	stefan.richthofer
Recipients	jeff.allen, stefan.richthofer, zyasoft
Date	2017-11-03.14:51:55
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1509720716.08.0.213398074469.issue2638@psf.upfronthosting.co.za>
In-reply-to

Content
To let PyShadowString perform __eq__, PyString's __eq__ would still have to check for PyShadowString and return PyNotImplemented on this to leverage PyShadowString's own __eq__, wouldn't it? If there's a way to get rid of ShadowString as builtin type that would be fine. I would just regard this low priority for now. Especially given that it won't migrate to Jython 3.

To let PyShadowString perform __eq__, PyString's __eq__ would still have to check for PyShadowString and return PyNotImplemented on this to leverage PyShadowString's own __eq__, wouldn't it?

If there's a way to get rid of ShadowString as builtin type that would be fine. I would just regard this low priority for now. Especially given that it won't migrate to Jython 3.

History
Date	User	Action	Args
2017-11-03 14:51:56	stefan.richthofer	set	messageid: <1509720716.08.0.213398074469.issue2638@psf.upfronthosting.co.za>
2017-11-03 14:51:56	stefan.richthofer	set	recipients: + stefan.richthofer, zyasoft, jeff.allen
2017-11-03 14:51:55	stefan.richthofer	link	issue2638 messages
2017-11-03 14:51:55	stefan.richthofer	create