RetroSearch Browse

Wed Jun 30 23:12:59 CEST 2010 · http://mail.python.org/pipermail/python-dev/2010-June/101249.html

On Wed, Jun 30, 2010 at 12:53, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>> The whole "unexpected" skipping is somewhat of a mess. In an ideal
>> situation modules that are optionally built should be allowed to skip,
>
> While this may be the wide-spread interpretation, it is definitely *not*
> the original intention of the feature.
>
> When Tim Peters added it, he wanted it to tell him whether he did the
> Windows build correctly, INCLUDING ALL OPTIONAL PACKAGES that can
> possibly work on Windows. If you try to generalize this beyond Windows,
> then the only skips that are expected are the ones for tests that
> absolutely cannot work on the platform - i.e. Unix tests on Windows,
> and Windows tests on Unix. Otherwise, if you can get it to pass by
> installing additional software, Tim did *not* mean this to be an
> expected skip.

Interesting. Do you use it that way when you make the Windows build?

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2010-June/101249.html below:

[Python-Dev] OS X buildbots: why am I skipping these tests?