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 | rhettinger |
|---|---|
| Recipients | amaury.forgeotdarc, gvanrossum, rhettinger |
| Date | 2008年07月02日.23:24:04 |
| SpamBayes Score | 0.019279445 |
| Marked as misclassified | No |
| Message-id | <1215041045.27.0.978650699893.issue3263@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I don't think we should build in explicit support for bad designs that violate the Liskov substitution principle. Are there any valid use cases for wanting non-hashable subclasses of hashable classes? If for some reason, this feature survives, it would be better to use NotImplemented instead of None. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月02日 23:24:05 | rhettinger | set | spambayes_score: 0.0192794 -> 0.019279445 recipients: + rhettinger, gvanrossum, amaury.forgeotdarc |
| 2008年07月02日 23:24:05 | rhettinger | set | spambayes_score: 0.0192794 -> 0.0192794 messageid: <1215041045.27.0.978650699893.issue3263@psf.upfronthosting.co.za> |
| 2008年07月02日 23:24:04 | rhettinger | link | issue3263 messages |
| 2008年07月02日 23:24:04 | rhettinger | create | |