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