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 jaraco
Recipients Anthony Sottile, Zac Hatfield-Dodds, domdfcoding, jaraco, kj, miss-islington, steve.dower
Date 2021-06-06.15:04:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1622991897.31.0.903760261188.issue44246@roundup.psfhosted.org>
In-reply-to
Content
The line where the failure occurs is the point where it's checking that the warning was issued. The fact that a StopIteration is raised indicates that no warnings were caught. I can think of a couple of scenarios where that could happen:

- That warning is somehow disabled.
- The `Distribution` object returned by `distribution('distinfo-pkg')` is somehow an older implementation (perhaps an older importlib_metadata is present).

Given that the DeprecationWarnings aren't missed on other tests, the latter seems to be a more likely candidate.

I notice that the regular tests are passing. It's only in the 'appx' environment where the test fails. I'm not familiar with appx, but it seems likely that something from the appx environment creation is a factor in the divergent behavior.

Steve, can you advise on how appx environments are created and how one could replicate a test failure that only occurs in that environment?
History
Date User Action Args
2021-06-06 15:04:57jaracosetrecipients: + jaraco, steve.dower, Anthony Sottile, Zac Hatfield-Dodds, miss-islington, domdfcoding, kj
2021-06-06 15:04:57jaracosetmessageid: <1622991897.31.0.903760261188.issue44246@roundup.psfhosted.org>
2021-06-06 15:04:57jaracolinkissue44246 messages
2021-06-06 15:04:57jaracocreate