[sage-devel] feature?: syntax so x=var("x") unnecessary for every variable

2008-07-15 Thread Mats
: Since Sage is already preparsing code, it could do this: expr = w./x. + y./z. print expr(z=5) #substitution I'm not necessarily suggesting using "." as the special symbol... just something easy to hit and that doesn't conflict with reserved python synta

[sage-devel] bug: double escaping of quotes

2008-07-15 Thread Mats
bug report: Using notebook mode. Problem: cell input: '\'' output: '\\u0027' expected output: '\u0027' Sincerely, Mats --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe fr

[sage-devel] Re: bug? from __future__ import division

2008-07-06 Thread Mats
Excuse me please, but is there any sort of workaround yet to this? It is preventing me from running python code that expects 2/3=0.... in notebook mode... Thank you, Mats On Jun 17, 12:59 pm, Mats <[EMAIL PROTECTED]> wrote: > It seems that "from __future__ import division&quo

[sage-devel] Re: Possible bug with sys.path interaction?

2008-06-17 Thread Mats
hat this issue somehow be made more visible to the user, who may be confused at to why sage isn't respecting the python environment variables or using the defauly python distribution. Perhaps some way to tell sage's python to use installed packages if they're compatible? Best wishes,

[sage-devel] Re: bug? from __future__ import division

2008-06-17 Thread Mats
It seems that "from __future__ import division" works in console mode, but does not work in notebook mode. Running the commands quoted below will yield the expected results in the console mode (....), but 2/3 will equal 0 in notebook mode. Sincerely, Mats On Jun 15, 1:36 pm, &quo

[sage-devel] bug? from __future__ import division

2008-06-15 Thread Mats
Hello, I've done Integer=int, but however it seems that after I do "from __future__ import division", I still get 2/3=1. This does not occur in the python interpreter; I get .66... as I should. Sincerely, Mats --~--~-~--~~~---~--~~ To pos

[sage-devel] Re: Possible bug with sys.path interaction?

2008-06-09 Thread Mats
I tried to do "sudo easy_install feedparser", which worked. I can "import feedparser" from the python shell, but not from sage unless I explicitly add it to my path. I also did exactly as you did and compared the paths; as per request: sage: import sys sage: sys.path [

[sage-devel] Possible bug with sys.path interaction?

2008-06-08 Thread Mats
his is a bug. I closed and reopened sage. Best wishes, Mats --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at h

[sage-devel] bug: jsmath doesn't like modeshift

2008-06-03 Thread Mats
o hit modeshift- k to select an autocompletion. --Mats --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/

[sage-devel] Re: notebook('', secure=true) not working

2008-06-03 Thread Mats
Apparently this bug is well-known; I got the fix from some kind folks at http://groups.google.com/group/sage-support/browse_thread/thread/a2adf91fd234a548 , for anyone else who is interested. Best wishes, Mats On Jun 3, 8:24 am, Mats <[EMAIL PROTECTED]> wrote: > Hello, > > Fyi

[sage-devel] notebook('', secure=true) not working

2008-06-03 Thread Mats
uot; be given higher visibility, for example in the readme, perhaps as its own script, and as a third line when running ./sage in text mode. Thank you, Mats INPUT: sage: notebook(address='', secure=True) RESULT: The notebook files are stored in: /home/mats/.sage//sage_notebook In order to us