On May 5, 6:35 am, Francois Bissey
wrote:
> > On May 4, 8:43 pm, Francois Bissey
>
> > wrote:
> > > > same problem if I try building a standalone ecl, and if I use gcc
> > > > 4.0.1, too.
> > > > So this looks like the combination of OSX 10.5 and PPC that is not
> > > > working here, nothing S
Le 04/05/2011 19:01, Joris Vankerschaver a écrit :
On May 3, 11:23 pm, Thierry Dumont wrote:
1) it takes time to do this,
2) we have to solve the callback problem: such program make a lot of
callbacks (to the rhs of the system): AFAIK, there are no simple method
to make this work fast enough
Hi Mike!
Thanks for your quick answer!
On Wed, May 04, 2011 at 10:47:53PM -0400, Mike C. Fletcher wrote:
> I've added a note to the RunSnakeRun homepage.
> I *think* you should be able to add an overriding command in your
> user-local bin directory and override the system runsnake execut
Hello,
I'm not sure if I should open a ticket on the following issue, or if
this is just a case of "Error Between Keyboard And Chair". Here is a
simplified version of what happened.
I had parents A and B and map phi between them, as follows:
sage: A = CombinatorialFreeModule(ZZ,[1,2,3],prefix='X
On Wed, May 4, 2011 at 12:51 AM, dagss wrote:
> I don't really have a say in this, but I've given this a lot of thought
> since I decided to drop Sage as my scientific Python distribution a year ago
> and have been searching for a new one ever since.
Just curious --- why did you drop it? Is it de
> On May 4, 8:43 pm, Francois Bissey
>
> wrote:
> > > same problem if I try building a standalone ecl, and if I use gcc
> > > 4.0.1, too.
> > > So this looks like the combination of OSX 10.5 and PPC that is not
> > > working here, nothing Sage-specific.
> > >
> > > Dima
> > >
> > > On May 4, 3
On 05/ 4/11 10:51 AM, Dima Pasechnik wrote:
-- Forwarded message --
From: Dima Pasechnik
Date: May 4, 5:07 pm
Subject: sage-4.7.rc1 released -- SAGE_CHECK=?
To: sage-release
Are we to test with SAGE_CHECK=yes ?
I have a test failure while building python spkg on a pretty usual
D
On 05/ 4/11 08:50 AM, Jeroen Demeyer wrote:
On 2011-05-03 21:44, Volker Braun wrote:
I agree that sage-4.7 should compile with gcc-4.6.[01]. But why not
specifically excluding these two instead of an wildcard?
What if gcc 4.6.2 exhibits the same bug? I think the *safer* option is
to assume th
On Wednesday, May 4, 2011 3:06:40 PM UTC-7, robertwb wrote:
>
> On Wed, May 4, 2011 at 3:05 PM, Robert Bradshaw
> wrote:
> > On Wed, May 4, 2011 at 2:16 PM, Jeroen Demeyer
> wrote:
> >> On 2011-05-04 23:06, Robert Bradshaw wrote:
> >>> Are you returning a non-python object in a cdef method wit
Does anybody know the current state-of-the-art in sage to compute with
finitely generated Z-modules (i.e., finitely generated abelian
groups)? The operations I would be looking for are
- sums, intersections and quotients of/by submodules
- homomorphisms between Z-modules
- computing kernel and i
On Wed, May 4, 2011 at 3:05 PM, Robert Bradshaw
wrote:
> On Wed, May 4, 2011 at 2:16 PM, Jeroen Demeyer wrote:
>> On 2011-05-04 23:06, Robert Bradshaw wrote:
>>> Are you returning a non-python object in a cdef method without an
>>> "except" signature?
>> This is not the issue.
>>
>> I think that
On Wed, May 4, 2011 at 2:16 PM, Jeroen Demeyer wrote:
> On 2011-05-04 23:06, Robert Bradshaw wrote:
>> Are you returning a non-python object in a cdef method without an
>> "except" signature?
> This is not the issue.
>
> I think that *somewhere* in Sage a KeyboardInterrupt exception is caught
> by
I finished compilerwrapper-1.1 which now allows you to transform the wrapper
as well as the wrapped gcc binary names by means of configure options. For
example,
./configure --with-gcc-transform-name='s/^/x86_64-/' --program-suffix='-4'
will call the compiler wrapper binaries gcc-4, c++-4, ... a
On 2011-05-03 21:44, Volker Braun wrote:
> I agree that sage-4.7 should compile with gcc-4.6.[01]. But why not
> specifically excluding these two instead of an wildcard?
I did this for cliquer because that gcc bug should be fixed, see #11227.
--
To post to this group, send an email to sage-devel@
On 2011-05-04 23:06, Robert Bradshaw wrote:
> Are you returning a non-python object in a cdef method without an
> "except" signature?
This is not the issue.
I think that *somewhere* in Sage a KeyboardInterrupt exception is caught
by an "except:" (i.e. except everything) and I want to know where.
Are you returning a non-python object in a cdef method without an
"except" signature? (In this case, it should be printing where the
exception was unable to be propagated.) Turning on profiling is
another way to get call stacks.
On Wed, May 4, 2011 at 11:53 AM, Jeroen Demeyer wrote:
> Hello all,
Hi Francois,
On Thu, 05 May 2011 00:33:57 +1200
Francois Bissey wrote:
> > > Well done so far. We need a repo. While we are putting this
> > > together I'd like it if you added the following to etc/make.conf:
> > > PORT_LOGDIR="${SBASE}"/var/log/portage
> > > PORTAGE_ELOG_CLASSES="warn error in
Hello all,
I would be *very happy* if somebody can tell me a way of debugging
exceptions in Python and Cython. I would like to know when exceptions
are raised and where they are caught during a Sage run.
In particular, there is an instance where I explicitly raise an
exception (in Cython code) bu
and this is a log from an older post (on Sage-4.7.alpha3) exhibiting
the same problem:
http://www.google.com/url?sa=D&q=http://boxen.math.washington.edu/home/dima/tmp/sage4.7.aplha3.MacOSX.PPC.install.log.gz
On May 4, 8:43 pm, Francois Bissey
wrote:
> > same problem if I try building a standalon
On May 3, 11:23 pm, Thierry Dumont wrote:
> 1) it takes time to do this,
> 2) we have to solve the callback problem: such program make a lot of
> callbacks (to the rhs of the system): AFAIK, there are no simple method
> to make this work fast enough (the ODE solver in Sage is extremely slow,
>
Dear runsnake developpers,
Thanks so much for runsnake! It's such a useful tool for optimizing
our code. Actually, I just wrote an interface to streamline and
promote it usage from within the Sagemath project:
http://www.sagemath.org/
http://trac.sagemath.org/sage_trac/tic
Hi,
#11287 adds two developper tools in sage.misc.dev_tools:
- An interface to the graphical profiler runsnake:
sage: runsnake("list(SymmetricGroup(3))")
See [1] for a screenshot.
- A function import_statements:
sage: import_statements(WeylGroup, lazy_attribute)
On May 4, 8:43 pm, Francois Bissey
wrote:
> > same problem if I try building a standalone ecl, and if I use gcc
> > 4.0.1, too.
> > So this looks like the combination of OSX 10.5 and PPC that is not
> > working here, nothing Sage-specific.
>
> > Dima
>
> > On May 4, 3:47 pm, Dima Pasechnik wro
On Wednesday, May 4, 2011 1:27:27 PM UTC+1, François wrote:
>
> Yes that's a big problem with the current tarball of Burcin.
> It doesn't fail for him or me because we already have the stuff in the
> system.
>
We could use strace to make sure that no process in the compilation accesses
headers
> same problem if I try building a standalone ecl, and if I use gcc
> 4.0.1, too.
> So this looks like the combination of OSX 10.5 and PPC that is not
> working here, nothing Sage-specific.
>
> Dima
>
> On May 4, 3:47 pm, Dima Pasechnik wrote:
> > On MacOSX 10.5.8 (PPC G4) I cannot proceed past
> On Tue, 3 May 2011 20:42:01 -0700 (PDT)
>
> François wrote:
> > On May 4, 5:23 am, Burcin Erocal wrote:
> > > > One last thing about "sage -clone, -b, -ba, br, ..." --- from my
> > > > memory about several discussions, the sage community regards this
> > > > as a "killer feature", i.e. that th
> FWIW, I do have a SAGE_PREFIX/local/include/gf2x.h. The failing compilation
>
> x86_64-pc-linux-gnu-g++ -I../include -I. -O2 -pipe -c -fPIC -o GF2X.lo
> GF2X.c
> GF2X.c:13:18: fatal error: gf2x.h: No such file or directory
>
> is executed in some faraway path, so it doesn't find the header un
-- Forwarded message --
From: Dima Pasechnik
Date: May 4, 5:07 pm
Subject: sage-4.7.rc1 released -- SAGE_CHECK=?
To: sage-release
Are we to test with SAGE_CHECK=yes ?
I have a test failure while building python spkg on a pretty usual
Debian x64 system (with make -j8, or just make
The *safest* option of them all is of course to never build with
optimizations. Its comparably easy to generate straightforward machine code,
the compiler bugs are invariably tied to the optimization process. Also, I
think that old bugs in the gcc bugzilla are not systematically tested
against
I seem to remember that it used to be possible to change status on Trac
tickets from "new" to "needs_work" but now that's not possible. Has
this changed or am I misremembering? In any case, I prefer the old
behaviour.
Jeroen.
--
To post to this group, send an email to sage-devel@googlegroups.c
Are we to test with SAGE_CHECK=yes ?
I have a test failure while building python spkg on a pretty usual
Debian x64 system (with make -j8, or just make) if I have it on.
namely, the failures are:
test_distutils
test test_distutils failed -- errors occurred; run in verbose mode for
details
(this is
FWIW, I do have a SAGE_PREFIX/local/include/gf2x.h. The failing compilation
x86_64-pc-linux-gnu-g++ -I../include -I. -O2 -pipe -c -fPIC -o GF2X.lo
GF2X.c
GF2X.c:13:18: fatal error: gf2x.h: No such file or directory
is executed in some faraway path, so it doesn't find the header unless it is
i
On Wednesday, May 4, 2011 10:51:10 AM UTC+2, Burcin Erocal wrote:
>
> Hi Dag,
>
> On Wed, 4 May 2011 00:51:56 -0700 (PDT)
> dagss wrote:
>
> > I don't really have a say in this, but I've given this a lot of
> > thought since I decided to drop Sage as my scientific Python
> > distribution a year ag
Hi Dag,
On Wed, 4 May 2011 00:51:56 -0700 (PDT)
dagss wrote:
> I don't really have a say in this, but I've given this a lot of
> thought since I decided to drop Sage as my scientific Python
> distribution a year ago and have been searching for a new one ever
> since.
>
> My problem with Gentoo
Hi!
On bsd.math, I found that some tests from sage.interfaces.maple fail.
Typically, it is
Expected:
"(2)*"(17)*"(53)*"(109)
Got:
``(2)*``(17)*``(53)*``(109)
Is that problem restricted to non-linux (note that it is just " versus
``, which might just depend on the operating system)? I can
same problem if I try building a standalone ecl, and if I use gcc
4.0.1, too.
So this looks like the combination of OSX 10.5 and PPC that is not
working here, nothing Sage-specific.
Dima
On May 4, 3:47 pm, Dima Pasechnik wrote:
> On MacOSX 10.5.8 (PPC G4) I cannot proceed past ecl.
> I get cras
On Tue, 3 May 2011 20:42:01 -0700 (PDT)
François wrote:
> On May 4, 5:23 am, Burcin Erocal wrote:
> >
> > > One last thing about "sage -clone, -b, -ba, br, ..." --- from my
> > > memory about several discussions, the sage community regards this
> > > as a "killer feature", i.e. that there is not
On Tue, 3 May 2011 20:07:39 -0700 (PDT)
François wrote:
> On May 4, 7:58 am, Maarten Derickx
> wrote:
> > On May 3, 7:23 pm, Burcin Erocal wrote:
> >
> > > IIRC, there were messages on this list about having python as a
> > > dependency already. What are the dependencies of Sage besides
> >
On MacOSX 10.5.8 (PPC G4) I cannot proceed past ecl.
I get crashes (sort or random) after bare.lsp is loaded,
ie after the log lines
;;; About to load cmp/load.lsp
;;;
;;; Now we are in shape to do something useful.
;;; End of bare.lsp
it can be:
Internal or unrecoverable error in:
not a lisp dat
I don't really have a say in this, but I've given this a lot of thought
since I decided to drop Sage as my scientific Python distribution a year ago
and have been searching for a new one ever since.
My problem with Gentoo in general is that it solves the problems that SPKGs
have by adding compl
On 2011-05-03 21:44, Volker Braun wrote:
> I agree that sage-4.7 should compile with gcc-4.6.[01]. But why not
> specifically excluding these two instead of an wildcard?
What if gcc 4.6.2 exhibits the same bug? I think the *safer* option is
to assume the status-quo that the bug will not be fixed.
41 matches
Mail list logo
