From 00736e4738a7a53d95dbbcd36667db6f2e473a3f Mon Sep 17 00:00:00 2001
From: Ned Batchelder <ned@edx.org>
Date: Tue, 22 Jun 2021 12:52:01 -0400
Subject: [PATCH] build: pin pylint-test==1.0.3

This avoids mysterious errors:
https://github.com/reverbc/pylint-pytest/issues/20
---
 requirements/constraints.txt | 4 ++++
 requirements/dev.txt         | 6 ++++--
 requirements/quality.txt     | 6 ++++--
 3 files changed, 12 insertions(+), 4 deletions(-)

diff --git a/requirements/constraints.txt b/requirements/constraints.txt
index 94595ab..2de14d0 100644
--- a/requirements/constraints.txt
+++ b/requirements/constraints.txt
@@ -7,3 +7,7 @@
 # link to other information that will help people in the future to remove the
 # pin when possible.  Writing an issue against the offending project and
 # linking to it here is good.
+
+# Not sure why I'm getting cannot-enumerate-pytest-fixtures failures:
+# https://github.com/reverbc/pylint-pytest/issues/20
+pylint-pytest==1.0.3
diff --git a/requirements/dev.txt b/requirements/dev.txt
index 53a3e9f..6673ac4 100644
--- a/requirements/dev.txt
+++ b/requirements/dev.txt
@@ -210,8 +210,10 @@ pylint==2.8.3
     # via
     #   -r requirements/quality.txt
     #   pylint-pytest
-pylint-pytest==1.1.2
-    # via -r requirements/quality.txt
+pylint-pytest==1.0.3
+    # via
+    #   -c requirements/constraints.txt
+    #   -r requirements/quality.txt
 pyparsing==2.4.7
     # via
     #   -r requirements/quality.txt
diff --git a/requirements/quality.txt b/requirements/quality.txt
index 2160bec..c39e42a 100644
--- a/requirements/quality.txt
+++ b/requirements/quality.txt
@@ -168,8 +168,10 @@ pygments==2.9.0
     #   sphinx
 pylint==2.8.3
     # via pylint-pytest
-pylint-pytest==1.1.2
-    # via -r requirements/quality.in
+pylint-pytest==1.0.3
+    # via
+    #   -c requirements/constraints.txt
+    #   -r requirements/quality.in
 pyparsing==2.4.7
     # via
     #   -r requirements/doc.txt