> Hi,
> I am using Pardus 2011 and trying to build sage on it with gcc 4.5.3.
> It aborts installation due to 12 errors while installing =20
> gnutls-2.2.1.p5. Some part of the log is in Turkish, all they say is
> something like "exiting from directory " And yamak is the
> user's name.
>
> I hope
Hi all,
this is not just Lion that is causing trouble. I opened #11619 about
problem with building some python bits under a linux-3.0 kernel. Some bits
of the building system looks at the major version number of linux to
determine that it needs to build stuff in plat-linux2. On linux-3.0 it look
On Fri, 29 Jul 2011 13:44:01 kcrisman wrote:
> On Jul 29, 4:20 pm, Volker Braun wrote:
> > On Friday, July 29, 2011 9:16:10 PM UTC+1, kcrisman wrote:
> > > More seriously, it would be helpful to know "how official" such non-
> > > releases are.
> >
> > Not at all official.
>
> Right, but it woul
On Mon, 01 Aug 2011 02:35:46 Simon King wrote:
> > It is a
> > bit of pity. sage-on-gentoo generates a bit of traffic on the
> > gentoo-science mailing list and the occasional thread here.
>
> sage-on-gentoo? Is that yet another list I haven't been aware of?
Just for clarification I work on portin
On Fri, 05 Aug 2011 05:49:41 kcrisman wrote:
> Thanks for the detailed analysis, Francois! The 'official'
> announcement hadn't been made on their list or the main Maxima page
> yet, just that it had been tagged, so I didn't mention it yet - but
> they have everything up on their download site, gr
On Sat, 20 Aug 2011 06:48:02 Dima Pasechnik wrote:
> A couple of days ago we had a hard to explain crash of sagenb (flask)
> webapp when it was hammered by 70 undergrads simultaneously during our lab.
> We don't rule out that it could be a twisted bug. Twisted has meanwhile
> advanced to version 1
On Fri, 12 Aug 2011 06:05:22 Volker Braun wrote:
> Looks like intel uses a completely different naming scheme instead
> of liblapack.so / libcblas.so / libf77blas.so. Francois' suggestion of
> renaming the intel MKL libraries to something standard is a good one, though
> it might not work. Since in
> On Oct 30, 10:12 am, Francois Bissey
>
> wrote:
> > There is also the fact that a number of packages check:
> > sys.platform == 'linux2'
>
> One quick data point: on FC 15 they are shipping linux 3.* kernels
> with a fake 2.* version number exactly fo
> On 30 Okt., 21:13, Nils Bruin wrote:
> > On Oct 30, 10:12 am, Francois Bissey
> >
> > wrote:
> > > There is also the fact that a number of packages check:
> > > sys.platform == 'linux2'
> >
> > One quick data point: on FC 15 th
Hi all,
After the merging of #10903 and #11339 I cannot see
any doctest crashing anymore because of singular.
There are only about a handfull of files in which we have failling doctests
from python-2.7.
Here they are:
sage -t -long -force_lib "devel/sage-
main/sage/rings/padics/padic_capped_rel
> On Nov 5, 2011, at 18:02 , Burcin Erocal wrote:
> > On Sat, 5 Nov 2011 17:23:38 -0700 (PDT)
> >
> > leif wrote:
> >> On 5 Nov., 21:24, "Justin C. Walker" wrote:
> >>> On Nov 5, 2011, at 12:16 , Julien Puydt wrote:
> Le 05/11/2011 17:42, William Stein a écrit :
> > What do you base thi
> Em 8 de novembro de 2011 04:20, Paulo César Pereira de Andrade
>
> escreveu:
> > 2011/11/7 Francois Bissey :
> >> Hi Paulo,
> >>
> >> You are using python-2.7 right? In #9958 I have a list of patches
> >> as long as my arm to deal wi
> On 11/08/11 13:37, William Stein wrote:
> > On Tue, Nov 8, 2011 at 8:04 AM, Michael Orlitzky
wrote:
> >> (I use Sage on Gentoo)
> >>
> >> For maintainers, the argument is that a package manager should handle
> >> dependencies for you. It's easier to write the dependencies down in a
> >> text f
> On 11/08/11 15:41, Francois Bissey wrote:
> > And by the way thanks for using sage-on-gentoo, we get tired but a pat
> > on the back helps a lot.
>
> Sure! You guys do a great job. I use Sage on three Gentoo machines and
> you've saved me countless hours ove
> 2011/11/8 Francois Bissey :
>
> [...]
>
> > I don't get any of that. I suspect there may be an issue with gmp/mpir.
> > But I have really no clue about the glibc problem, you are using
> > mpmath-0.17 I expect.
>
> Yes, mpmath-0.17.
>
>
> Em 9 de novembro de 2011 00:29, Paulo César Pereira de Andrade
>
> escreveu:
> > 2011/11/8 Francois Bissey :
> >>> 2011/11/8 Francois Bissey :
> >>>
> >>> [...]
> >>>
> >>> > I don't get any of that. I suspe
> 2011/11/9 Francois Bissey :
>
> Maybe setting MPMATH_NOGMPY is not enough to prevent it to
> call to gmpy "init" function that calls mp_set_memory_functions.
>
> I will try to debug a bit further, in the worst case, I can resubmit a
> sagemath package with
> rsync://distrib-coffee.ipsl.jussieu.fr/pub/linux/MandrivaLinux/devel/co
> oker/x86_64/media/contrib/release/python-gmpy-1.14-1mdv2011.0.x86_64.rpm
> instalando python-gmpy-1.14-1mdv2011.0.x86_64.rpm a partir de
> /var/cache/urpmi/rpms
> Preparando...
Interesting mix of French and Brazilian
> On Wed, Nov 9, 2011 at 11:00 PM, Dan Drake wrote:
> > On Wed, 09 Nov 2011 at 09:16PM -0500, Daniel Thau wrote:
> > > Yeah, I considered that possibility. The md5sum for both the
> >
> > pre-compiled
> >
> > > version I tried and the source both matched what they were expected
> > > too.
> > >
> I also use sage-on-gentoo. I find it a very good way to just use sage.
>
> But i don't only use sage, i also develop it: when there is a feature
> i miss, i implement it (if i have the knowledge and time to do so).
> The easyest way to do so is to have sage installed in a directory in
> the "sta
> On Fri, Nov 11, 2011 at 12:59 PM, frosty wrote:
> > I have just discovered Sage & want to know if there are any folks here
> > working on making a Debian version that would work without having to
> > compile all the parts. i.e. use the needed files, apps & libraries
> > that are already packaged
> Hello,
>
> I got an error while compiling sage-4.7.2 on my computer (Intel core 2
> Duo T8100) at the very begining. I should mention that on the same
> computer sage-4.7.1 compiles. Does anybody encounter such a problem or
> have a solution ?
>
> $ uname -a
> Linux jahe 2.6.32-5-amd64 #1 SMP F
Hi,
I spotted those two files and I am wondering what they are
used for.
sage-sage.py looks like a rewrite of sage-sage in python, is it ever called
from anywhere or is it a work in progress of some kind?
sage-sagex is it just a comand to execute a sage script? If so can't you
do that by calling
> On Saturday, November 12, 2011 5:21:07 PM UTC-8, François wrote:
> > Hi,
> >
> > I spotted those two files and I am wondering what they are
> > used for.
> > sage-sage.py looks like a rewrite of sage-sage in python, is it ever
> > called
> > from anywhere or is it a work in progress of some kind
> The only real advantages of keeping the upstream sources packaged is
> that (1) you can know what's in them, check md5sums, etc., and (2)
> there's less chance of introducing hard-to-find errors by fat-
> fingering a particular unpacked source file. But I'm happy to unpack,
> too.
>
Hi,
In my
Hi,
I have been looking at upgrading numpy again in #11334
Everything seem to build fine but the doctest failures reveal some
possibly deep problems.
In several tests a numpy array is prepared with numpy.linspace (there
are at least two in functions/other.py). Then a function is appled to
the nu
> I would like to propose that we *disallow* upgrading from any 4.x
> version of Sage to any 5.x version.
>
> This means that we can merge various upgrade-breaking patches in
> sage-5.0 (I foresee this to be the release after sage-4.8). Of course,
> we have to make an effort to make upgrades from
Hi all,
Over here in ticket #9958 we are almost done with
the big move to python 2.7.2.
However we have some issues that we don't know
how to resolve with 2 doctests from sage/combinat.
Some of the results appear to vary usually between
different 32bit systems but sometimes also between
64bit sy
On Mon, 02 Jan 2012 20:08:52 cch wrote:
> Make Sage with matplotlib by
> export SAGE_MATPLOTLIB_GUI='yes'
>
> and it stops with the error:
> ...
> Tkinter (IndexError: list index out of range)
> ...
>
> where tcltk-8.5.11 used in 64bit Slackware Linux.
>
> To solve this problem, I remove TCLTK a
On Sat, 25 Feb 2012 21:02:46 Jan Groenewald wrote:
> Hi
>
> I am looking for a Debian or Ubuntu packaging mentor.
>
> I am not an experienced debian packager, I am learning everything from
> scratch.
> But I am an experienced system administrator.
>
> I am hoping to find a mentor familiar with b
On Fri, 02 Mar 2012 11:17:55 William Stein wrote:
> Hi,
>
> I thought that if I rendered a 3d scene using viewer='tachyon', then
> it would use the multiple cores of my computer to render the scene
> more quickly. However, I was just rendering a complicated 3d scene
> for my class (that takes abo
On Fri, 02 Mar 2012 12:43:46 William Stein wrote:
> On Fri, Mar 2, 2012 at 12:42 PM, Francois Bissey
>
> wrote:
> > On Fri, 02 Mar 2012 11:17:55 William Stein wrote:
> >> Hi,
> >>
> >> I thought that if I rendered a 3d scene using viewer='tachyon
On Fri, 09 Mar 2012 17:12:30 Keshav Kini wrote:
> Jeroen Demeyer writes:
> > On 2012-03-09 06:18, Keshav Kini wrote:
> >> Something else: Why do we even have local/ ? Why not just have bin/,
> >> lib/, etc. in the root directory?
> >
> > I like local/. It makes the top-level directory a lot clea
On Sat, 10 Mar 2012 08:23:58 William Stein wrote:
> On Sat, Mar 10, 2012 at 8:16 AM, Keshav Kini wrote:
> > William Stein writes:
> >> Hi,
> >>
> >> Have you ever wondered how difficult it might be to switch Sage from
> >> Python 2.7 to Python 3.x? Some students in my course made a webpage
> >>
On Tue, 13 Mar 2012 22:44:03 P Purkayastha wrote:
On Wednesday, March 14, 2012 4:54:32 AM UTC+8, François wrote:
On Tue, 13 Mar 2012 01:18:41 P Purkayastha wrote:
> On Tuesday, March 13, 2012 3:41:35 PM UTC+8, Jeroen Demeyer wrote:
> > If you do this, you certainly should not restrict yourself t
On Tue, 20 Mar 2012 23:07:33 John H Palmieri wrote:
> Does anyone use the files in the directory SAGE_ROOT/ipython? Would you
> object if they were moved elsewhere in the Sage distribution, and if some
> of the files were modified or deleted? (In particular, ipythonrc-scipy
> might not be long for
On Fri, 13 Apr 2012 13:24:21 oNNy wrote:
> Hello, I tried to compile Sage Mathematics 4.8 using the ArchLinux AUR
> buildscript from here: https://aur.archlinux.org/packages.php?ID=56737
>
> The error occurs while installing the package linbox, see the log in the
> attachment. I hope this is fixab
-Original Message-
From: sage-devel@googlegroups.com on behalf of Jason Grout
Sent: Wed 12/8/2010 2:19 AM
To: sage-devel@googlegroups.com
Subject: [sage-devel] Re: Goto Blas.
On 12/7/10 12:05 AM, Thierry Dumont wrote:
> The Goto Blas are now under BSD license.
>
> http://www.tacc.utexas.e
Seems like I didn't dig deep enough.
So it isn't actively developed by the TACC
anymore, it is given to the community to
maintain and take over development.
It only provides f77blas. I guess it would
be possible to create a cblas interface using
f2c but it is not really something anyone would
wan
-Original Message-
From: sage-devel@googlegroups.com on behalf of Bill Hart
Sent: Fri 12/10/2010 2:21 PM
To: sage-devel
Subject: [sage-devel] Re: Goto Blas.
So I don't know what is considered a fast time to build BLAS, but on
my machine it was straightforward. I just typed make and it det
-Original Message-
From: sage-devel@googlegroups.com on behalf of Volker Braun
Sent: Fri 12/17/2010 1:11 AM
To: sage-devel@googlegroups.com
Subject: [sage-devel] Re: Should Sage include its own gcc ? It would add <= 1.6
MB to the Sage tarball.
Gentoo-prefix uses rpath instead of the LD_L
-Original Message-
From: sage-devel@googlegroups.com on behalf of Georg S. Weber
Sent: Fri 12/17/2010 11:30 AM
To: sage-devel
Subject: [sage-devel] Re: Should Sage include its own gcc ? It would add <= 1.6
MB to the Sage tarball.
P.S.:
Francois, I thought you were "on leave" moving to a
-Original Message-
From: sage-devel@googlegroups.com on behalf of Volker Braun
Sent: Sun 12/19/2010 01:44
To: sage-devel@googlegroups.com
Subject: [sage-devel] Combine ATLAS and LAPACK?
The newest development version atlas-3.9.32 now wants to build lapack itself
and the old --with-netlib
> Hi,
>
> I'm the guy who reported and worked on :
> http://trac.sagemath.org/sage_trac/ticket/10285
>
> For reference, the problem was that I couldn't get sage 4.6.0 to build
> on my ARM-based netbook. I fought hard (and well!), and finally got sage
> up -- that required a few changes here and t
> Le 05/02/2011 11:44, Francois Bissey a écrit :
> > So gamma could be called from C, Cython, possibly mpmath, pynac or
> > maxima. I guess you could tests the results calling from mpmath or
> > maxima. I am guessing that SR(10.0r).gamma() will end up being a call to
> &
> Le 05/02/2011 20:08, Francois Bissey a écrit :
> > > Le 05/02/2011 11:44, Francois Bissey a écrit :
> > > > So gamma could be called from C, Cython, possibly mpmath, pynac or
> > > > maxima. I guess you could tests the results calling from mpmath or
&g
Once should be enough. Found it because I am running maxima-5.23.2
on my iMac, this is with 4.6.2.alpha4:
age -t -force_lib "devel/sage-main/sage/interfaces/maxima.py"
**
File "/Users/frb15/Desktop/Gentoo/usr/share/sage/devel/sage-
> Once should be enough. Found it because I am running maxima-5.23.2
> on my iMac, this is with 4.6.2.alpha4:
> age -t -force_lib "devel/sage-main/sage/interfaces/maxima.py"
> **
> File "/Users/frb15/Desktop/Gentoo/usr/share/sage/d
> I thought I would try to see if Sage builds in the upcoming version of
> Ubuntu, which is still early in the development stages but I think the
> compilers and other basic system stuff are stable. But there's some kind
> of linker error:
>
> ../kernel/libkernel.a(mod_raw.o): In function `dynl_op
> I've updated ECL to the latest upstream release
>
> http://boxen.math.washington.edu/home/kirkby/patches/ecl-11.1.1.spkg
>
> Can people test this package, then run the doctests. Note the changes are
> not committed yet, but the are a note in SPKG.txt, and of course the
> source code has changed
> On 10 February 2011 20:32, kcrisman wrote:
> > I get essentially (probably exactly) the same errors on OS X 10.4
> > PPC.If anyone else tries this, don't forget you have to rebuild (./
> > sage -f maxima) Maxima after building the new ECL.
> >
> > Francois' idea is great. I mentioned the a
> On 10 February 2011 20:59, Francois Bissey
>
> wrote:
> > Reading the message linked by Karl it seems easy to patch for this
> > behavior. Of course there could be other problems elsewhere with a
> > similar origin. I'd say we should go ahead with a patch in
> > On 10 February 2011 20:59, Francois Bissey
> >
> > It appears this was a bug created by ECL which the ECL developer has
> > acknowledged
> >
> > http://www.mail-archive.com/ecls-list@lists.sourceforge.net/msg00671.html
> >
> > and is fixed in
> On 02/11/11 12:46 AM, Francois Bissey wrote:
>
> Can you post a link to your .spkg since you have created one.
>
> I assume you are using 'patch' rather than 'cp' to copy the files over,
> since 'patch' has been added to Sage.
>
> I gue
Hi all,
Just want to check something that I think is weird.
I was looking at ticket #10764 and basically fixing the deprecated
warnings in the following files:
sage/combinat/combinat_cython.pyx
sage/rings/polynomial/polynomial_real_mpfr_dense.pyx
sage/ext/interpreters/wrapper_cdf.pxd
sage/ext/inte
> On 2011-02-21 02:19, David Kirkby wrote:
> > /export/home/drkirkby/sage-4.6.2.rc0/spkg/build/cddlib-094f.p8/src/missin
> > g --run automake-1.11 --gnu
> > sh: line 1: autoconf: not found
> > automake-1.11: autoconf failed with exit status: 127
> > make: *** [Makefile.in] Error 1
> > Error buildin
> > On 2011-02-21 02:19, David Kirkby wrote:
> > > /export/home/drkirkby/sage-4.6.2.rc0/spkg/build/cddlib-094f.p8/src/miss
> > > in g --run automake-1.11 --gnu
> > > sh: line 1: autoconf: not found
> > > automake-1.11: autoconf failed with exit status: 127
> > > make: *** [Makefile.in] Error 1
> >
> Is SQLAlchemy actually used in Sage at all? We distribute an old
> version (0.5.8) as a standard spkg. However, I can't seem to find where
> it is being used:
>
> ~/sage/devel/sage/sage% grep -ri "sqlalchemy" *
> databases/database.py:#- wrap sqlalchemy
>
> So apparently it isn't imported
> On Mon, 28 Feb 2011 at 01:26PM -0800, jtyard wrote:
> > I'm running sage 4.6.1 and cannot use plot after loading mpmath.
> > Namely, running
> >
> > > from mpmath import *
> > > plot(lambda t: sin(2*pi*t), [1, 4])
> >
> > produces no output in the notebook. I'm loading mpmath because I need
>
> Although Sage builds fully and passes all doctest on 32-bit Solaris
> with gcc, there are a couple of issues I'm aware of where gcc is not
> working as well as I'd like.
>
> * R will not build 64-bit on OpenSolaris with gcc
> * The optional OpenMPI will not build with gcc on Solaris, but will
>
> This may be of interest
>
> https://www.theopensourceway.org/wiki/How_to_tell_if_a_FLOSS_project_is_doo
> med_to_FAIL
>
> and should explain why sage is not included and/or built from
> sources in any major distro. Well, I make rpms for Mandriva,
> and there is the gentoo port...
>
My turn?
> > What would be nice: better recognition that we are doing some
> > hard work that may an impact on the quality of sage in the long term
> > much like portability work. At present time you can use a gentoo
> > prefix to build sage on other linuxes and OS X, windows is the next
> > frontier (but t
> On 14 March 2011 16:40, Julien PUYDT wrote:
> > Le 14/03/2011 14:12, David Kirkby a écrit :
> >
> > The solution of finding a "good" integer is fragile : it will break
> > anytime wind will change direction.
>
> I tend to agree.
>
> > Actually, the best solution is the one I gave : handle fuz
Hi,
I have created a ticket (trac #10936) to remove scipy_sandox from sage.
Back in the day of trac #1430 it contained experimental parts waiting to be
integrated in scipy.
Time has passed and now scipy_sandbox has been discontinued for a while
upstream and one part it provided is now in scipy pr
Hi,
I am not able to look for tickets on trac. I am getting:
Report execution failed: could not write block 1 of temporary file: No space
left on device HINT: Perhaps out of disk space?
Francois
This email may be confidential and subject to legal privilege, it may
not reflect the views of the U
> On 14 March 2011 16:40, Julien PUYDT wrote:
> > Le 14/03/2011 14:12, David Kirkby a écrit :
> >> Perhaps you can find value of n, such that gamma(n) gives an exact
> >> integer result. If that happens on other CPUs too, then I suggest the
> >> argument to the doctest is changed.
> >
> > The sol
> We should resurrect http://trac.sagemath.org/sage_trac/ticket/5731 :
> Update NTL to 5.5.2 release (latest upstream).
>
> It has been sitting around for 2 years. See the ticket for the bugs
> which have been fixed.
>
> Sage Days 29?
>
Why not. sage-on-gentoo has been using it for a long time
> Alas the info on the ticket is out-of-date.
>
> Whilst GMP 4.3.0 did implement extended GCD differently, this was
> fixed in a later release (likewise for MPIR), specifically GMP 4.3.2
> and GMP 5.0.0. I don't know if recent NTL takes these later changes
> into account.
>
Since I have installs
> On 3/26/11 10:03 AM, Jonathan wrote:
> > This problem with Jmol appears to be multifaceted.
> > 1) The path to Jmol looks strange, although the error messages do
> > appear to come from Jmol.
> > 2) It looks like something is being added to the top of the script
> > file for Jmol and confusing it
> On 03/31/11 05:22 PM, Volker Braun wrote:
> >As Dave Kirby remarked,
> >
> > right now it compiles on a couple of gcc releases and essentially no
> > other compiler. And thats hardly a surprise if you look at the code. At
> > the very least the endless compiler warnings need to be looked at /
> >
An idea that may be on the constructive side.
John could you convince/help Micheal to upload his current code
in a hg repo on google code like you did with eclib?
Rather than whining we could contribute and take a snapshot
when it is satisfactory.
Francois
This email may be confidential and subje
> With a slightly hacked version of 4.7.alpha3, I get the following doctest
> failures:
>
> **
> File
> "/export/home/drkirkby/try/sage-4.7.alpha2/devel/sage/sage/plot/plot3d/para
> metric_surface.pyx", line 180:
> sage: s[:2
> In XCode 4.0.1, the default C compiler (cc) is
> gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.9)
> (see http://en.wikipedia.org/wiki/Low_Level_Virtual_Machine)
>
> whereas it also has gcc:
> gcc version 4.2.1 (Apple Inc. build 5666) (dot 3)
>
> I wonder what should be the
> I've placed here an updated package with the latest version of sqlite,
> as the one we have in Sage is 2-3 years old.
>
> http://boxen.math.washington.edu/home/kirkby/patches/sqlite-3.7.5.spkg
>
> I've built Sage from scratch using this, and found all doctests
> passed. But I'd be interested ho
Hi all,
Following an initial post by Paulo from mandriva I started
to look at using sage with python-2.7 (2.7.1 in fact).
The news is two fold:
1) sage seems to work ok. It starts.
2) a good deal of the test suite is shot.
As a consequence of 2 it is difficult to work out which parts
need to be
> Hi François,
>
> On Fri, Apr 08, 2011 at 02:08:57PM +1200, Francois Bissey wrote:
> > Following an initial post by Paulo from mandriva I started
> > to look at using sage with python-2.7 (2.7.1 in fact).
> > The news is two fold:
> > 1) sage seems to work
> On 04/ 9/11 11:05 AM, Dr. David Kirkby wrote:
> I've found after installing the following 3 files
>
> http://boxen.math.washington.edu/home/kirkby/patches/singular-3-1-1-4.p5.sp
> kg http://sage.math.washington.edu/home/dreyer/spkg/polybori-0.7.0.p2.spkg
> http://www.stp.dias.ie/~vbraun/Sage/spk
Thanks to Nicolas there is a lot of progress there. Initial test by my friend
Steve has shown that test failures is way down and the problems with
assertEqual seems to be mostly solved.
Next we have a number of warning messages that have changed and the number
of significant figures displayed by
It turns out that warnings are not visible to the end users anymore.
This is according to the python documentation:
http://docs.python.org/library/warnings.html
Section 27.6.5 to be precise.
Actually more explicit in http://docs.python.org/using/cmdline.html :
Starting from Python 2.7, DeprecationW
> Hi!
>
> It was recommended to me by Jeroen to use sage-4.7.alpha5 for rebasing
> a patch of mine.
>
> AFAIK, sage-4.7.alpha5 is not officially released yet, but I hope it
> is OK to report here that ecl fails to build. The log can be found at
> http://sage.math.washington.edu/home/SimonKing/bug
> Having a working Gentoo-prefix that one could use if the host system's
> toolchain is broken already would be very interesting.
>
> But when I played around with it I ran into some library problems. For
> example, gmp/mpir would be installed twice (host and gentoo prefix),
> potentially mutually
> Hi Francois,
> > Aside from that it is not as developer friendly as vanilla sage. You
> > cannot apply a patch and do "sage -b". Effectively to apply a patch I
> > change the ebuild and do the equivalent of "sage -ba". On the other hand
> > upgrade always works :)
>
> Can't we tell emerge to "k
> Hi Francois,
>
> On 12 Apr., 23:35, Francois Bissey
>
> wrote:
> > this is totally #10986 could you give it a review? And possibly pipe on
> > the ecl tracker upstream to tell them I am not on drugs :)
>
> Thank you! I replaced the old spkg with your
> Hi Francois,
>
> On 13 Apr., 08:35, Francois Bissey
>
> wrote:
> > > I read athttp://bugs.gentoo.org/show_bug.cgi?id=357319that the bug
> > > is fixed upstream (unless I misunderstood), so, I guess it won't be
> > > needed to tell them you are
> Hi kcrisman,
>
> On Thu, Apr 14, 2011 at 11:27 AM, kcrisman wrote:
> > We need to implement something, stat. #11191 and #11192 (both within
> > the last hour) are spam.
>
> Solution: Remove the current captcha plugin. It's trivially broken
> with a human spammer creating spam accounts. Have a
After a small number of patch (#11156 from Nicolas M. Thiery, and 2 in
#9958, one of which is from my friend Steve Trogdon) we have a clear view
of what needs to be fixed. Test done on 4.7.alpha4 + #7377 and #9969
Aside from the chatter due to change of format and messages here is
what is interest
While working on getting sage to work with python-2.7.1 I encountered a
segfault in sage which seems to come from libsingular.
In fact the backtrace points to line 127 of kernel/ideals.cc in the singular
source code:
Program received signal SIGSEGV, Segmentation fault.
id_Delete (h=0x509b078, r=
> On Wed, Apr 20, 2011 at 06:41:26PM -0700, François wrote:
> > > This test reduces to:
> > >
> > > sage: class CCls(Parent):
> > > ... def __eq__(self, other):
> > > ... return True
> > > sage: x = CCls()
> > > sage: x == None
> > > True
> > >
> > > and I
sage: x = CCls()
sage: x == None
True
So I still get True and not false as he expected.
Francois
> On Wed, Apr 20, 2011 at 22:04, Francois Bissey <
>
> francois.bis...@canterbury.ac.nz> wrote:
> > > On Wed, Apr 20, 2011 at 06:41:26PM -0700, François wrote:
> > &g
> On Thu, Apr 21, 2011 at 10:05:58PM +1200, Francois Bissey wrote:
> >> Does hitting Enter again not do it?
> >> David
> >
> >No! huu it didn't earlier this afternoon for some reason.
> >I had an ipython message. Never mind so
> On Fri, Apr 22, 2011 at 06:08:08AM +1200, Francois Bissey wrote:
> >I'll leave the patch to you! Thanks for taking care of that.
>
> http://trac.sagemath.org/sage_trac/ticket/11236
>
Thanks, building right now. Could you have a look at the two small
patches I po
> > On Fri, Apr 22, 2011 at 06:08:08AM +1200, Francois Bissey wrote:
> > >I'll leave the patch to you! Thanks for taking care of that.
> >
> > http://trac.sagemath.org/sage_trac/ticket/11236
>
> Thanks, building right now. Could you have a look at the tw
> While working on getting sage to work with python-2.7.1 I encountered a
> segfault in sage which seems to come from libsingular.
> In fact the backtrace points to line 127 of kernel/ideals.cc in the
> singular source code:
> Program received signal SIGSEGV, Segmentation fault.
> id_Delete (h=0x50
> On Apr 25, 2:56 pm, John H Palmieri wrote:
> > I can answer part of this: on Mac OS X, we don't install ATLAS at all, we
> > just rely on the system's version. I can't answer the rest of your
> > questions.
>
> Thanks, John. So I wonder if somebody could exercise the Mac system
> ATLAS/LAPACK
> On Apr 25, 4:33 pm, Francois Bissey
>
> wrote:
> > You could build numpy without lapack to check if it is the source of the
> > problem. I gave someone instructions on how to do that a while ago.
> > But that may have been on sage-release rather than sage-devel.
>
Hi all,
I have created a ticket (#11244) with fix for deprecation warning in
python-2.7. The fix should not harm a sage using python-2.6 but it has to be
reviewed.
The heart of the problem is that python devs have decided deprecation warnings
are of no value to the end user and therefore shouldn
> On Apr 26, 6:14 am, Francois Bissey:
> > Actually do we know what version of
> > ATLAS/BLAS/LAPACK is shipped with OSX?
>
> Here are a few excerpts from the sage install log file
> /Applications/sage-4.7.alpha5/install.log
> on my mac.
>
> ATLAS=atlas-3.8.
> On Tuesday, April 26, 2011 2:52:01 PM UTC-7, François wrote:
> > > On Apr 26, 6:14 am, Francois Bissey:
> > > > Actually do we know what version of
> > > > ATLAS/BLAS/LAPACK is shipped with OSX?
> > >
> > > Here are a few excerpts from
> On 27 April 2011 21:28, William Stein wrote:
> > Hi,
> >
> > Aly Deines showed me what happened when she installed Xcode 4 then
> > built Sage. She build Sage-4.7.rc0 itself, and it compiled fine.
> > However, when she ran it, it crashed on startup. The traceback
>
> > implicates Pynac:
> C
Hi Michael,
I now think it is in fact a sage bug. Harald schilly had a slightly different
version of that a month ago or so (with ecl or ecls in Gentoo speak).
The problem is that you are in the sage environment and LD_LIBRARY_PATH
set by sage is hiding the system libgd. If you look at the system
1 - 100 of 553 matches
Mail list logo
