From 8af36acbd2238299e62795198488b682a8099853 Mon Sep 17 00:00:00 2001
From: Robie Basak <robie@justgohome.co.uk>
Date: Sat, 7 Mar 2020 19:11:26 +0000
Subject: [PATCH] Mark upstream-only test

It doesn't make sense for downstream redistributors to run this test,
since they might be using a newer version of Python with additional
symbols which won't be reflected in trio.socket, and this shouldn't
cause downstream test runs to start failing.

Origin: backport, https://github.com/python-trio/trio/commit/0dcfbbf53056ae33c85f686d7e8a1b03a3e03a34
Last-Update: 2020-03-10
---
 setup.cfg                  | 2 ++
 trio/tests/test_exports.py | 5 +++++
 2 files changed, 7 insertions(+)

--- a/trio/tests/test_exports.py
+++ b/trio/tests/test_exports.py
@@ -49,6 +49,11 @@
 NAMESPACES = list(public_namespaces(trio))
 
 
+# It doesn't make sense for downstream redistributors to run this test, since
+# they might be using a newer version of Python with additional symbols which
+# won't be reflected in trio.socket, and this shouldn't cause downstream test
+# runs to start failing.
+@pytest.mark.redistributors_should_skip
 # pylint/jedi often have trouble with alpha releases, where Python's internals
 # are in flux, grammar may not have settled down, etc.
 @pytest.mark.skipif(
--- a/setup.cfg
+++ b/setup.cfg
@@ -1,6 +1,8 @@
 [tool:pytest]
 xfail_strict = true
 faulthandler_timeout = 60
+markers =
+    redistributors_should_skip: tests that should be skipped by downstream redistributors
 
 [egg_info]
 tag_build = 
