conversion error

[jasongrout]

Using Sage 3.4.alpha0:

{{{sage: RDF(e^(1j))
ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (1419, 0))

ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (1535, 0))

ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (1419, 0))

ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (1419, 0))

(then a TypeError is thrown since I don't have an RDF value)

}}}

Now, of course, the above gives a TypeError, but there still shouldn't be the scary preparser error.

CC: @sagetrac-mvngu

Component: misc

Issue created by migration from https://trac.sagemath.org/ticket/5400

[jasongrout]

comment:1

Trying this again:

sage: RDF(e^(1j))
ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (1419, 0))

ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (1535, 0))

ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (1419, 0))

ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (1419, 0))

[jasongrout]

comment:3

Robert, I "assigned" you the bug because I don't know an easy way to CC you on the bug report, since you are likely the best person to look at this currently.

[sagetrac-mabshoff]

comment:4

Replying to @jasongrout:

Robert, I "assigned" you the bug because I don't know an easy way to CC you on the bug report, since you are likely the best person to look at this currently.

I assume you know about the CC field, so what is the problem?

Many account holders in trac are listed at http://trac.sagemath.org/sage_trac/wiki

Cheers,

Michael

[jasongrout]

comment:5

The only CC option I have now with the new trac is to add myself. It's not a text box anymore.

[sagetrac-mabshoff]

comment:6

Replying to @jasongrout:

The only CC option I have now with the new trac is to add myself. It's not a text box anymore.

Ok, this is a permission issue with the new trac since I can CC anybody :)

This is now #5401.

Cheers,

Michael

[robertwb]

comment:7

Hmm... this doesn't happen in 3.3.

What does sage: preparse('RDF(e^(1j))') give you?

[robertwb]

comment:8

This is not a preparsing bug.

sage: a = sage: a = e^1j; a
 e^(1.0*I)
sage: RDF(a)
ERROR: An unexpected error occurred while tokenizing input
The following traceback may be corrupted or invalid
The error message is: ('EOF in multi-line statement', (1088, 0))
...

[jasongrout]

comment:9

Good point with your test. The tokenizing statement made me think it was the preparser.