[sage-devel] Re: VOTE: code of conduct - ends Monday at midnight, PST.

[ X] Yes -- adopt the code of conduct -- 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, send email t

[sage-devel] Re: Sage library license

On Monday, 24 February 2014 15:57:23 UTC+1, Georg S. Weber wrote: > > Uh oh. Splendid. License discussion (again). > > Since "GPL v3+" is not compatible with "GPL v2" (without "+"), a change > from GPL v2+ to GPL v3+ would mean a change to a more re

[sage-devel] Re: Sage library license

Uh oh. Splendid. License discussion (again). Since "GPL v3+" is not compatible with "GPL v2" (without "+"), a change from GPL v2+ to GPL v3+ would mean a change to a more restrictive license. IIRC, Sage-the-library always was intended to be "GPL v2+", while Sage-the-distribution might have inco

[sage-devel] Re: Pkgconfig as standard spkg

> > +1 to distributing and using our own pkgconfig. One problem I found in > rewriting the location-moving code above is that there are some cool > features of newer pkgconfigs that we couldn't necessarily take advantage > of on older systems. > > Thanks, > > Jason > > > +1 and keep you

[sage-devel] Re: "git trac" command

On Wednesday, 25 December 2013 21:36:45 UTC+1, Volker Braun wrote: > > I've been working on a "git trac" subcommand to complement the git suite > with trac integration instead of the separate UI that the sage -dev scripts > present. This project is the basis for my release management scripts, s

Re: [sage-devel] review and rebase workflow with git

On Wednesday, 18 December 2013 17:59:00 UTC+1, Jeroen Demeyer wrote: > > On 2013-12-18 08:24, Robert Bradshaw wrote: > >> 7. But since the "u/johndoe/tracabcde" branch misses everything that > went > >> into Sage in between 6.1 and 6.2, I suppose the first thing I now > should do > >> is: >

[sage-devel] review and rebase workflow with git

Hi all, I've been reading docs (good job done, BTW!) and experimenting a bit with git in the past days to get acquaintance with the new git workflow for Sage trac tickets. There's a common situation I didn't find well described yet, and I wanted to ask whether my thoughts/my intuition is right

[sage-devel] Re: Trouble compilng 5.12

FWIW, let me try to explain some background. The PIL package build system checks for various alternatives (build with or without Tcl/TK support, build with our without jpeg support, etc.), but does that in a highly selfmade way, which not always works. Sage does not need PIL to be built with jpe

[sage-devel] Re: The 2013 Spies Prize winner is...

Jeroen, our congratulations --- you do deserve this! -- 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 grou

[sage-devel] Re: Need developer account on OSX 10.4 PPC (or remove from supported platforms)

Hi, I tried to prepare my OS X 10.4 MacIntel system as good as possible for Volker (or any other that would want to help) to "ssh in", installing the most recent Sage version, the problematic new package, and so on. In the course of doing so, I found out that OS X 10.4 on MacIntel is unfortuna

[sage-devel] Re: Need developer account on OSX 10.4 PPC (or remove from supported platforms)

On Tuesday, 4 September 2012 16:49:42 UTC+2, Volker Braun wrote: > > Intel OSX 10.4 might be good enough. Would be worth a shot. > > My ssh public key is at http://www.stp.dias.ie/~vbraun/Sage/id_dsa.pub > Hi, first thanks to everybody for their supportive messages! @Volker: Would you prefe

[sage-devel] Re: Need developer account on OSX 10.4 PPC (or remove from supported platforms)

On Sunday, 2 September 2012 12:50:22 UTC+2, Volker Braun wrote: > > Something in our OSX 10.4 build uses the reference blas instead of the > accelerate framework. See http://trac.sagemath.org/10508 for some heroic > efforts by Karl-Dieter to debug this by word of mouth, but thats just not > su

[sage-devel] Re: Implementation of Farey symbols

Hi, as usual my apoplogies for not having so really much time to work on Sage lately (for quite some time now, to be honest). I hadn't heard of the terminus "Schreier Graph" before, but I think that the Wikipedia article "http://en.wikipedia.org/wiki/Schreier_coset_graph"; hits the mark. Using

Re: [sage-devel] And the 2012 Spies Sage Development Prize Winner is...

:-) -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org

[sage-devel] Re: new computer - any special Lion instructions?

