0

Is the `hex(31)` conversion deprecated or not?

asked 2020-06-14 00:43:41 +0200

dsejas
2819 ●14 ●49 ●95

Hello, Sage Community!

A few months ago, when compiling Sage code to convert the decimal 31 to hexadecimal notation, I got a deprecation warning message telling me not to use hex(31), but 31.hex(). That was with SageMath 8.x (possibly 8.8 or 8.9; I don't remember exactly).

However, right now (version 9.1), when I run the command hex(31), it returns ``0x1f (the decimal representation of decimal 31), without any deprecation warning.

As the title says: Is the hex(31) conversion deprecated or not?

Other problem: hex(31) return 0x1f, while 31.hex() returns 1f

Thanks in advance for your answers!

Related:https://ask.sagemath.org/question/519...

edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted

1

answered 2020-06-14 22:05:28 +0200

tmonteil
27323 ●31 ●202 ●514 http://wiki.sagemath.o...

It is a known issue, but no consensus was found about fixing it, see https://groups.google.com/forum/#!msg...

edit flag offensive delete link

Comments

Hello, @tmonteil! Following that discussion, if I define

def hello():
    print(012)

I do get a deprecation warning about using 0o12 instead. However, if I define

def hello():
    print(hex(31))

I don't get any warning, nor if I do

def hello():
    print(31.hex())

However, I get an inconsistent output: the former gives 0x1f, while the latter gives just 1f.

dsejas ( 2020-06-22 18:17:26 +0200 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Question Tools

1 follower

Stats

Asked: 2020-06-14 00:43:41 +0200

Seen: 1,104 times

Last updated: Jun 14 '20

Related questions

Copyright Sage, 2010. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.

Powered by Askbot version 0.7.59