ivars = set(dvar.arguments()).intersection(extract_var_from_diff(de))
I forgot to make intersection in first patch. Changes are in the
second one.
It helps us to solve
sage: x,t=var('x
t')
sage:
f=function('f',x)
sage:
g=function('g',t,x)
sage: de=diff(f,x)+f+diff(g,t,x)
sage: desolve(de,f)
(c
if you can not access a website or in your school office and there is
a blocked website, you can access a blocked website by using this
website.
http://refinanceroxy.co.cc or http://nightway.info
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this
Spammer.
I've just banned him.
On Mon, Mar 29, 2010 at 7:22 AM, votre votre.vo...@gmail.com wrote:
if you can not access a website or in your school office and there is
a blocked website, you can access a blocked website by using this
website.
http://refinanceroxy.co.cc or
It is noted on the discussion Sage 4.3.3 Fails To Build On 64 bit Linux
System (gcc.4.4.2) on sage-support that Sage fails to build on SELinux unless
the stack protection is disabled. I asked on comp.lang.c for help in writing a
program which would detect if stack protection is enabled or not.
Hi,
The following is from Markus, director of the GeoGebra project:
GeoGebra is now a mentoring organization for Google Summer of Code
2010 (see http://www.geogebra.org/trac/wiki/Gsoc2010). This means that
Google pays students $5500 for a 2 month coding project. If we can
find a student who
I'm in the process of developing some SAGE packages, so I've made my
own private copy of the whole SAGE tree, and have added/modified some
files in that. I'd like to upgrade to a new SAGE version. What's the
proper procedure for doing this? That is how do I get my changes
installed into it. I
Python is not a sledgehammer; it is an elegant tool, which can be used
to produces beautiful readable maintainable and portable code.
Anyway, it's your decision.
I'm for allowing the use of Python in the Sage build system.
-- William
Under $SAGRE_ROOT/local/bin/, several of the Sage
On Mar 29, 8:01 pm, Georg S. Weber georgswe...@googlemail.com
wrote:
Python is not a sledgehammer; it is an elegant tool, which can be used
to produces beautiful readable maintainable and portable code.
Anyway, it's your decision.
I'm for allowing the use of Python in the Sage build
On Mon, Mar 29, 2010 at 11:04 AM, Dr. David Kirkby
david.kir...@onetel.net wrote:
When I try the same program on sage.math, it dumps core there too. So I
don't know if sage.math has protection of the stack enabled. If it does,
then it is strange that SELinux has problems, whereas sage.math does
Gonzalo Tornaria wrote:
On Mon, Mar 29, 2010 at 11:04 AM, Dr. David Kirkby
david.kir...@onetel.net wrote:
When I try the same program on sage.math, it dumps core there too. So I
don't know if sage.math has protection of the stack enabled. If it does,
then it is strange that SELinux has
On Mar 28, 9:10 pm, William Stein wst...@gmail.com wrote:
I'm for allowing the use of Python in the Sage build system.
It seems to me that with a little care one could have python used in
some parts of the build system and avoid declaring python a
prerequisite for python.
If a package requires
Hi Victor,
Here's what I would do. If there's a better way maybe this will
prompt somebody to pony it up. This assumes all your changes are
under SAGE_ROOT/devel/sage.
Lots more details are in http://www.sagemath.org/doc/developer/walk_through.html
This is an expanded version of the Upgrading
On Mon, Mar 29, 2010 at 5:41 PM, Dr. David Kirkby
david.kir...@onetel.net wrote:
I'm just puzzled why SELinux is indicating problems with code trying to
execute the stack, whereas there are no such complaints on sage.math,
despite the fact attempting to execute the stacks dumps core on
Nils Bruin wrote:
On Mar 28, 9:10 pm, William Stein wst...@gmail.com wrote:
I'm for allowing the use of Python in the Sage build system.
It seems to me that with a little care one could have python used in
some parts of the build system and avoid declaring python a
prerequisite for python.
On Mon, Mar 29, 2010 at 4:05 PM, Dr. David Kirkby
david.kir...@onetel.net wrote:
Nils Bruin wrote:
On Mar 28, 9:10 pm, William Stein wst...@gmail.com wrote:
I'm for allowing the use of Python in the Sage build system.
It seems to me that with a little care one could have python used in
On Sun, Mar 28, 2010 at 3:13 AM, William Stein wst...@gmail.com wrote:
We should definitely move to PARI 2.4. We haven't only because it is
indeed a monumental task. Perhaps I'll do the move, since I wrote
most of the Sage wrapper of PARI anyways, and surely porting is much
less work than
Gonzalo Tornaria wrote:
On Mon, Mar 29, 2010 at 5:41 PM, Dr. David Kirkby
david.kir...@onetel.net wrote:
I'm just puzzled why SELinux is indicating problems with code trying to
execute the stack, whereas there are no such complaints on sage.math,
despite the fact attempting to execute the
On 03/29/2010 01:34 PM, VictorMiller wrote:
I'm in the process of developing some SAGE packages, so I've made my
own private copy of the whole SAGE tree, and have added/modified some
files in that. I'd like to upgrade to a new SAGE version. What's the
proper procedure for doing this? That is
On Mon, Mar 29, 2010 at 8:16 PM, Dr. David Kirkby
david.kir...@onetel.net wrote:
I don't know how practical it is going to be for a Sage developer to change
the the source code of PARI, NTL and whatever else has this problem, to add
mprotect() where needed. I suspect that might be a bit
19 matches
Mail list logo
