@@ -181,11 +181,16 @@ buildPythonPackage rec {
181181 # some files, like Pipfile, pyproject.toml, requirements.txt and setup.cfg
182182 # are generated by the bootstrap script using m4. these can fetch data from
183183 # build/pkgs, either directly or via sage-get-system-packages.
184− sed -i 's/==2.1.0rc1/>=2.1.1/' ../gmpy2/install-requires.txt
185− sed -i 's/, <3.4//' ../rpy2/install-requires.txt
186− sed -i 's/, <4.3//' ../sphinx/install-requires.txt
187184 sed -i '/sage_conf/d' src/setup.cfg.m4
188185 sed -i '/sage_conf/d' src/requirements.txt.m4
186+
187+ # version lower bounds are useful, but upper bounds are a hassle because
188+ # Sage tests already catch any relevant API breakage.
189+ # according to the discussion at https://trac.sagemath.org/ticket/33520,
190+ # upper bounds will be less noisy starting from Sage 9.6.
191+ sed -i 's/==2.1.0rc1/>=2.1.1/' ../gmpy2/install-requires.txt
192+ sed -i 's/, <[^, ]*//' ../*/install-requires.txt
193+
189194 for infile in src/*.m4; do
190195 if [ -f "$infile" ]; then
191196 outfile="src/$(basename $infile .m4)"