This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | gvanrossum |
|---|---|
| Recipients | amaury.forgeotdarc, barry, eikeon, glyph, gvanrossum, jek, ncoghlan, rhettinger, schmir |
| Date | 2008年06月27日.18:05:08 |
| SpamBayes Score | 0.0033122431 |
| Marked as misclassified | No |
| Message-id | <1214589911.25.0.37759524958.issue2235@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Thanks for giving this some time. I think that backwards compatibility should be a higher priority than being able to issue -3 warnings -- if the warnings can't be generated, too bad, we'll just have to document it. (I don't think that checking things at class scope is an easy task in 2to3, though I may be underestimating it.) So, concluding, insofar as the proposal is to revert 2.6 to the 2.5 semantics where it comes to __eq__ and __hash__, I'm okay with that if there's no other way to maintain backwards compatibility, even though my preference would be to still flag this when -3 is specified. (There may be similar backwards compatibility issues caused by stricted arg checking in __new__ and __init__ -- the same remarks apply there.) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年06月27日 18:05:11 | gvanrossum | set | spambayes_score: 0.00331224 -> 0.0033122431 recipients: + gvanrossum, barry, rhettinger, amaury.forgeotdarc, ncoghlan, schmir, jek, eikeon, glyph |
| 2008年06月27日 18:05:11 | gvanrossum | set | spambayes_score: 0.00331224 -> 0.00331224 messageid: <1214589911.25.0.37759524958.issue2235@psf.upfronthosting.co.za> |
| 2008年06月27日 18:05:09 | gvanrossum | link | issue2235 messages |
| 2008年06月27日 18:05:08 | gvanrossum | create | |