Le 20/10/2016 à 13:15, John Cremona a écrit :
That is surely a bug. I always assumed that the only trabformation
made when inputting a .sage file whe nit is converted to a .py file
was to apply the same preparsing as when you type into the command
line. But that is not the case: note that
pr
That is surely a bug. I always assumed that the only trabformation
made when inputting a .sage file whe nit is converted to a .py file
was to apply the same preparsing as when you type into the command
line. But that is not the case: note that
preparse('0 = 42')
returns
'__tmp__=var("0"); Int
> 0 = 42
> print 0
Hahaha, easiest way to get a contradiction and thereby prove any statement
in Sage :-D
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-dev
Consider the following code:
0 = 42
print 0
If you write it into sage's ipython, it of course gives you an error. More
precisely, you get
ValueError: The name "0" is not a valid Python identifier.
But suppose you write it into a file bug.sage, and execute it using sage
bug.sage, you get 42! T
