On Wednesday, July 1, 2020 at 4:39:12 PM UTC-7, John H Palmieri wrote:
>
>
>
> On Wednesday, July 1, 2020 at 2:22:49 PM UTC-7, Antonio Rojas wrote:
>>
>>
>>
>> El miércoles, 1 de julio de 2020, 21:06:43 (UTC+2), John H Palmieri
>> escribió:
>>>
>>>
>>> Why so many deprecation warnings? I think
On Wednesday, July 1, 2020 at 2:22:49 PM UTC-7, Antonio Rojas wrote:
>
>
>
> El miércoles, 1 de julio de 2020, 21:06:43 (UTC+2), John H Palmieri
> escribió:
>>
>>
>> Why so many deprecation warnings? I think they're coming from plain
>> Python; why doesn't Python print the warnings?
>>
>>
>>
>
El miércoles, 1 de julio de 2020, 21:06:43 (UTC+2), John H Palmieri
escribió:
>
>
> Why so many deprecation warnings? I think they're coming from plain
> Python; why doesn't Python print the warnings?
>
>
>
Because python ignores deprecation
warnings,
On Wed, Jul 01, 2020 at 10:39:18PM +0200, Vincent Delecroix wrote:
> Don't use ZZ as a base ring for your polynomial ring but Zmod(2**64).
>
> sage: R. = PolynomialRing(Zmod(2**64), 3)
> sage: x * 2**64
> 0
That doesn't actually work. The sum of 2 64 bit numbers is a 65
bit number. The
Don't use ZZ as a base ring for your polynomial ring but Zmod(2**64).
sage: R. = PolynomialRing(Zmod(2**64), 3)
sage: x * 2**64
0
Vincent
Le 01/07/2020 à 22:00, Kurt Roeckx a écrit :
Hi,
I'm working on a project that reads an assembler file and converts that to
sage to help verify that the
Hi,
I'm working on a project that reads an assembler file and converts that to
sage to help verify that the math the assembler is doing is correct. It's
to verify cryptographic implementations. Sage is only part of the
verification, other properties are checked using SMT.
What I did so far
This puzzles me: evaluating '\i' in Python 3 just gives '\i'. Same with
IPython. Evaluating it in Sage prints many warning messages: the following
is from a fresh Sage session, and I only evaluated '\i' once, despite the
appearance:
% sage
