[sage-devel] trac for review - LaTeX accents for (East) European languages

Dear sage-devel I submitted an easy to review patch which uses T1 font encoding in LaTeX header. http://trac.sagemath.org/sage_trac/ticket/8083 This should help European users and should not break anything for the others. Very easy to review IMHO, if you are interested. Robert Marik -- To post

[sage-devel] Sage on Solaris - is there a policy for testing / releasing ?

Since versions 4.2 Sage would build on Solaris 10 SPARC using gcc. The last remaining issue to prevent this: http://sagetrac.org/sage_trac/ticket/6579 which was solved 3 months ago. However, it would not build if the Sun compilers were installed - since the Sage library chose the Sun C++ rather

[sage-devel] Re: python sage : new cvxopt package planned ?

Just tried it, it builds on Linux x86 (Debian) and OSX 10.5 (PPC) Perhaps it makes sense to make a new ticket and invite testers here. Dima On Jan 26, 9:19 pm, Harald Schilly wrote: > Hi, I've just upgraded it a few minutes ago. See my comments > here:http://trac.sagemath.org/sage_trac/ticket/6

Re: [sage-devel] Re: Could / should 'prereq' be run if ever the build is restarted?

2010/1/24 Georg S. Weber : >> >> Solaris, Linux and HP-UX all have the 'ldd' command, which if used on one of >> the >> binaries that links to the fortran library, it would show up. OS X does not >> appear to support such a command. >> > > On OS X, > > the "ldd" functionality is provided by "otool

[sage-devel] Exhibit booth for 2011 joint meetings

Since this sort of decision should be made pretty early in the year I wanted to open a discussion on it. Sage has had two exhibition booths at the national (US) joint math meetings, in 2008 and 2009. This year we did not have a booth. I think those booths were extremely helpful in making people

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

On Wed, 27 Jan 2010 at 10:19AM +1100, Minh Nguyen wrote: > Hi folks, > > This is the first alpha release of Sage 4.3.2, whose final release is > planned to be out a few days before Sage Days 20. Many of the tickets > closed in this alpha0 release is due to the hard work of participants > at Sage D

[sage-devel] Re: Unknown control sequence '\texttt'

On Jan 26, 6:13 pm, lutusp wrote: > > Maybe use "view" instead of "show"? > > A good solution until text and graphics are mixed, then it fails (by > requiring what 'show' has to offer). As I said elsewhere, this problem > is worse in 4.3.1 than it was in 4.2. Give some examples, please. By the wa

[sage-devel] package needing review marked by William as critical

William created a ticket, to check for a Fortran compiler on any platform other than OS X. http://trac.sagemath.org/sage_trac/ticket/8026 and marked it as "critical". It was actually a duplicate of something I'd created a couple of tickets earlier. http://trac.sagemath.org/sage_trac/ticket/8

[sage-devel] Re: Unknown control sequence '\texttt'

> Maybe use "view" instead of "show"? A good solution until text and graphics are mixed, then it fails (by requiring what 'show' has to offer). As I said elsewhere, this problem is worse in 4.3.1 than it was in 4.2. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubs

[sage-devel] Re: about complex and graphics

You are right that this ticket isn't the same, though it is also a good one and probably can be fixed at the same time. I must have been thinking of http://trac.sagemath.org/sage_trac/ticket/7050, though, because after quite a search I can't find the other one I thought was out there! #7050 could

[sage-devel] Sage 4.3.2.alpha0 released

Hi folks, This is the first alpha release of Sage 4.3.2, whose final release is planned to be out a few days before Sage Days 20. Many of the tickets closed in this alpha0 release is due to the hard work of participants at Sage Days 19. Thanks, guys! One notable feature is an upgrade to R 2.10.1,

[sage-devel] Re: python sage : new cvxopt package planned ?

CVXOPT is developed on Ubuntu, and I've never had to do anything special to build it. If you identified a problem in the build process, please report it on the CVXOPT forum. best regards Joachim On Jan 26, 2:19 pm, Harald Schilly wrote: > Hi, I've just upgraded it a few minutes ago. See my comm

