2009/12/16 Craig Citro :
>> Hi John -- the offending character is the mu for microseconds. There are
>> probably classier fixes, but I edit the ipython source file in my sage
>> install. It's one of the ones in the traceback -- I'm on my phone and can't
>> look right now.
>>
>
> Line 1778 of $SAGE_
> OK, so there's a python (or ipython) source code file which causes
> problems when running ipython on some machines. Should that be
> reported as a bug to the python people?
>
This could probably go upstream to IPython -- I've been meaning to do
it once I sit down and figure out whether it's ju
Thanks for the diagnosis! I tried the same thing on another machine
and it worked fine.
OK, so there's a python (or ipython) source code file which causes
problems when running ipython on some machines. Should that be
reported as a bug to the python people?
John
2009/12/16 Craig Citro :
>> Hi
> Hi John -- the offending character is the mu for microseconds. There are
> probably classier fixes, but I edit the ipython source file in my sage
> install. It's one of the ones in the traceback -- I'm on my phone and can't
> look right now.
>
Line 1778 of $SAGE_ROOT/local/lib/python2.6/site-pac
Hi John -- the offending character is the mu for microseconds. There are
probably classier fixes, but I edit the ipython source file in my sage
install. It's one of the ones in the traceback -- I'm on my phone and can't
look right now.
-cc
On Dec 16, 2009 10:36 AM, "John Cremona" wrote:
I have
I have defined a function in external .sage file which I load. Then I
test it using %timeit. But an error is raised:
UnicodeEncodeErrorTraceback (most recent call last)
/home/jec/.sage/temp/selmer/11222/_home_jec_agm_sage_3.py in ()
/home/jec/sage-4.3.rc0/local/lib/pyth
