Message132867
| Author |
rhettinger |
| Recipients |
eric.araujo, ezio.melotti, michael.foord, rhettinger, terry.reedy |
| Date |
2011年04月03日.18:27:10 |
| SpamBayes Score |
0.03204105 |
| Marked as misclassified |
No |
| Message-id |
<1301855232.35.0.674535345471.issue9424@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
It probably would have been okay to remove assertDictContainsSubset which had nearly zero uptake (according to Google's code search). That's probably because it addresses an uncommon use case, because it was only recently introduced, and because its arguments were in the wrong order.
That situation is much different that assertEquals and friends that have been around for a long time.
I don't care much how this gets resolved; just wanted to point-out that there is much less of a reason to keep assertDictContainsSubset.. |
|