[sage-devel] Re: Unknown control sequence '\texttt'

On Jan 25, 10:44 pm, "ma...@mendelu.cz" wrote: > On 25 led, 21:40, John H Palmieri wrote: > > > sage: 'x^2' > > sage: type(factor) > > > both work fine. > > A similar problem: > sage:'x_2'  (with checked Typeset button) > and > sage: view('x_2') > produce unwanted backslash (but the TeX code "\hb

[sage-devel] Re: hosting the release note generation script on bitbucket.org

Hi folks, On Sun, Jan 24, 2010 at 9:40 AM, Minh Nguyen wrote: > If Mike Hansen would prefer > this approach as well, I'm willing to maintain his script to generate > release notes [3] and host it on bitbucket.org as well. I have uploaded to bitbucket.org [1] a complete Mercurial repository of

[sage-devel] Re: Fedora 12 build: lib/*.la broken

Volker, Much thanks for your explanation. So Sage binaries - since they depend on finding dynamic compiler libraries like libstdc++.so - must be built using compilers in standard locations on the build machine, and the target machines must have those same libraries in the same standard locations.

[sage-devel] Re: about complex and graphics

Perhaps it is this http://trac.sagemath.org/sage_trac/ticket/4838 but it is not about the same problem. I will look more carefuly as soon as possible Vincent -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+u

[sage-devel] Re: about complex and graphics

There is already a ticket (somewhere) for plotting a complex point (set) appropriately, so please check for that one and point it to your own, if possible. It should also give you a sense of desired behavior - Mathematica has something like this, for instance. Thanks! - kcrisman On Jan 26, 1:50

[sage-devel] Re: Fedora 12 build: lib/*.la broken

Hi Mariah, On Jan 26, 6:21 pm, Mariah wrote: > I guess I do not understand that "usual drawbacks" to > statically linking to which you refer.  Can you expand, please? First off all it wastes disk space; I'm trying to make a TOPCOM spkg and a naive compile/make/make install will generate 200MB of

[sage-devel] about complex and graphics

Hi, In the current code we have is a strange behavior of "point" and "line" {{{ sage: point(CC(0)) # plot the point with coordinates (0, 0) as expected sage: point(CC(1)) # plot the point with coordinates (0, 1) as expected sage: point([CC(0), CC(1)]) # plot the point with coordinates (0, 1) s

Re: [sage-devel] Re: 2 variable polynomial factorization over finite fields

2010/1/26 Bill Hart : > Indeed. I am putting in a URSS application here at Warwick for a > student to work over the summer on bivariate factoring in Sage. > Good! I still have not decided (and I know the deadline is soon). If I have a good idea I may do it, otherwise I'll leave the field for you

Re: [sage-devel] from __future__ imports and cython.py

On Jan 26, 2010, at 2:04 AM, Dag Sverre Seljebotn wrote: I think a case can be made for *always* enabling the __future__ imports that Cython provides, i.e. just add it to the pyx_preparse prefix string. After all, really long-term (Python 3-land) they will be the defaults anyway, and with

[sage-devel] Re: Fedora 12 build: lib/*.la broken

Volker, I guess I do not understand that "usual drawbacks" to statically linking to which you refer. Can you expand, please? I still am confused about what is not working in Sage. Are you talking about a program external to Sage not being able to dynamically link with the Sage libraries? Sorry

Re: [sage-devel] doc bug on new gale_ryser_theorem()

Hi, On Wed, Jan 27, 2010 at 4:30 AM, Drini wrote: > On the recently added > gale_ryser_theorem() > there's a documentation bug (also present on the changelog) This issue is now tracked at ticket #8081: http://trac.sagemath.org/sage_trac/ticket/8081 Thank you very much for your bug report. --

[sage-devel] Re: Fedora 12 build: lib/*.la broken

Hi Mariah, The problem is that no program can dlink the (C++-using) libraries. All existing spkgs apparently link statically which works but suffers from the usual drawbacks. I've tried to modify cddlib to link dynamically with gmp/mpir: http://www.stp.dias.ie/~vbraun/cddlib-094f.p3.spkg Now spk

[sage-devel] doc bug on new gale_ryser_theorem()

On the recently added gale_ryser_theorem() there's a documentation bug (also present on the changelog) "The Gale Ryser theorem asserts that if p1;p2 are two partitions of n of respective lengths k1;k2 , then there is a binary k1Âk2 matrix M such that p1 is the vector of row sums and p2 is th

[sage-devel] Re: 2 variable polynomial factorization over finite fields

Indeed. I am putting in a URSS application here at Warwick for a student to work over the summer on bivariate factoring in Sage. Bill. On Jan 13, 9:33 am, John Cremona wrote: > Thanks -- interesting discussion!  That would make a nice project for > someone to implement in Sage. > > John > > 2010

[sage-devel] Re: Fedora 12 build: lib/*.la broken

Volker, I am trying to understand what goes wrong by having the build compiler in a non-standard place. (I am the sys admin for the particular build machine in question.) Can you give me an example of what Sage command or sequence of commands fails? Mariah On Jan 26, 7:43 am, Volker Braun wro

Re: [sage-devel] Fedora 12 build: lib/*.la broken

Hi Volker, On Tue, Jan 26, 2010 at 11:43 PM, Volker Braun wrote: > $SAGE_ROOT/local/lib/*.la files contain incorrect dependency_libs on > sage-4.3.1-linux-fedora12-x86_64-Linux. Specifically, all c++ This looks to me like you used a Sage 4.3.1 binary for 64-bit Fedora 12. Would you get the same

[sage-devel] Re: gap vs guava - why was it merged?

I don't think one can rely on this. It is not guaranteed to work, although in practice you might often see this. Typically, it uses A.Hulpke's method, which is randomised: http://www.math.colostate.edu/~hulpke/paper/permclass.pdf So you are relying on a pseudorandom generator to give you exactly th

Re: [sage-devel] Re: gap vs guava - why was it merged?

On Tue, Jan 26, 2010 at 8:01 AM, Dima Pasechnik wrote: > David, > GAP does not fix an ordering of the conj. classes, or an ordering of > the irreducibles. They depend upon the way > the group comes in, and as conj. classes and irreds are often computed > by randomised procedures, > it's very hard

Re: [sage-devel] Re: symbolic units

Hi kcrisman, That was it, thanks a lot! Kinda logical, if it has trac_3852.patch trac_3852-part2.patch trac_3852-part3.patch

[sage-devel] Re: symbolic units

It looks like there are several "parts"; perhaps they all have to be applied, in order? However, the ticket doesn't make this clear. Hope this helps, - kcrisman On Jan 26, 8:11 am, Stan Schymanski wrote: > Hi William, > > I tried to apply the patch using the following command: > > hg_sage.appl

[sage-devel] Re: gap vs guava - why was it merged?

There is a related ticket out there about making character tables behave properly - that is to say, so that groups with identical character tables (such as isomorphic groups represented in different ways) can be identified. As pointed out below, that is easier said than done. But please let us kn

[sage-devel] Re: python sage : new cvxopt package planned ?

Hi, I've just upgraded it a few minutes ago. See my comments here: http://trac.sagemath.org/sage_trac/ticket/6456 I'm by far not an expert on building software and I only know that I wasn't able to compile cvxopt on my ubuntu linux machine. Therefore I did what I described above. If this spkg works

Re: [sage-devel] symbolic units

Hi William, I tried to apply the patch using the following command: hg_sage.apply('http://trac.sagemath.org/sage_trac/attachment/ticket/3852/trac_3852-part3.patch') However, the patch failed to apply with the following error message: unable to find 'sage/symbolic/units.py' for patching 7 out o

[sage-devel] Re: gap vs guava - why was it merged?

David, GAP does not fix an ordering of the conj. classes, or an ordering of the irreducibles. They depend upon the way the group comes in, and as conj. classes and irreds are often computed by randomised procedures, it's very hard to predict them. (and not fun to deal with issues that somtimes aris

[sage-devel] Re: python sage : new cvxopt package planned ?

good that I saw this thread, as I was planning to create a cvxopt-1.1.2 spkg (I need it for my work...) So, can this spkg be made "official" ? Thanks, Dima On Jan 26, 7:35 am, William Stein wrote: > On Mon, Jan 25, 2010 at 3:33 PM, Harald Schilly > > wrote: > > > On Jan 25, 11:43 pm, William St

[sage-devel] Fedora 12 build: lib/*.la broken

$SAGE_ROOT/local/lib/*.la files contain incorrect dependency_libs on sage-4.3.1-linux-fedora12-x86_64-Linux. Specifically, all c++ libraries have a dependency on /usr/local/gcc-4.4.2/x86_64-Linux-core2-fc-binutils-2.20/lib/../lib64/libstdc++.la. C-only libraries are ok. This bug must be some remnan

Re: [sage-devel] Re: gap vs guava - why was it merged?

On Tue, Jan 26, 2010 at 6:27 AM, Alex Ghitza wrote: > On Tue, 26 Jan 2010 06:19:16 -0500, David Joyner wrote: >> >> What Dima means is that the ordering returned by the character >> must of course agree with the internal ordering of the conjugacy classes. >> I assume (without having looked at you

Re: [sage-devel] Re: gap vs guava - why was it merged?

On Tue, 26 Jan 2010 03:31:57 -0800 (PST), Dima Pasechnik wrote: > > Which Sage are you using? (in my case it is 4.3.1, on Debian Linux > x86), > and with gap-4.4.12, as well as with the original 4.3.1's gap-4.4.10, > I get, > > sage: g=GL(2,3) > sage: sorted([x.values() for x in g.irreducible_c

[sage-devel] gap-4.4.12.p2.spkg - testers needed

I have created the next version of gap-4.4.12 spkg, see http://trac.sagemath.org/sage_trac/ticket/8076 for details and download location(s). In particular, testers with access to working ia64 (Linux Itanium) installations of Sage are needed! Thanks, Dima -- To post to this group, send an email

[sage-devel] Re: gap vs guava - why was it merged?

in my case sorted() does not sort that list: sage: K. = CyclotomicField(8) sage: g=GL(2,3) sage: sorted([x.values() for x in g.irreducible_characters()]) [[1, 1, 1, 1, 1, 1, 1, 1], [1, 1, 1, 1, 1, -1, -1, -1], [2, -1, 2, -1, 2, 0, 0, 0], [2, 1, -2, -1, 0, -zeta8^3 - zeta8, zeta8^3 + zeta8, 0], [2,

[sage-devel] Re: gap vs guava - why was it merged?

Alex, sorry, I didn't look through the whole patch carefully, and missed that matrix_gps/matrix_group.py and perm_gps/permgroup.py were actually patched... Which Sage are you using? (in my case it is 4.3.1, on Debian Linux x86), and with gap-4.4.12, as well as with the original 4.3.1's gap-4.4.10

Re: [sage-devel] Re: gap vs guava - why was it merged?

On Tue, 26 Jan 2010 06:19:16 -0500, David Joyner wrote: > > What Dima means is that the ordering returned by the character > must of course agree with the internal ordering of the conjugacy classes. > I assume (without having looked at your patch) that you are not > changing the functions at all

Re: [sage-devel] Re: gap vs guava - why was it merged?

On Tue, Jan 26, 2010 at 5:58 AM, Alex Ghitza wrote: > On Tue, 26 Jan 2010 02:42:14 -0800 (PST), Dima Pasechnik > wrote: >> my objection is that in order for your patch not to break things, you >> also have to patch >> irreducible_characters() >> in >> matrix_gps/matrix_group.py >> and >> perm_gp

Re: [sage-devel] Re: gap vs guava - why was it merged?

On Tue, 26 Jan 2010 02:00:34 -0800 (PST), Dima Pasechnik wrote: > yes, this works for numerical lists, but not for e.g. > [[1, 1, 1, 1, 1, 1, 1, 1], [1, 1, 1, 1, 1, -1, -1, -1], [2, -1, 2, -1, > 2, 0, 0, 0], [2, 1, -2, -1, 0, -zeta8^3 - zeta8, zeta8^3 + zeta8, 0], > [2, 1, -2, -1, 0, zeta8^3 + ze

Re: [sage-devel] Re: gap vs guava - why was it merged?

On Tue, 26 Jan 2010 02:42:14 -0800 (PST), Dima Pasechnik wrote: > my objection is that in order for your patch not to break things, you > also have to patch > irreducible_characters() > in > matrix_gps/matrix_group.py > and > perm_gps/permgroup.py > (and perhaps in other places I might have misse

[sage-devel] Re: gap vs guava - why was it merged?

my objection is that in order for your patch not to break things, you also have to patch irreducible_characters() in matrix_gps/matrix_group.py and perm_gps/permgroup.py (and perhaps in other places I might have missed) Dima On Jan 26, 6:24 pm, Alex Ghitza wrote: > On Tue, 26 Jan 2010 01:23:10 -

Re: [sage-devel] Re: gap vs guava - why was it merged?

On Tue, 26 Jan 2010 01:23:10 -0800 (PST), Dima Pasechnik wrote: > it does not help: > indeed, I do not see how e.g. the following: > > --- a/sage/groups/class_function.py Wed Jan 20 15:09:32 2010 -0800 > +++ b/sage/groups/class_function.py Tue Jan 26 09:10:38 2010 +1100 > @@ -284,7 +284,

Re: [sage-devel] from __future__ imports and cython.py

Tim Joseph Dumol wrote: Hello, On Tue, Jan 26, 2010 at 6:07 AM, msafiri > wrote: Hello everyone, ticket #7207 deals with "from __future__" imports resulting in syntax errors in the SAGE notebook. The same is true when one tries to use cython fr

[sage-devel] Re: gap vs guava - why was it merged?

yes, this works for numerical lists, but not for e.g. [[1, 1, 1, 1, 1, 1, 1, 1], [1, 1, 1, 1, 1, -1, -1, -1], [2, -1, 2, -1, 2, 0, 0, 0], [2, 1, -2, -1, 0, -zeta8^3 - zeta8, zeta8^3 + zeta8, 0], [2, 1, -2, -1, 0, zeta8^3 + zeta8, -zeta8^3 - zeta8, 0], [3, 0, 3, 0, -1, 1, 1, -1], [3, 0, 3, 0, -1, -1

Re: [sage-devel] from __future__ imports and cython.py

Hello, On Tue, Jan 26, 2010 at 6:07 AM, msafiri wrote: > Hello everyone, > ticket #7207 deals with "from __future__" imports resulting in syntax > errors in the SAGE notebook. The same is true when one tries to use > cython from the command line e.g. via cython_create_local_so(). This > is becau

Re: [sage-devel] Re: gap vs guava - why was it merged?

Hi, On Tue, Jan 26, 2010 at 8:23 PM, Dima Pasechnik wrote: > (e.g. just sort([x.degree() for x in irr])) before comparing it with > [1, 1, 4, 4, 5, 5, 6] > > (I do not know how to write such a test in Sage, though...) Does the following help? [mv...@sage ~]$ sage

[sage-devel] Re: gap vs guava - why was it merged?

it does not help: indeed, I do not see how e.g. the following: --- a/sage/groups/class_function.py Wed Jan 20 15:09:32 2010 -0800 +++ b/sage/groups/class_function.py Tue Jan 26 09:10:38 2010 +1100 @@ -284,7 +284,7 @@ sage: S5 = SymmetricGroup(5) sage: irr = S5.irr