Message80072
| Author |
jnoller |
| Recipients |
amaury.forgeotdarc, barry, christian.heimes, jnoller, loewis, rhettinger |
| Date |
2009年01月18日.02:35:09 |
| SpamBayes Score |
0.0005973779 |
| Marked as misclassified |
No |
| Message-id |
<1232246110.29.0.153250086775.issue4449@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
FYI, there was a small issue in the patch - namely the only way to get
the
AttributeError to raise in the Value/Array creation is to not pass in a
lock, True/None - the latter two get to a lock/RLock while the
former will have the acquire method. If you pass in False, you
immediately get the RawValue() object back.
I changed the test to reflect this:
self.assertRaises(AttributeError, self.Value, 'i', 5,
lock='navalue')
self.assertRaises(AttributeError,
self.Array, 'i', range(10), lock='notalock') |
|