On Wednesday, 6 June 2012 04:11:24 UTC+2, kcrisman wrote: > > So although my 3-year-old MacBook Pro with Snow Leopard on it works > fine, due to warranty issues my employer is basically forcing me to > get a new machine. (I won't be paying for it, or I'd say no - I love > this little guy.) >

[sage-devel] Re: FreeModule basis coercion

Hi Jan, it is my feeling that Nils is absolutely right with his remark. I looked myself quickly through http://www.sagemath.org/doc/reference/sage/matrix/matrix_integer_dense.html and what is written there about LLL --- there are at least two number theoretic packages mentioned there, that Sag

[sage-devel] Re: FreeModule basis coercion

On Tuesday, 5 June 2012 10:01:08 UTC+2, Jan Pöschko wrote: > > Hi everyone, > > I am working on the Summer of Code Lattices > projectand ran into a problem when > trying to subclass > Lattice from FreeModule_submodule_with_basis_pid. If I'm getting it >

Re: [sage-devel] Re: C build problems on MacOS 10.7 Lion.

On Tuesday, 22 May 2012 23:26:52 UTC+2, Jason Ekstrand wrote: > > On Tue, May 22, 2012 at 2:53 PM, Jason Grout > wrote: > > Sorry I haven't got back to you on this. Is XCode installed on the 10.7 > > laptop? Also, I notice that the error messages seem to indicate that > you're > > using t

