Hello, I modified the test suite to accept either result. Tests pass with either GMP6.2.0/MPFR4.1.0/MPC1.2.0rc1 or GMP6.1.2/MPFR4.0.2/MPC1.1.0.
The source code has been released via PyPi at https://pypi.org/project/gmpy2/2.1.0b5/#files The same code has also been released via GitHub at https://github.com/aleaxit/gmpy/releases/download/gmpy2-2.1.0b5/gmpy2-2.1.0b5.tar.gz If you encounter any issues please let me know. casevh On Thu, Jul 30, 2020 at 9:10 AM Martin Kelly <mar...@martingkelly.com> wrote: > > On Thu, Jul 30, 2020, 6:48 AM Case Van Horsen <cas...@gmail.com> wrote: >> >> I will update the test suite today. (The offending test will be >> removed from test_gmpy2_format.txt and moved to test_mpfr40_format.txt >> and test_mpfr41_format.txt with the appropriate version chosen.) >> >> Will this release move to MPC 1.2.0? >> >> Case > > > Thanks Case! Matthias, Vincent, would one of you be willing to do a > non-maintainer upload once Case releases the new version? I would like to but > won't have computer access until October. > >> >> On Thu, Jul 30, 2020 at 6:36 AM Martin Kelly <mar...@martingkelly.com> wrote: >> > >> > On Thu, Jul 30, 2020, 5:34 AM Matthias Klose <d...@debian.org> wrote: >> >> >> >> On 7/30/20 3:42 AM, Martin Kelly wrote: >> >> > Apparently this bug is going to cause autoremoval from testing soon. Is >> >> > the >> >> > severity really high enough for that? >> >> >> >> yes, because it blocks migration of mpfr4, used by our GCC packages. I'm >> >> certainly biased, however I'd like to see the new mpfr4 in use now, even >> >> if it >> >> means removing a bindings package from testing. >> > >> > >> > Case Van Horsen (upstream maintainer), is there anything we can do here to >> > fix the tests? I can look at this in October, but the package will be >> > removed from testing at that point. I'm not sure when the package freeze >> > will be, but I certainly don't want to miss the next release. >> > >> > >> >
