William Stein wrote:
> If we are going to change something in this case, probably Simon's
> suggestion to have a warning (that can be turned off) be printed by
> the top-level globalsI() is_prime when confronted with a field element
> seems best... It definitely won't break anybody's code, and avo
On Tue, Mar 27, 2018 at 11:21 AM, Marc Mezzarobba wrote:
> John Cremona wrote:
>> However pedantic you are it is very hard indeed to justify this for a
>> package which is intended for a wide class of users:
>>
>> sage: a = 300/100
>> sage: a
>> 3
>> sage: a in ZZ
>> True
>> sage: a.is_prime()
>>
John Cremona wrote:
> However pedantic you are it is very hard indeed to justify this for a
> package which is intended for a wide class of users:
>
> sage: a = 300/100
> sage: a
> 3
> sage: a in ZZ
> True
> sage: a.is_prime()
> False
Yes, but having a.is_prime() return True may break generic cod
