def phi(z):
return 2*sqrt(3+z)
def dif(a,b):
return (phi(a+I*b)-(a+I*b))
var('x y')
plot_vector_field((dif(x,y).real(),dif(x,y).imag()),(x,-3,3),
(y,-3,3)).show()
This returns an error because Maxima does not know: "Is y positive,
negative, or zero?"
I suspect that this is a bug, since plo
I currently have some Sage code in a file called main.sage. I call this from
the Sage command line interpreter with "load main.sage". After profiling my
code, I moved a few functions into a "cfuncs.spyx" which I call with a "load
cfuncs.spyx" command in main.sage. This works great, and cfuncs.spy
On Fri, Apr 25, 2008 at 6:56 AM, Stephen Hartke <[EMAIL PROTECTED]> wrote:
> I currently have some Sage code in a file called main.sage. I call this from
> the Sage command line interpreter with "load main.sage". After profiling my
> code, I moved a few functions into a "cfuncs.spyx" which I call
Gabriel Pannwitz wrote:
> def phi(z):
> return 2*sqrt(3+z)
> def dif(a,b):
> return (phi(a+I*b)-(a+I*b))
> var('x y')
> plot_vector_field((dif(x,y).real(),dif(x,y).imag()),(x,-3,3),
> (y,-3,3)).show()
>
> This returns an error because Maxima does not know: "Is y positive,
> negative, or zer
> Sound pretty much like it could be. Can you take vanilla python 2.5.2
> on your box, build from source and then check if the gdbm extension
> compiles [I think it won't]. Can you then build gdbm from source and
> use that version to build python? If that works it is likely to be a
> use flag pr
> Sound pretty much like it could be. Can you take vanilla python 2.5.2
> on your box, build from source and then check if the gdbm extension
> compiles [I think it won't]. Can you then build gdbm from source and
> use that version to build python? If that works it is likely to be a
> use flag pro
I attempted to upgrade my Sage software from 2.something to 3.0.
I renamed my old /Applications/sage folder, copied in the new one from
the dmg,
and did the usual launch of the sage icon using Terminal.
It said
--
| SAGE Version
On Fri, Apr 25, 2008 at 2:36 PM, Cotati <[EMAIL PROTECTED]> wrote:
>
> I attempted to upgrade my Sage software from 2.something to 3.0.
> I renamed my old /Applications/sage folder, copied in the new one from
> the dmg,
> and did the usual launch of the sage icon using Terminal.
> It said
>
The Sage binary was sage-3.0-osx10.5-Intel-i386-Darwin.dmg dated
April 22nd, 6:19pm which I downloaded this afternoon from the Sage
website downloads page for Mac binaries.
My machine is a Macbook (laptop) running OSX 10.4.11, Darwin kernel
version 8.11.1, having an Intel Core Duo processor.
I
On Apr 25, 3:31 pm, Cotati <[EMAIL PROTECTED]> wrote:
> The Sage binary was sage-3.0-osx10.5-Intel-i386-Darwin.dmg dated
> April 22nd, 6:19pm which I downloaded this afternoon from the Sage
> website downloads page for Mac binaries.
>
Correction: that should be 6:19am, not 6:19pm.
I would ha
On Apr 26, 12:31 am, Cotati <[EMAIL PROTECTED]> wrote:
> The Sage binary was sage-3.0-osx10.5-Intel-i386-Darwin.dmg dated
> April 22nd, 6:19pm which I downloaded this afternoon from the Sage
> website downloads page for Mac binaries.
> My machine is a Macbook (laptop) running OSX 10.4.11, Darwin
On Apr 26, 12:41 am, Cotati <[EMAIL PROTECTED]> wrote:
> On Apr 25, 3:31 pm, Cotati <[EMAIL PROTECTED]> wrote:
>
> > The Sage binary was sage-3.0-osx10.5-Intel-i386-Darwin.dmg dated
> > April 22nd, 6:19pm which I downloaded this afternoon from the Sage
> > website downloads page for Mac binari
On Fri, Apr 25, 2008 at 3:31 PM, Cotati <[EMAIL PROTECTED]> wrote:
>
> The Sage binary was sage-3.0-osx10.5-Intel-i386-Darwin.dmg dated
> April 22nd, 6:19pm which I downloaded this afternoon from the Sage
> website downloads page for Mac binaries.
> My machine is a Macbook (laptop) running O
On Apr 25, 10:21 pm, ugus <[EMAIL PROTECTED]> wrote:
> > Sound pretty much like it could be. Can you take vanilla python 2.5.2
> > on your box, build from source and then check if the gdbm extension
> > compiles [I think it won't]. Can you then build gdbm from source and
> > use that version to
Hi:
I'm wondering why is it that
rm -rf "$SAGE_ROOT/local/lib/$GAP/pkg/"
mkdir "$SAGE_ROOT/local/lib/$GAP/pkg/"
occurs in the spkg-install script for gap_packages*?
Is there a reason why the old packages are deleted?
- David Joyner
--~--~-~--~~~---~--~~
To post t
On Apr 26, 3:14 am, "David Joyner" <[EMAIL PROTECTED]> wrote:
> Hi:
>
> I'm wondering why is it that
> rm -rf "$SAGE_ROOT/local/lib/$GAP/pkg/"
> mkdir "$SAGE_ROOT/local/lib/$GAP/pkg/"
> occurs in the spkg-install script for gap_packages*?
> Is there a reason why the old packages are deleted?
Hi
On Wed, Apr 2, 2008 at 6:36 AM, William Stein <[EMAIL PROTECTED]> wrote:
[...]
> By the way, you can modify sys.path in Sage so that it's possible
> to use your existing system-wide Python modules in some cases...
[...]
I tried just that, since I want to use Graphviz
(http://www.graphviz.org/)
On Fri, Apr 25, 2008 at 7:20 PM, Hector Villafuerte <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 2, 2008 at 6:36 AM, William Stein <[EMAIL PROTECTED]> wrote:
> [...]
>
> > By the way, you can modify sys.path in Sage so that it's possible
> > to use your existing system-wide Python modules in some
Sage uses Python 2.5 while your system installation looks like 2.4.
--Mike
On Fri, Apr 25, 2008 at 6:25 PM, Hector Villafuerte <[EMAIL PROTECTED]> wrote:
>
> On Fri, Apr 25, 2008 at 7:20 PM, Hector Villafuerte <[EMAIL PROTECTED]>
> wrote:
> > On Wed, Apr 2, 2008 at 6:36 AM, William Stein <[EM
William --
Thanks muchly!
The new binary installs and runs just fine.
-- Kurt
On Apr 25, 4:51 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Fri, Apr 25, 2008 at 3:31 PM, Cotati <[EMAIL PROTECTED]> wrote:
>
> > The Sage binary was sage-3.0-osx10.5-Intel-i386-Darwin.dmg dated
> > Apri
Hello.
recently I've installed SAGE 3.0 on my computer (ubuntu 7.10).
everything works great when I'm working from the sage shell, or from
the notebook.
However it's very difficult to get real work done from the shell, so
I'm trying to use idle, according to the instructions given here:
http://g
On Fri, Apr 25, 2008 at 7:27 PM, Mike Hansen <[EMAIL PROTECTED]> wrote:
>
> Sage uses Python 2.5 while your system installation looks like 2.4.
>
> --Mike
Thanks Mike!
Upgrading to Python 2.5 did the trick.
Best,
--
Hector
--~--~-~--~~~---~--~~
To post to this
22 matches
Mail list logo