From 82f367a13497c7dfce6274879d8d0dc44b292bc6 Mon Sep 17 00:00:00 2001
From: Oz N Tiram <oz.tiram@gmail.com>
Date: Tue, 21 Jun 2022 15:18:56 +0200
Subject: [PATCH] PIPENV_MAX_ROUNDS is no longer used

Since [this commit][1] removed the usage of piptools
resolver in favor of pip's internal resolver.

[1] 5ef5a59d41385945f2fc7f0e492900921ffc924b
---
 pipenv/environments.py | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/pipenv/environments.py b/pipenv/environments.py
index 70379095aa..b263d241d1 100644
--- a/pipenv/environments.py
+++ b/pipenv/environments.py
@@ -206,12 +206,6 @@ def initialize(self):
         Default is 0. Automatically set to 1 on CI environments for robust testing.
         """
 
-        self.PIPENV_MAX_ROUNDS = int(os.environ.get("PIPENV_MAX_ROUNDS", "16"))
-        """Tells Pipenv how many rounds of resolving to do for Pip-Tools.
-
-        Default is 16, an arbitrary number that works most of the time.
-        """
-
         self.PIPENV_MAX_SUBPROCESS = int(os.environ.get("PIPENV_MAX_SUBPROCESS", "8"))
         """How many subprocesses should Pipenv use when installing.