andyvand / gmpy

Automatically exported from code.google.com/p/gmpy
GNU Lesser General Public License v3.0
0 stars 0 forks source link

next_prime returns incorrect results #84

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. using gmpy v1.15 and v1.17: function 'next_prime' calcs non prime numbers:
73705633, 54470491, 18790021, 16661633
2. but gmpy2.next_prime works correct.
3. gmpy v1.14 works correct too.

What is the expected output? What do you see instead?
-

What version of the product are you using? On what operating system?
gmpy v1.14, v1.15, v1.17
gmpy2 v2.03
Windows 7 x64

Please provide any additional information below.

Original issue reported on code.google.com by spobezhi...@gmail.com on 22 Jan 2014 at 11:44

GoogleCodeExporter commented 9 years ago
This is caused by a bug in the MPIR 2.6.0 library that is used for the Windows 
builds. gmpy2 2.03 is built with a patched version of MPIR that fixes the bug. 
The best answer is to use gmpy2 2.03.

Original comment by casevh on 22 Jan 2014 at 4:24

GoogleCodeExporter commented 9 years ago
Closing.

Original comment by casevh on 31 Jan 2014 at 6:53