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 terry.reedy
Recipients BreamoreBoy, alexis, eric.araujo, henry.precheur, ncoghlan, tarek, terry.reedy
Date 2014-06-28.16:41:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403973673.21.0.315652369475.issue12420@psf.upfronthosting.co.za>
In-reply-to
Content
I feel that conscientious users who test their installations should get a clean test. They cannot be expected to know that this is an 'expected failure' and therefore not really a failure.

Test_tools has the following, which indeed works to skip on installed 3.4.1 but not on built 3.4.1+.

if not sysconfig.is_python_build():
    # XXX some installers do contain the tools, should we detect that
    # and run the tests in that case too?
    raise unittest.SkipTest('test irrelevant for an installed Python')

How about we decorate the two failing tests
   line 156, in test_optional_extension # or
   line 316, in test_get_outputs
with
@unittest.skipUnless(sysconfig.is_python_build(),
'test irrelevant for an installed Python')  # or modify message
?
History
Date User Action Args
2014-06-28 16:41:13terry.reedysetrecipients: + terry.reedy, ncoghlan, tarek, eric.araujo, henry.precheur, alexis, BreamoreBoy
2014-06-28 16:41:13terry.reedysetmessageid: <1403973673.21.0.315652369475.issue12420@psf.upfronthosting.co.za>
2014-06-28 16:41:13terry.reedylinkissue12420 messages
2014-06-28 16:41:12terry.reedycreate