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 mgorny
Recipients mgorny
Date 2018-10-03.10:32:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1538562764.11.0.545547206417.issue34883@psf.upfronthosting.co.za>
In-reply-to
Content
xz-utils has four options to configure codecs supported by liblzma:

  --enable-encoders
  --enable-decoders
  --enable-match-finders
  --enable-checks

In Gentoo, we're using those options to optionally provide smaller footprint liblzma builds that include only the standard set of codecs used by .xz archives (i.e. that work with any archive created by xz/lzma without expert options used).  However, it seems that the CPython test suite wrongly presumes that all codecs are always available and it fails on LZMAErrors when those are not present.

I'm attaching the verbose output of test_lzma.

I think the best solution here would be to catch LZMAError and skipTest() if it's LZMA_OPTIONS_ERROR.  I think this would be best done by exposing the underlying error code in LZMAError exception (rather than string-matching, though the latter would also work).
History
Date User Action Args
2018-10-03 10:32:44mgornysetrecipients: + mgorny
2018-10-03 10:32:44mgornysetmessageid: <1538562764.11.0.545547206417.issue34883@psf.upfronthosting.co.za>
2018-10-03 10:32:43mgornylinkissue34883 messages
2018-10-03 10:32:43mgornycreate