Wrong treatment of "big" double literals about astor HOT 3 CLOSED

This looks more broken in astor 0.6:

>>> import astor
>>> import ast
>>> print (astor.to_source(ast.parse('a = 1e400')))
a = 1e1000

>>> print (astor.to_source(ast.parse('a = -1e400')))
a = -1e1000

@pmaupin do you know what causes this?

from astor.

@berkerpeksag :

Sorry I didn't document this fix better.

As described by the bug report, the behavior in 0.5 is broken -- inf can appear in the AST, but inf is not a reserved word in Python.

However, the suggested fix of using float('inf') will not round-trip properly; the call to float is embedded in the AST along with the string 'inf', so the generated AST does not match the original AST.

The only way I know of to create source code that will cause inf to be output in the AST is to use a number that is too big, so the current solution works and round-trips correctly, unless somebody has a python with more than 10 bits of exponent in a float. If anybody knows a more canonical way of doing this, that would be great, but the goal is to generate source code that will compile to having inf in the AST, not to generate a call to float along with a string.

BTW, thanks for all your great work on this!

from astor.

Ah, you're right. I definitely missed this:

I've added a test case and explicitly document this in the test so hopefully I won't forget again :)

Thanks!

from astor.