Re: [sage-devel] GCC package (#12369) needs review

> Ah, maybe the link went to a wrong email. I meant the email by Georg S. > Weber > which says: > > " > the approach to "include our own GCC 4.5.1" is doomed to fail. > " > > and explains why, to which William replied "I think you really know

Re: [sage-devel] Re: which sage should i download for evaluation purposes on Snow Leopard?

Hi Anthony, thank you very much for your report! I just checked all the mirrors, and except for one (" Universidade Federal do Paraná, Brazil ") it seems all now provide the "...p0.." app dmg's. It always takes some time to synchronize for all the

Re: [sage-devel] Re: which sage should i download for evaluation purposes on Snow Leopard?

On Thursday, 5 April 2012 00:44:28 UTC+2, Anthony Durity wrote: > > To be very clear about this to avoid confusion. > > I have a white Macbook about 3 years old, designated a Macbook5,2 > > http://www.everymac.com/systems/apple/macbook/specs/macbook-core-2-duo-2.13-white-13-mid-2009-nvidia-specs.

[sage-devel] Re: which sage should i download for evaluation purposes on Snow Leopard?

> ImportError: No module named _socket > That sort of breakage should be fixed by the OS X ...-app.p0.dmg's (note the "p0") --- there was a trac a trac ticket and several discussions. I don't think it has something to do with the bitness, i.e. 32 vs. 64. Did you really use an older dmg "withou

[sage-devel] Re: Call for vote: remove MoinMoin?

On Tuesday, 27 March 2012 19:10:50 UTC+2, John H Palmieri wrote: > > This topic has been brought up here before as side notes in various > threads, but I'd like to discuss it more officially: > > Should we remove MoinMoin as a standard package? > > [x ] Yes > [ ] No > > If "yes", I'm assuming we

[sage-devel] Re: Basing new development versions of Sage on the previous development version

On 16 Mrz., 01:52, Dima Pasechnik wrote: > Should we invite Linus to do a demo release for us (unless Jeroen objects)? > /me *hides* Greg KH has some nice series in his blog about certain kinds of requests, see http://www.kroah.com/log/linux/maintainer-06.html -- To post to this group, sen

[sage-devel] Re: Basing new development versions of Sage on the previous development version

Hi Keshav, that's the diagram I have the most stomachache with: (snip) > > How it would work given current practices > - > (snip) > > 5) Another release is made, incorporating the developer's changes (X, M, > and Y), but first backing out the changes made i

[sage-devel] Re: Basing new development versions of Sage on the previous development version

On 14 Mrz., 20:43, Jeroen Demeyer wrote: > On 2012-03-14 19:20, Keshav Kini wrote:> If we switch to git, as I understand > we eventually will, patches > > (commits) made from an older dev release will be considered to "not > > apply" (not be mergeable) a lot more often than merely the cases when

[sage-devel] Re: Basing new development versions of Sage on the previous development version

> > Frankly said, it is currently *too easy* (for the release manager) to > abandon changes made to previous, already published [devel] releases > -- as if they never happened.  And whether that's beneficial to the > development and review process is at least questionable. > > 2ct, > > -leif Hi L

[sage-devel] Re: Releasing more often?

> > Jeroen, what do you think about this? > * The main bottleneck in Sage releasing is testing. It takes a lot of > time to test stuff on the Buildbot and we need some time during the > "release candidate" phase for other people to test Sage. On 6 Mrz., 12:28, Jeroen Demeyer wrote: > On 2012-

[sage-devel] Re: Basing new development versions of Sage on the previous development version

On 6 Mrz., 11:44, Keshav Kini wrote: > "Georg S. Weber" writes: > > >  Hi Keshav, > > > honestly, I don't believe that what you describe, are arguments > > against the workflow as such --- but rather arguments against waiting > > for too long bef

[sage-devel] Re: sage, gentoo-prefix & lmonade was: log messages

> When you say relocatable, do you mean the entire directory? For example, Yes! > > mv ~/src/sage-5.0.beta5 ~/src/sage-old > > ? I'm not sure how prefix handles that, but I can check. I'm sure we > could make /sage/ work, but the rest of the prefix system might be trickier. > > (Why would y

[sage-devel] Re: Basing new development versions of Sage on the previous development version

Hi Keshav, honestly, I don't believe that what you describe, are arguments against the workflow as such --- but rather arguments against waiting for too long before releasing a new official version. Sage 4.7.2 was released in last November, Sage 4.8 in January, and now it is March and Sage 5.0 mi

[sage-devel] Re: sage, gentoo-prefix & lmonade was: log messages

Hi, >> ... (too much) of the work that goes into sage is fixing external packages >> -- that work would be better spent working on the sage library ... Yes, I do share that insight, for quite some time now. It's good to see, that others think alike! Does it concern you that the support mat

[sage-devel] Re: Is Sage a pure Python/Cython library?

Well, as for the original question(s), the answer is "No, the Sage core library is not a pure Python/Cython library, so yes, essentially you can include C/C++ code." --- there are already other examples (I think some code of David Harvey for example). I think formally, the way of the integration

[sage-devel] Re: Sage mini-manual in Catalan

Hi, to my knowledge, Prof. Jordi Quer from Barcelona both speaks Catalan and knows Sage, so he might give valuable input. If the format/ licensing issues are clarified, maybe we should ask him to be the reviewer? Cheers, Georg -- To post to this group, send an email to sage-devel@googlegroups

[sage-devel] Re: Are the Sage binaries for OS X are crap?

Hi all, I finally could verify that the patch at trac 12161 is good, i.e. heals not only the original problem for OS X 10.7, but the "_PyUnicodeUCS4_AsUTF8String" incarnation, too (at least on one of my own OS X 10.6 installations --- try starting a Sage "app" after (closing all Sage and all termi

[sage-devel] Re: Are the Sage binaries for OS X are crap?

Hi, interesting. I have the faint hope that the fix at http://trac.sagemath.org/sage_trac/ticket/12161 (which I hope to review this weekend --- it requires building twice a Sage app on OS X 10.6, and then test these on OS X 10.7) will also cure this. Even though this new report is on OS X 10.6!

[sage-devel] Re: xcode and gcc

Hi, so far, three distinct topics evolved in this thread: 1. Make Sage not needing a C compiler, when one changed only .py files and then types "sage -b". That's the topic of trac #12365 (see the original post), and up to now, I read only supportive comments (to which I say +1 also). 2. Discuss

[sage-devel] Re: xcode and gcc

Hi William, unlike OS X 10.7 Lion (for which no official install DVDs exist), OS X 10.6 Snow Leopard came with/on a install DVD (either with the Mac when one bought it, or when one bought Snow Leopard later). And on those DVD(s), there is also the XCode 3.x package --- to the best of my knowledge

[sage-devel] Re: VirtualBox

> > > but its less error prone imho. > > This is probably true.  VirtualBox is massively more widely used. > When we used to distribute a coLinux version of Sage (in 2006), I > remember watching many Windows laptops crash hard due to their > low-level driver.   But that was 5 years ago, and things

[sage-devel] Re: Sage on openSUSE 12.1

On 9 Dez., 15:24, Julien Puydt wrote: > Le 09/12/2011 09:28, Georg S. Weber a crit : > > What about making sage use the system readline by default instead? > > Snark on #sagemath Hi Julien, unfortunately, there are some OSes (I think Solaris was one of them?!), where the d

[sage-devel] Re: Sage on openSUSE 12.1

Hi, after reading the discussion at http://trac.sagemath.org/sage_trac/ticket/10572 it occured to me that as a rule, rules comes with exceptions. More precisely, renaming the readline library that is bundled with sage as "sage-readline" and adapting the R spkg to look for "sage- readline" (I don

[sage-devel] Re: Sage on openSUSE 12.1

On 8 Dez., 23:54, Volker Braun wrote: > I think I'll be able to say more if you show me the install.log ;-) I agree. Possibly, some lightly tweaked new readline spkg solves this problem. But to have chance, a bit more information seems to be needed. Cheers, Georg -- To post to this group, s

[sage-devel] Re: Matplotlib uses Wrong Version of freetype when macports is installed

Hi felix, thanks for your report! > You may argue, that macports > shouldn't override anything in the first place, but I think Sage > should be robust against this problem. You're perfectly right, we know that, and there's work in progress by several developers on it. The "correct" solution wou

[sage-devel] Re: talk about sage -i and sage -f in the developer's guide?

On 15 Nov., 18:51, Bill Janssen wrote: > It would be nice if the developer's guide talked about using sage -i > and sage -f to test new spkg's.  In the section about building spkg's, > perhaps. Yes. Two or three sentences, maybe? I think you could better formulate what you (it seems) have soug

[sage-devel] Re: integrating spkg-check and spkg-install?

On 15 Nov., 21:35, Bill Janssen wrote: > Georg, > > I'll fix those problems (unwanted binaries in $SAGE_LOCAL/bin/, and > linking against unintended libraries), in my new spkg. > Please be careful to not throw away "too much". Some people buidling Sage from source do *want* a libjpeg on their s

[sage-devel] Re: why unpack the source packages?

On 15 Nov., 21:38, Bill Janssen wrote: > Fine with me. > > But if the src directory is allowed to be a modified version of > upstream, why not just integrate the Sage-specific patches directly > into the sources, too? > > Bill > > On Nov 15, 11:29 am, William Stein wrote: > Ease of workflow.

[sage-devel] Re: why unpack the source packages?

On 15 Nov., 20:29, William Stein wrote: > On Tue, Nov 15, 2011 at 11:13 AM, Bill Janssen wrote: > > I'm a bit unclear as to why third-party source packages are unpacked > > in an spkg?  Since the patching protocol is very strict, would it make > > sense for me to include Imaging-1.1.7.tar in th

[sage-devel] Re: integrating spkg-check and spkg-install?

On 15 Nov., 20:03, Bill Janssen wrote: > I'm building a new spkg for PIL 1.1.7. > > I'd like to build PIL, then run its test suite, then if that passes, > install it.  Should I just do all of that in spkg-install, or should I > run the test suite in spkg-check?  If I install it before I test it,

[sage-devel] Re: Why does pari need 1Gig of memory allocated?

On 15 Nov., 18:18, Jeroen Demeyer wrote: > On 2011-11-15 18:09, Maarten Derickx wrote:> I think 102400 byte wich is > about 1 gigabyte is a bit to much to > > allocate just at once. So the main question is where does this number > > come from and why is it so huge? > > The Heegner test simp

[sage-devel] Re: Encoding of .py files

On 11 Nov., 19:16, Jeroen Demeyer wrote: > Is there a requirement that all Sage .py files should be ASCII or is > UTF8 also accepted? > > It seems that Sphinx 1.1.2 (#10620) cares more about this: at #10112 > there is a patch with a 0xd0 byte (which is neither ASCII neither UTF8) > which is reje

[sage-devel] Re: or sage-5.0? (Re: [sage-release] Next release: sage-4.7.3 or sage-4.8?)

On 10 Nov., 13:33, Maarten Derickx wrote: > I like your ideas about guest distributions Georg. > Thanks! > The missing thing you describe: "a way to tell the host distrubution on > what packages we depend" is not really the missing thing. I think a way to > make sage configurable to use other

[sage-devel] Re: or sage-5.0? (Re: [sage-release] Next release: sage-4.7.3 or sage-4.8?)

On 9 Nov., 00:12, Maarten Derickx wrote: > It seems like there are two groups of people here with different interests. > > One is the group whose main goal (at least as related to this discussion, > since the main goal of sage is different) to make sage easily available on > as much platforms as

[sage-devel] Re: or sage-5.0? (Re: [sage-release] Next release: sage-4.7.3 or sage-4.8?)

> > So to summarize what's above : > 1) I can help with a win32 port, but by cross-compiling, as I know it's > efficient ; > 2) in fact, helping with a win32 port would be a natural follow-up to my > current work on the ARM port ; > 3) but that won't be an easy ride (especially if I'm all alone as

[sage-devel] Re: Upstream projects

On 4 Sep., 08:47, daly wrote: > The Cost of Going it Alone by Dave > Nearyhttp://blogs.gnome.org/bolsh/2011/09/01/the-cost-of-going-it-alone/ Yeah, nice post. Let's look at two absolute core components of Sage, the versions of which shipped with the current Sage-4.7.1 release are outdated: MP

[sage-devel] Re: website/download stats

Cool! There are still on average one hundred people per month to download one of the OS X 10.4 versions. It makes me happy to see, that providing these versions is still of value for so many users. Cheers, Georg -- To post to this group, send an email to sage-devel@googlegroups.com To unsubsc

[sage-devel] Re: Solving a gcd equation for polynomials

On 25 Mai, 08:18, Rob Beezer wrote: > I'm wondering if Sage has the following function for polynomials over > a field.  Mostly, I don't know if it is a common thing to expect, and > if so, I have no idea what it would be called.  So a pointer would be > of real help, if it  exists.  The paper I

[sage-devel] Re: Windows port status

On 19 Apr., 13:27, Keshav Kini wrote: > Perhaps a bit off topic, but is there any possibility of Sage ever being > ported to Windows natively, i.e. without cygwin dependencies? We have a > couple thousand lines worth of shell scripts currently underpinning Sage, > and we'd probably have to conve

[sage-devel] Re: sage & gentoo prefix

> Hi Burcin, > > it would be complicated and requires that we change the current setup. > We currently don't ship the hg tree at all. We disable -b -ba and -upgrade. > Reenabling any of these will negate the benefit of having a package manager. > That is you will get files that are not tracked anym

[sage-devel] Re: has Apple effectively forked gcc?

Hi all, interesting thread, let me toss in my 2 cents. There are also Linux distributions which do not have gcc installed by default, so users might fall into the "Cython is not usable" trap, too. Python, from v2.7 on, has some new module called "sysconfig" (see http://docs.python.org/dev/library

[sage-devel] Re: .hg and build directories in binary tarball?

On 7 Apr., 18:50, IanSR wrote: > Are ".hg" and "build" directories supposed to be in the binary tarballs?   > I'm looking, in particular, at * > sage-4.6.2-linux-64bit-red_hat_enterprise_linux_server_release_5.6_tikanga-x86_64-Linux.tar.gz.

[sage-devel] Sage in the media: article in German computer magazine c't 5/2011

Hi Sage-devel, since I visited the Heise publisher booth at the Cebit 1988, I'm a subscriber of the German computer magazine c't, and get it once a fortnight. The newest issue 05/2011, that I got today, has a full one- page (page 69) article about Sage (see e.g. weblink http://www.heise.de/ct/11/0

[sage-devel] Re: post more

Hi Sage-Devel, this January I worked on two topics. Firstly, getting Sage working as an integral part of Gentoo Prefix (a "hosted" distribution, like Cygwin, MacPorts, ...), under three host OSes: 32-bit OS X 10.4, 64-bit OS X 10.6, and Maemo 5 (a Debian-based 32-bit Linux on my N900 mobile) --- n

[sage-devel] Re: build error for sage 4.6.1 on OS X 10.5.8

Hmm, the important information seem to be: a) You try to build Sage on Mac OS X 10.5 (Leopard). b) There's a "-m64" in the third line of your output, i.e. the build system tries to build a "64-bit" library. (Then it seems that qdCocoa.o is only a 32-bit object file, hence rejected, hence later s

[sage-devel] Re: Should Sage include its own gcc ? It would add <= 1.6 MB to the Sage tarball.

On 16 Dez., 14:56, leif wrote: > On 16 Dez., 13:11, Volker Braun wrote: > > > Gentoo-prefix uses rpath instead of the LD_LIBRARY_PATH kludge, very good! > > But this also means that there won't be any binary distributions (even in > > their current broken state) until we work out the rpath-rewr

[sage-devel] Re: Should Sage include its own gcc ? It would add <= 1.6 MB to the Sage tarball.

> > I think you really know what you're talking about. I agree with your > remarks above, especially points 1 and 2 above, and your remarks about > the difficulty of building GCC itself and having different coexisting > GCC's at once are exactly right. > > Shall we start taking some genuine steps

[sage-devel] Re: Should Sage include its own gcc ? It would add <= 1.6 MB to the Sage tarball.

On 14 Dez., 16:36, Dima Pasechnik wrote: > actually, this idea won't fly on OSX, IMHO. > Using a non-Xcode compiler on OSX looks next to impossible. > On OS X, the approach to "include our own GCC 4.5.1" is doomed to fail. We could ship our own gcc-apple 4.2.1 for all supported Mac platforms (1

[sage-devel] Re: Does a doc test require a compiler?

Hi Dave, to be able to process a *.pyx file (as the doctest definitely seems to do), yes, you need a compiler (either C or even C++, depending on the .pyx file). If you want to load/attach *.pyx files, the same applies. (Behind the scenes, Cython is used to generate out of the *.pyx file a *.c, or

[sage-devel] Re: why are there two copies of the Sage library in devel/sage/build?

Watch out, there are are dragons ... :-) Let me try to give you some answers nevertheless (which might be neither correct nor complete). Essentially, Sage uses the classical Python setuptools/distutils, with some proprietary enhancements for Cython support. Classically, you have a "python setup.p

[sage-devel] Re: All of sage as a python library

> > This post is about: > >    (1) Concern about distutils/setuptools/etc., is misplaced. >    (2) Python3 and librarifying Sage. > > First, all this discussion about distutils/setuptools/david > cournapeau, etc., is actually mostly IRRELEVANT to making the core > Sage library into a standalone li

[sage-devel] Re: Is it *really* necessary for everyone to download fortran.spkg ?

Hi Francois, > > Well thanks for the plug for our work. We are quite happy to develop the > prefix :-) > part of sage-on-gentoo, so far the effort has been limited but if you are > testing it on an arch we are quite happy to try to get as much as possible > keyworded. Is the keywording the mos

[sage-devel] Re: All of sage as a python library

> > (1) Have a Python library called "sagecore", which is just the most > important standard spkg's (e.g., Singular, PARI, etc.), perhaps > eventually built *only* as shared object libraries (no standalone > interpreters). > Interesting! One challenge I see here, is that on the one hand, Pytho

[sage-devel] Re: Is it *really* necessary for everyone to download fortran.spkg ?

Hi folks, for sime time now, there is a tendency of the Sage distribution to become unmaintanable (only minutes ago, I read the upteenth message thread and trac ticket about the recurrent Suse Linux 11.x/Arch Linux bash/readline issue ...). There are several possibilities/ways to go. One way I e

[sage-devel] Re: call for comment: matplotlib config directory in SAGE_LOCAL/etc/

> Set the matplotlib configuration and cache directory to > $SAGE_LOCAL/etc/matplotlib > > Advantages: >    * Each sage directory would have its own cache of font locations > (needed since some of those fonts are inside the sage directory). > > Disadvantages: >    * To have a matplotlib custom con

[sage-devel] Re: import scipy failing in sage 4.6.alpha1

On 24 Sep., 09:40, Minh Nguyen wrote: > Hi Niles, > > On Fri, Sep 24, 2010 at 7:58 AM, Niles wrote: > > Is there something easy I "forgot" to do? > > I couldn't even get Sage to compile successfully on that machine. > Doing a serial compilation with > > $ make > > resulted in > > /usr/local/lib

[sage-devel] Re: Cloning is frustratingly slow

On 3 Aug., 08:34, Rob Beezer wrote: > I just built a clone in about a minute.  On a fresh install of > 4.5.2.rc0 created from source.  Maybe with a binary install, the docs > need to be built on the first clone? No, the problem is with relocation, but not with binary installs "per se". Proof:

[sage-devel] Re: hyperbolic geometry and fundamental domains for subgroups of PSL(2,ZZ)

On 23 Jul., 01:38, Vincent D <20100.delecr...@gmail.com> wrote: > Thank you very much for the precise answers. > > I need to do some computations with subgroups of PSL(2,Z) (not only > beautiful drawings). I also implemented some stuff to do the things I > want but it would be nice to fit the gen

[sage-devel] Re: hyperbolic geometry and fundamental domains for subgroups of PSL(2,ZZ)

Hello Vincent, just a couple of remarks: 1. This is exactly the type of threads I think that would belong to sage-nt rather than sage-devel 2. Using kind of "graph methods" it is definitely possible to give better enumerations of both coset representatives and generators than e.g. sage/modular/a

[sage-devel] Re: cephes is seriously broken

On 15 Jul., 14:17, Francesco Biscani wrote: > [possibly OT] Out of curiosity, what was the rationale for going for > SAGE on Cygwin instead of MinGW? > > Cheers, > >  Francesco. AFAIR, only the Cygwin environment is able to provide pty's (pseudo tty's) under Windows, which are needed for the p

[sage-devel] Re: OSX tester wanted

On 5 Jul., 18:03, "Dr. David Kirkby" wrote: > On 07/ 5/10 11:14 AM, Fran ois Bissey wrote: > > > Hi, > > > In making a patch for ticket #9097 I simplified the > > logic of the building sage_clib on OSX and 64 bit platforms. > > It works for Dave on solaris 64 bits. But it would be nice > > if we

[sage-devel] Why I love the open-ness of Sage

Yeah, I do favor working with Sage over, say, working with Magma, because if I run into a bug like this (nice one, eh'?): {{{ sage: V = span([[1/7,0,0] ,[0,1,0]], ZZ); V Free module of degree 3 and rank 2 over Integer Ring Echelon basis matrix: [1/7 0 0] [ 0 1 0] sage: T = matrix(ZZ,3,[1,0

[sage-devel] Re: Python process going long after Sage is exited?

I've seen this on Tiger too, and it might be related to doctesting (which both of us do rather extensively, I guess, but probably not the average user). Cheers, Georg -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-

[sage-devel] Re: Vote on making GNU patch a standard package

Since Sage already has lots and lots of "batteries included", I agree to say that we should be careful about whether additional spkgs are really needed. I vote "-1" to the inclusion of an additional "patch.spkg". May I assume there is consensus about mercurial (once successfully installed) provid

[sage-devel] Re: sage-on-gentoo status at version 4.4.4

Great work! Actually, it makes me think about installing Gentoo just to test this (I do know I don't have the time for this, but it does wet my mouth nevertheless). Two further comments from me below: > > Outstanding issues: ... > -pexpect: version 2 is outdated, version 2.4 has trouble with grap

[sage-devel] Re: Sage 4.4.4 doctest failure on Mac PPC

On 29 Jun., 04:04, Mike Hansen wrote: > On Mon, Jun 28, 2010 at 3:07 PM, Georg S. Weber > > wrote: > > I remember that once Michael Abshoff had created some mechanism to > > make the Sage/Maxima interface (i.e. the pexpect interface in general) > > produce verbose

[sage-devel] Re: Sage 4.4.4 doctest failure on Mac PPC

On 28 Jun., 19:28, kcrisman wrote: > I know there are not tons of PPC users still on these lists, but I > wanted to ask whether they had seen something weird when testing sage/ > interfaces/maxima.py.  Namely, there is a guaranteed timeout (even > with SAGE_TIMEOUT=1)!  Previously I traced t

[sage-devel] Re: maxima

Hi Ralf, as far as I know, ECL hardcodes some paths to its internals in some non-standard way. That is not a problem, unless the Sage install is moved to a different directory than it was built in. Then, an environment variable "ECL_DIR" (or something like that) has to be set, in order for ECL to

[sage-devel] Re: Call for vote: make top-level identity_matrix and zero_matrix constructors return mutable matrices again

Yes. Cheers, Georg -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org

[sage-devel] Re: matplotlib is reading old system headers, in preference to Sage ones.

> > > I mean what will happen on OS X? > > I have pkg-config installed automatically via MacPorts, so at least some > OSX systems will have the program.  In the case of matplotlib, it looks > like it has a fallback (which is taken care of in the patches in the > update spkg) > > Thanks, > > Jason

[sage-devel] Re: Sage OSX Clickable App

On 10 Jun., 02:37, Jason Grout wrote: > Karl-Dieter just showed me how to get the OSX App built using sage -bdist: > > export SAGE_APP_BUNDLE=yes > sage -bdist 4.4.2-app > > There are people I know that would *love* to have a clickable app on > OSX.  Why do we not have this as a download option

[sage-devel] Re: Sage 4.4.4.alpha0 released / build reports

On 8 Jun., 10:21, John Cremona wrote: > Built fine and all (ptestlong) tests passed on 32-but Suse and 64-bit ubuntu. > > John > Same for MacIntel OS X 10.4 (32bit). Cheers, Georg -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an em

[sage-devel] Re: Is R used as a library, or just as a command ?

Just one thought: problems may arise with libraries which are used by both the R binary and certain other binaries from Sage. E.g. "iconv" comes to my mind. Probably one has to invest a greater-than-normal amount of care (w.r.t. environment variable settings and such), to ensure that R *as well as

[sage-devel] Re: Run doctests for external projects

On 29 Mai, 08:03, Martin Raum wrote: > Hi, > > The output is indeed > > sage -t -verbose "jacobiforms/jacobiformd1nn_fegenerators.py" > Traceback (most recent call last): >   File "/home/martin/.sage// > tmp/.doctest_jacobiformd1nn_fegenerators.py", line 18, in >     from jacobiformd1nn_fegener

[sage-devel] Re: Run doctests for external projects

On 27 Mai, 21:40, Martin Raum wrote: > Hi all, > > I've got an extern project, namely, which is not currently part of the > Sage tree. Now, I want to start using doctests and I wonder how to do > it. Sage reports a mysterious error. >     sage -t  "jacobiforms/jacobiformd1nn_fegenerators.py" # S

[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

> > It also looks like that works fine now, too. > > I am now seeing an error message when starting the sage notebook - see below. > > If I displayhttp://localhost:8000instead > ofhttp://localhost:8000/?startup_token=ae62addaf110060a2765c595ea17d16 > the notebook works OK. > Best, Paul > Thank y

[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

Well, one last try, before I give up. You should have a (temporary) directory /home/leopardi/src/Sage/sage-4.4.1/spkg/build/ symmetrica-2.0.p5/. In its subdirectory src/ there is a file "makefile". Change its last line (line 12) from " $(CC) $(CFLAGS) -lm test.c bar.o bi.o boe.o bruch.o cla

[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

Sorry for replying to myself, but I just found this in the current readline spkg's install script: ... if [ -f /etc/SuSE-release ]; then if [ `grep 11.1 /etc/SuSE-release > /dev/null; echo $?` -eq 0 ]; then echo "OpenSUSE 11.1 detected" if [ -d /usr/include/readline/ ]; then

[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2

Hi, these are two (if not three) very different kinds of problems. 1. The "readline" story on OpenSuse 11.1, 11.2, ArchLinux with Sage Looking at what was done for OpenSuse 11.1 64bit: http://trac.sagemath.org/sage_trac/ticket/4946 and/or for ArchLinux http://trac.sagemath.org/sage_trac/

[sage-devel] Re: Call for votes on Sage for Mac OS X

> > 2.) Having done this (or even not), shall we deliver the Mac OS X > > binary distributions in one and the same directory, i.e. discard the > > distinction (see E above) between "intel" and "powerpc" binary > > directories? (This would imply that we should add some mechanism(s) in > > the Sage

[sage-devel] Call for votes on Sage for Mac OS X

Hi sage-devel, currently, there are several issues. I've got a bit spare time right now to work on them, but can't do that alone. Help, and helpful comments, are appreciated. Some technicalities: Mac OS X runs on PowerPC and Intel CPUs (iPhone OS runs also on ARM, but that does not matter for us

[sage-devel] Re: Sage 4.4.2.alpha0 released

The third issue I se with sage-4.4.2-alpha0 is the following. I did the usual " export SAGE_BINARY_BUILD=yes " (the PIL spkg does not build for me without this additional environment variable, something that is "accepted") and " export MAKE='make -j2' " (my machine has a Core2Duo CPU, so there), an

  1   2   3   4   >