Hi, I suspected it would have something to do with the interpreter.
Thanks for the explanation!
On Mon, May 20, 2013 at 12:02:43PM +, Simon King wrote:
> Hi!
>
> On 2013-05-20, man...@gmx.net wrote:
> > import bar
> > type( bar.foo( ) )
> >
> > returns
> >
> >
> >
> > Needless to say, this c
On Mon, May 20, 2013 at 07:38:10PM +0800, P Purkayastha wrote:
> On 05/20/2013 07:08 PM, man...@gmx.net wrote:
> > A function
> >
> > def foo( ):
> > return 0
> >
> > evaluates type( foo( ) ) to
> >
> >
> >
> > But then I put this function into bar.py like so
> >
> > bar.py:
> > from sage.all
A function
def foo( ):
return 0
evaluates type( foo( ) ) to
But then I put this function into bar.py like so
bar.py:
from sage.all import *
def foo( ):
return 0
and
import bar
type( bar.foo( ) )
returns
Needless to say, this causes a bunch of new errors if my code assume
ude
functions returning floats while yet others cause errors when called
with floats instead of Reals, etc...
On Mon, May 13, 2013 at 05:22:07PM -0700, rjf wrote:
> On Monday, May 13, 2013 2:11:59 PM UTC-7, ManDay wrote:
>
> Could anyone shed a bit of light on this?
>
>
Could anyone have a look at this? Needless to say, this is *extremely*
annoying. Every few minutes the notebook gets completely messed up with
this bug.
I can forgo the Backspace Key, but I need to press Enter, and that just
breaks in the middle of a block then and I'm left with a complete d
u
56:28PM -0700, John H Palmieri wrote:
>On Monday, May 13, 2013 2:11:59 PM UTC-7, ManDay wrote:
>
> Could anyone shed a bit of light on this?
>
> The more I try, the more SAGE's types get in my way. It turns out to be
> an unpredictable element. Unless I make
Could anyone shed a bit of light on this?
The more I try, the more SAGE's types get in my way. It turns out to be
an unpredictable element. Unless I make sure *every* involved function
really returns one specific type, calculations are becoming practically
impossible, because the results are compl
I think there is a conceptual problem with function returning s.
Consider the following:
def find_roots( func,l,r ):
tol = 1e-10
try:
result = find_root( func,l,r ) )
except RuntimeError:
return []
return find_roots( func,l,result-tol )+[ result ]+find_roots(
func
Please have a look at this, is there any reasonable explanation for the
output of the few last cells?
http://alpha.sagenb.org/home/pub/700/
This happens reproducibly. plot( ) evaluates to nothing (no output, etc)
and afterwards, the workspace seems to be emptied of everything that was
defined.
-
I repeatedly run into problems where Sage claims it's not able to
evaluate a function. Often, this happens due to a
ValueError: negative number cannot be raised to a fractional power
which bubbles up from somewhere deep in the call stack. Here is one of
those cases
summand = summand*( m*( y_i-(
On Fri, May 10, 2013 at 05:56:03AM -0700, William Stein wrote:
> On Fri, May 10, 2013 at 4:04 AM, wrote:
> > It might be related. I'm confident this happend while the cursor was at
> > the end of a line, though.
> >
> > Also, I don't think this could explain the Enter-breaks-cell part, could
> >
It might be related. I'm confident this happend while the cursor was at
the end of a line, though.
Also, I don't think this could explain the Enter-breaks-cell part, could
it?
If what you say is true and a non-empty (!) cell is joined with the
preceeding one when Backspace is pressed on the first
On Fri, May 10, 2013 at 11:10:58AM +0200, man...@gmx.net wrote:
> Backspace in the Notebook in webkit(gtk) often (not always, haven't
> found a pattern) joins the cell with the previous cell. As you might
> imagine, that's fairly annoying. Could anyone have a look? Thanks.
Similarly, often causes
Backspace in the Notebook in webkit(gtk) often (not always, haven't
found a pattern) joins the cell with the previous cell. As you might
imagine, that's fairly annoying. Could anyone have a look? Thanks.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" gr
implement it, I don't know,
On Sunday, April 21, 2013 2:03:31 PM UTC+2, adsmith wrote:
>
> On Saturday, April 20, 2013 2:03:07 PM UTC-4, ManDay wrote:
>
>> I'd like to be able to derive in the following manner:
>>
>> x = var( "x" );
>> J = functi
Typo: All the "g"s are supposed to be J's, sorry.
--
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-devel+unsubscr...@googlegroups.com.
To post to this group, s
I'd like to be able to derive in the following manner:
x = var( "x" );
J = function( "g",x );
f = function( "f",g );
# like so
x1 = var( "x1" );
f.diff( J( x1 ) );
which is the functional f derivate with respect to the value of J at x1. Is
this possible in a fashion at least similar to what I
ZIP file.
On Jun 13, 6:10 pm, Paulo César Pereira de Andrade
wrote:
> 2010/6/13 ManDay :
>
> > I too haven't got JMol to work in the NB, although it works fine as
> > the standalone application when run from the commandline. I don't see
> > how the site you mention
I too haven't got JMol to work in the NB, although it works fine as
the standalone application when run from the commandline. I don't see
how the site you mentioned would help. Installing JAVA was no problem
and it works just fine, including JMol applets on the jmol.sourceforge
site. This is most l
19 matches
Mail list logo
