Message132044
| Author |
pitrou |
| Recipients |
brett.cannon, eric.araujo, pitrou, r.david.murray |
| Date |
2011年03月24日.21:59:58 |
| SpamBayes Score |
1.0319895e-10 |
| Marked as misclassified |
No |
| Message-id |
<1301003996.3957.25.camel@localhost.localdomain> |
| In-reply-to |
<1300918579.86.0.407981739941.issue10966@psf.upfronthosting.co.za> |
| Content |
> The attached patch has both the code to make test skipping more
> obvious as well as eliminating the concept of expected skips.
I still don't like the idea that we have to hand-maintain lists of
"optional" or "required" platforms. It is not more manageable than the
list of "expected" tests.
For example:
-import_module('_ctypes')
+import_module('_ctypes', optional=['openbsd3', 'netbsd3'])
there are other platforms where _ctypes is not supported. We don't want
to maintain a list of them.
Same for:
+pty = import_module('pty',
+ optional=['win32', 'os2emx', 'freebsd4', 'freebsd5', 'freebsd6',
+ 'freebsd7', 'freebsd8'])
Do you want to keep track of the specificities of each version of the *BSDs?
I'm not sure why you have "optional" and "required_on". Either
"optional" and "required", or "optional_on" and "required_on", would be
more logical (the former looks less verbose to me). |
|