from:"mabshoff"


Just to throw a number around: There are *157* tickets with patches
and that is an all time high.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: sage-3.2




On Nov 21, 9:45 am, Octoploid [EMAIL PROTECTED] wrote:
 On Nov 20, 10:44 pm, William Stein [EMAIL PROTECTED] wrote:

  Hi,

  For early adopters, sage-3.2 has been released.  You can get the
  source from here:http://sagemath.org/src/
  Or you can do sage -upgrade.

 I ran sage -upgrade on my system amd64, gcc  4.3.2.
 This is what I get after upgrading:


SNIP

 ImportError: /home/markus/sage/local/lib/libpynac-0.1.so.1: symbol
 _ZNKSt5ctypeIcE13_M_widen_initEv, version GLIBCXX_3.4.11 not defined
 in file libstdc++.so.6 with link time reference
 WARNING: Failure executing file: /home/markus/sage/local/bin/sage-
 startup

This seems to indicate that you upgraded from a binary build with a C+
+ compiler using a different ABI. What did you upgrade from? Did you
upgrade the C++ compiler since you last time build Sage?

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.alpha0 opened - Reviews, Reviews, Reviews




On Nov 21, 4:55 am, Gabriel Gellner [EMAIL PROTECTED] wrote:
 On Thu, Nov 20, 2008 at 06:22:10PM -0800, kcrisman wrote:

SNIP

  I'm sorry if this is described somewhere, but I couldn't figure out
  where that would be located.  A sample of before and after
  docstrings would be very helpful, especially for those of us who have
  patches that need some work and won't be ready for 3.2.1 or for a
  while after that.

 I have come late to the party. Is their any links to where I can find the
 new documentation standard?

Check out http://wiki.sagemath.org/HelpOnParsers/ReStructuredText/RstPrimer
for starters.

 thanks,
 Gabriel

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: sage-3.2




On Nov 21, 11:54 am, Tim Lahey [EMAIL PROTECTED] wrote:
 I just compiled and ran make test on Mac OS X 10.5.5
 on my MacBook 2.1GHz. All tests passed except,

SNIP

 The following tests failed:

         sage -t  devel/sage/sage/misc/sageinspect.py

 One thing I noticed is that the directory,
 /Users/tjlahey/Downloads/sage-3.2/local/lib/python2.5/site-packages/
 IPython/

 doesn't exist any more since I moved the sage installation as one can
 see in the test,
 File /Users/tjlahey/sage/devel/sage/sage/misc/sageinspect.py,

 So, this appears to be a problem with the relocation scripts, I think.

 Thoughts? Suggestions?

I think the problem here is easy-install.pth - which is an open issue
- see #4317 - but I might be completely wrong here :)

 Cheers,

 Tim.

Cheers,

Michael

 ---
 Tim Lahey
 PhD Candidate, Systems Design Engineering
 University of Waterloo
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: sage-3.2




On Nov 21, 12:42 pm, Octoploid [EMAIL PROTECTED] wrote:
 On Nov 21, 7:51 pm, mabshoff [EMAIL PROTECTED] wrote:

SNIP

  This seems to indicate that you upgraded from a binary build with a C+
  + compiler using a different ABI. What did you upgrade from? Did you
  upgrade the C++ compiler since you last time build Sage?

 There was an old and unused version of /usr/lib/libstdc++.so on my
 system.
 Libpynac must somehow picked it up. I removed the library and rebuild
 sage.
 Now everything runs fine.

Ok, that sounds about right :)

 BTW is there a way to pass -j3 to sage -upgrade ?

export MAKE=make -j3 and then run sage -upgrade

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: PolynomialRing over FractionField and Singular




On Nov 21, 6:10 pm, Guillaume Moroz [EMAIL PROTECTED] wrote:
 Hi,

Hi,

 I'm new to sage, and so far I like it!


:)

 Just my two cents here: it seems that the sage interface to singular
 is not aware that Singular handles multivariate polynomial rings with
 coefficients in a fraction field.

 sage: from sage.rings.polynomial.polynomial_singular_interface import
 can_convert_to_singular
 sage: r=Frac(QQ['a,b'])['x,y']
 sage: can_convert_to_singular(r)
 False

 However, it is possible to define it in Singular: in this case, it
 would be

 ring R=(0,a,b),(x,y),dp;

 (following the syntax 2. given 
 athttp://www.singular.uni-kl.de/Manual/latest/sing_30.htm#SEC40)

 In particular, Gröbner basis can be computed by Singular in these
 polynomial rings more efficiently than the toy algorithm currently
 used.

 I hope this can help!

This sounds very much like http://trac.sagemath.org/sage_trac/ticket/687
- but I think malb should comment.

 Best regards,

 Guillaume

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: sage-3.2




On Nov 22, 2:06 pm, Jaap Spies [EMAIL PROTECTED] wrote:
 Jaap Spies wrote:
  William Stein wrote:
  Hi,

  For early adopters, sage-3.2 has been released.  You can get the
  source from here:http://sagemath.org/src/
  Or you can do sage -upgrade.

  Binaries and an official announcement should come within a day or two.

  William

  After sage -upgrade I get:

  [EMAIL PROTECTED] sage-3.2]$ sage
  --
  | Sage Version 3.2, Release Date: 2008-11-20                         |
  | Type notebook() for the GUI, and license() for information.        |
  --
  Traceback (most recent call last):
     File /usr/local/sage/local/bin/sage-location, line 134, in module
       t, R = install_moved()
     File /usr/local/sage/local/bin/sage-location, line 18, in install_moved
       write_flags_file()
     File /usr/local/sage/local/bin/sage-location, line 63, in 
  write_flags_file
       open(flags_file,'w').write(get_flags_info())
  IOError: [Errno 13] Permission denied: 
  '/usr/local/sage/local/lib/sage-flags.txt'

  Thoughts?

  Jaap

 Sorry for the noise:

 As root: chmod a+rX -R /usr/local/sage

 solved the (non) issue.

I am not so sure this is a non-issue since that file should be created
with the right permissions. Let me think about it before I come to any
conclusion.

Meanwhile: Did you upgrade as root? Who owned the tree before?

 Jaap

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: sage-3.2




On Nov 22, 3:08 pm, William Stein [EMAIL PROTECTED] wrote:
 On Sat, Nov 22, 2008 at 3:06 PM, mabshoff [EMAIL PROTECTED] wrote:

SNIP

  Or it should truncate the no longer used spkgs to zero bytes. We
  already have a ticket to do so, but I can't find it right now.

 No, it shouldn't do that.  It should just delete them.  There's no reason
 to truncate them to 0 bytes.   Am I missing something?
 What did you have in mind?

Bragging rights, i.e My Sage install is older than yours :) - but if
people would just want to delete the archived spkgs I would be fine
with that.

  -- William

Jaap: Out of curiosity: how large is your install.log by now?

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: sage-3.2




On Nov 22, 3:41 pm, Ronan Paixão [EMAIL PROTECTED] wrote:
  It might be a very good idea to have sage -upgrade interactively ask
  the user if they really want to do this if they are upgrading a binary.
  If a user built from source in the first place, sage -upgrade is pretty
  likely to work (or at least, should be supported).  If they installed a 
  binary,
  it's reasonable to worry.

  Alternatively, maybe sage -upgrade should always interactively have
  a little quiz... :-).

   -- William

 +1 on having a quiz, but I have some reservations about it.
 When doing upgrades, one thing that I don't like is to have the install
 stop all the time asking for questions. The problem is that sage
 compilation takes a lot of time and I like to let it do that in the
 night. If one stops all the time, I have to be there to answer
 everything. That already happens with unresolved merges :(

 The ideal would be if the upgrade process made the 'quiz' in the
 beginning, so the user could answer everything up front.

The suggestion was a joke :)

 Ronan Paixão

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: sage-3.2




On Nov 22, 6:43 pm, Ronan Paixão [EMAIL PROTECTED] wrote:

SNIP

  Sure, if there actually is somebody out there who has ever used the
  spkg/archive.
  I'm kind of guessing nobody has ever used it, in which case it seems 
  completely
  pointless to support.

  William

 A compromise option would be to delete all versions except the one
 that's being upgraded from, so that archive/ only has one version.

 But even that may be pointless, since having previous versions is the
 whole point of using a version control system, and sage uses mercurial,
 which should allow to revert to old spkgs.

Nope, that won't work. Setting aside a few exceptions none of the code
in src in the spkgs is actually checked into the mercurial repos.
There is also no convenient way to figure out which spkgs were used by
sage release x.z.y.

 Ronan Paixão

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: sage-3.2




On Nov 22, 11:46 pm, Minh Nguyen [EMAIL PROTECTED] wrote:
 On Thu, Nov 20, 2008 at 1:44 PM, William Stein [EMAIL PROTECTED] wrote:

Hi Minh,

  Hi,

  For early adopters, sage-3.2 has been released.  You can get the
  source from here:http://sagemath.org/src/
  Or you can do sage -upgrade.

 Sage-3.2 built and passed all tests on these 32-bit x86 systems:

 -- Fedora 9, Kernel 2.6.25-14.fc9.i686

 -- Debian Lenny (testing), Kernel 2.6.26-1-686

Excellent.

 The source distro built fine on the following 32-bit system:

 Machine Model: MacBook2,1
 Processor Name: Intel Core 2 Duo
 Processor Speed: 2 GHz
 Memory: 1 GB
 System Version: Mac OS X 10.4.8 (8N1430)
 Kernel Version: Darwin 8.8.5

 All tests passed, except for the following two

 sage -t  devel/sage/sage/combinat/root_system/weyl_characters.py
 sage -t  devel/sage/sage/modular/abvar/homspace.py

 which gave (harmless) timed out errors. Here are the relevant error messages:

 sage -t  devel/sage/sage/combinat/root_system/weyl_characters.py***
 *** Error: TIMED OUT! *** ***
 *** *** Error: TIMED OUT! *** ***
          [2420.7 s]

#4464

 sage -t  devel/sage/sage/modular/abvar/homspace.py          *** ***
 Error: TIMED OUT! *** ***
 *** *** Error: TIMED OUT! *** ***
          [2622.1 s]

#4463

In total: ouch - how much RAM does that box have? The only reason the
timings could be so long if those tests get pushed deeply into swap.

 --
 Regards
 Minh Van Nguyen

Cheers,

Michael

 Web:http://nguyenminh2.googlepages.com
 Blog:http://mvngu.wordpress.com
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: sage-3.2




On Nov 22, 11:54 pm, Minh Nguyen [EMAIL PROTECTED] wrote:
 On Sat, Nov 22, 2008 at 11:49 PM, mabshoff [EMAIL PROTECTED] wrote:

 [...]
  The source distro built fine on the following 32-bit system:

  Machine Model: MacBook2,1
  Processor Name: Intel Core 2 Duo
  Processor Speed: 2 GHz
  Memory: 1 GB
  System Version: Mac OS X 10.4.8 (8N1430)
  Kernel Version: Darwin 8.8.5

SNIP

Hi Min,

  In total: ouch - how much RAM does that box have? The only reason the
  timings could be so long if those tests get pushed deeply into swap.

 1.0 GB of RAM

Yeah, once I hit send I noticed that you did list the amount of RAM
for that box. That is extremely strange that those tests take about 20
times as long as I would expect. Can you rerun them to see if the
problem is reproducible? You can also run with -verbose and hopefully
something will jump out.

 --
 Regards
 Minh Van Nguyen

Cheers,

Michael


 Web:http://nguyenminh2.googlepages.com
 Blog:http://mvngu.wordpress.com
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: about local/bin/ files




On Nov 23, 12:03 am, Kwankyu [EMAIL PROTECTED] wrote:
 Hi,

Hi Kwankyu,

 I want to make a patch for the file sage/local/bin/sage-notebook.
 What is the corresponding file that I should edit in sage/devel/sage-
 main tree? Perhaps I am confused.

There are several hg repos in Sage. Besides the Sage library in the
devel/sage there is also the so called scripts repo in local/bin. So
changes should be made and checked into the local/bin repo.

 Kwankyu

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: an incentive for gpu's and cuda




On Nov 23, 1:57 am, Alex Ghitza [EMAIL PROTECTED] wrote:
 Hi folks,

 I remember that the question of whether Sage could be ported to CUDA and run
 on nvidia's GPUs was already brought up on this list.  Here's another
 incentive to think about it:

 http://tech.slashdot.org/tech/08/11/23/068234.shtml

Well, those numbers are mostly not attainable in real life and it is 4
GFLops single precision. Double precision is already a whole different
game and you would be lucky to hit 1 GFlop double precision - not that
this is anything to sneeze at :)

Anyway, Clement and I have gotten FFPACK (which is the core of what
drives LinBox for example) to run on top of CUDABLAS, but we are
currently missing Tesla hardware to get the ball rolling in earnest. I
am also looking into libflame which has the potential to be used as
GPU scheduler so that all BLAS operations in Sage can be moved utilize
multiple GPU units. In the end that would accelerate everything that
uses matrixes of GP(p), charpoly and so on and we are certainly
working in that direction. Once the new Sage hardware is there we will
also stuff some GPU hardware in there.

 OK, I'll stop drooling now.

It isn't as powerful as it has been suggested, but for certain
applications it beats the living crap out of anything else (when
compared at Flops/Watt or Flops/$)

 Best,
 Alex

Cheers,

Michael

 --
 Alex Ghitza -- Lecturer in Mathematics -- The University of Melbourne --
 Australia --http://www.ms.unimelb.edu.au/~aghitza/
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: an incentive for gpu's and cuda




On Nov 23, 2:04 am, mabshoff [EMAIL PROTECTED] wrote:
 On Nov 23, 1:57 am, Alex Ghitza [EMAIL PROTECTED] wrote:

  Hi folks,

  I remember that the question of whether Sage could be ported to CUDA and run
  on nvidia's GPUs was already brought up on this list.  Here's another
  incentive to think about it:

 http://tech.slashdot.org/tech/08/11/23/068234.shtml

 Well, those numbers are mostly not attainable in real life and it is 4
 GFLops single precision. Double precision is already a whole different
 game and you would be lucky to hit 1 GFlop double precision - not that
 this is anything to sneeze at :)

actually: Peak double precision is 320 GFlops of which you might see
40% in real life. Another big issue is that limited amount of memory
on the GPU itself.

Anyway, sorry for the double post.

 Anyway, Clement and I have gotten FFPACK (which is the core of what
 drives LinBox for example) to run on top of CUDABLAS, but we are
 currently missing Tesla hardware to get the ball rolling in earnest. I
 am also looking into libflame which has the potential to be used as
 GPU scheduler so that all BLAS operations in Sage can be moved utilize
 multiple GPU units. In the end that would accelerate everything that
 uses matrixes of GP(p), charpoly and so on and we are certainly
 working in that direction. Once the new Sage hardware is there we will
 also stuff some GPU hardware in there.

  OK, I'll stop drooling now.

 It isn't as powerful as it has been suggested, but for certain
 applications it beats the living crap out of anything else (when
 compared at Flops/Watt or Flops/$)

  Best,
  Alex

Cheers,

Michael


  --
  Alex Ghitza -- Lecturer in Mathematics -- The University of Melbourne --
  Australia --http://www.ms.unimelb.edu.au/~aghitza/
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] sage.math hd space bimonthly consumption contest - November winners :)


Hello folks,

we nearly ran out of space on /home for the first time in a while. The
following accounts are using more than 1GB space and on case your name
is one the list you should consider cleaning up unused files.

Cheers,

Michael

1.9Gabhinav
5.5Gacgetchell
4.3Gadam
1.4Gaklemm
1.9Galfredo
2.0Gallan
15G binegar
1.5Gbober
3.9Gboothby
12G brettnak
1.6Gbroune
1.9Gburcin
24G burhanud
4.9Gclarita
4.8Gcraigcitro
2.7Gcswiercz
4.2Gcwitty
1.9Gdav
13G dbm25
1.8Gdeldotdr
2.9Gdfdeshom
1.1Gdisabled_accounts
14G dmharvey
1.4Gdrake
2.9Gelliottd
3.9Ggeorgesk
11G gfurnish
20K Grammian
16G gregorybard
2.5Gjacobml
1.6Gjared
7.7Gjason
1.7Gjec
2.9Gjen
1.1Gjetchev
2.7Gjkantor
7.1Gjonhanke
1.1Gjsp
5.3Gjvoight
1.1Gkathy
13G mabshoff
2.5Gmacaulay2
1.9Gmalb
1.7Gmanny
2.6Gmhansen
1.1Gnathan
2.6Gncalexan
1.1Gnils
1.2Gnoam
6.5Gnovoselt
1.8Gondrej
3.8Gpadicgroup
5.2Gpage
7.4Gpernet
3.0Gpurbon
1.4Grishikesh
3.6Grlmill
21G robertwb
2.6Groed
1.4Grpw
1.5Gsaliola
5.3Gsavitt
5.4Gshumow
7.5Gsimuw
3.1Gsuperstein
4.8Gtclemans
1.2Gtkosan
2.6Gtornaria
368Gwas
4.5Gwatkins
1.7Gwbhart
3.2Gwdj
16G yqiang


--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Sage 3.2.1.alpha0 released


Hello folks,

here goes 3.2.1.alpha0. Loads of merged patches all over the map. The
total number of ticket with patches is down to 144 from 157, but I
guess I don't need to point out that there is still plenty of patches
to go around :). The door before the big ReST transition is slowly
closing, but I would guess you have another ten days before 3.2.1 is
out. The source tarball can be found at:

http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/

Once I get a couple relocation bugs fixed there will be a binary
again. 3.2.1.alpha1 will hopefully be out in the next 72 hours, so
keep an eye on this space. The most interesting patch IMHO is
William's #4583. Now if you run

  sage -t --only-optional=magma devel/sage/sage

only the optional Magma tests are run. It takes about 2 to 3 minutes
for a complete test run since the doctests are only run if Magma
doctests are present, i.e. sage -t  --only-optional=magma devel/sage/
sage/foo.pyx takes 0.1s in case there are no Magma doctests in
foo.pyx. Not all optional packages work yet, i.e. so far only Magma,
M2 and MMA are (partially) supported. We need to fix the optional
doctests strings to get this working all over the map. Interestingly
enough this also exposes a bunch of interesting bugs when optional
doctests are not properly marked.

Cheers,

Michael

Merged in Sage 3.2.1.alpha0:

#169: Craig Citro: slice assignment not implemented for PARI C library
interface [Reviewed by Robert Bradshaw]
#846: Robert Bradshaw:  Split cdefs.pxi [Reviewed by Carl Witty]
#2304: Michael Abshoff: sparse_poly should probably be removed
[Reviewed by Nick Alexander]
#4144: Martin Albrecht: allow finite field elements in SBox
constructor [Reviewed by Carl Witty]
#4168: Robert Bradshaw: native mpfr polynomials [Reviewed by Mike
Hansen]
#4273: Jason Grout: Failure on Jordan form transformation matrices
[Reviewed by Marshall Hampton]
#4287: Paul Zimmermann, John Cremona: improve elliptic curve doctest
(part 5) [Reviewed by Alex Ghitza]
#4310: Robert Bradshaw: simplification of the coercion api [Reviewed
by Mike Hansen]
#4330: Mike Hansen: interfaces function_call(...) function is a total
MESS [Reviewed by William Stein]
#4403: Minh Nguyen: Fix Install from Source Code section in Sage
Installation Guide [Reviewed by Mike Hansen]
#4419: Mike Hansen: conversion of Permutations to GAP not implemented
[Reviewed by Franco Saliola]
#4468: Sebastien Labbe: assertion error when (some) bad color map
given [Reviewed by Mike Hansen]
#4487: Franco Saliola: add method to evaluate characters of
permutation and matrix groups [Reviewed by David Joyner, Mike Hansen]
#4528: John Cremona: Implement Krull dimension for orders in number
fields [Reviewed by Craig Citro]
#4533: Robert Bradshaw: divisors function slow for integers [Reviewed
by William Stein, John Cremona, Craig Citro]
#4540: Jason Bandlow: Symmetrica segfault converting Schur functions
to k-Schurs [Reviewed by Mike Hansen]
#4542: Marshall Hampton: polyhedra bug fix and improvments [Reviewed
by Carl Witty]
#4556: John Palmieri: nth_root for finite fields: document the fact
that 'extend' is not implemented [Reviewed by Robert Bradshaw]
#4558: Ondrej Certik: update to sympy-0.6.3.spkg (latest upstream)
[Reviewed by Michael Abshoff]
#4561: Robert Bradshaw: _fast_float_ for sin/cos, etc., in caculus.py
is implemented stupidly [Reviewed by Mike Hansen]
#4562: Jason Grout: clean up a bunch of imports in matrix CDF/RDF code
[Reviewed by Carl Witty]
#4564: Robert Bradshaw: implement long long - mpz_t [Reviewed by
Craig Citro]
#4569: Franco Saliola: problems with the Permutation constructor
function [Reviewed by Mike Hansen]
#4570: Jason Grout: change the numpy include to the standard place
[Reviewed by Robert Bradshaw]
#4573: Franco Saliola: Permutation not callable, but
PermutationGroupElement is [Reviewed by Mike Hansen]
#4577: Wilfried Huss: simple interface to scipy.optimize.leastsq
[Reviewed by Carl Witty]
#4579: Robert Bradshaw: put mpz_longlong functions in c_lib [Reviewed
by Carl Witty]
#4583: William Stein: implement sage -t --only-optional [Reviewed by
Michael Abshoff]
#4584: William Stein: remove doctest cruft -- delete sage-
doctest_old_ver [Reviewed by Michael Abshoff]
#4586: Michael Abshoff: delete sage/rings/number_field/todo.py
[Reviewed by Nick Alexander]
#4589: William Stein: sage/rings/polynomial/multi_polynomial_ideal.py
doctest failure due to #4583 [Reviewed by Michael Abshoff]
#4591: William Stein: magma -- EllipticCurve('37a').three_selmer_rank
() fails in Magma 2.14 [Reviewed by Michael Abshoff]
#4594: Minh Nguyen: typos in files under sage/algebras [Reviewed by
Michael Abshoff]
#4595: Minh Nguyen: typos in files under sage/calculus [Reviewed by
Michael Abshoff]
#4596: Craig Citro: delete sha.py [Reviewed by William Stein]


--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED

[sage-devel] Re: sage.math hd space bimonthly consumption contest - November winners :)




On Nov 23, 12:04 pm, Konrad Meyer [EMAIL PROTECTED] wrote:
 2008/11/23 mabshoff [EMAIL PROTECTED]:



  Hello folks,

  we nearly ran out of space on /home for the first time in a while. The
  following accounts are using more than 1GB space and on case your name
  is one the list you should consider cleaning up unused files.

  Cheers,

  Michael

  20K     Grammian

 That one seems to be using much more than 1GB of space :).

Yeah, damn grep and then I forgot to delete the line :)

Cheers,

Michael

 --
 Conrad
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Test Suite for Sage-FriCAS interaction?




On Nov 23, 12:04 pm, William Stein [EMAIL PROTECTED] wrote:
 On Sun, Nov 23, 2008 at 12:02 PM, Tim Lahey [EMAIL PROTECTED] wrote:

  Hi,

  I'm in the process of installing the FriCAS 1.0.3p0 optional package
  and I was wondering if there are tests to run to make sure everything
  is built and installed correctly. I'd like to run them before I start
  exploring FriCAS.

 sage -t -optional devel/sage/sage/interfaces/axiom.py

  Oh, what happened to the plan of switching to ECL for lisp? Has that
  been abandoned?

 It's not abandoned.   Michael Abshoff will comment further, I hope.

Yeah, it is still on, but I have been distracted by other things
recently. But it is now high enough on the list to happen soon since
(a) there are still problems with clisp even on x86-64 and (b) the
FriCAS people also want ecl due to some ffi issues with the clisp we
bulid.


  Thanks,

  Tim.

Cheers,

Michael

  ---
  Tim Lahey
  PhD Candidate, Systems Design Engineering
  University of Waterloo

 --
 William Stein
 Associate Professor of Mathematics
 University of Washingtonhttp://wstein.org
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Vote for ecl/boehmgc and removal of clisp


Hello folks,

this has been discussed a bunch of time, but now finally the first
official move: I would like to remove clisp and switch over to ecl as
the base for Maxima as well as the optional FriCAS spkgs. ecl is
faster, builds and works on way more platforms including 32 and 64 bit
MSVC and has been supported by Maxima since the 5.16.x release. ecl
does depend on boehm_gc which is the best of breed garbage collection
library out there. boehm_gc also has build support by pretty much
anything out there (inculding 32 and 64 bit MSVC) and we have had it
as an optional spkg for a while since M2 depends on it. If we get this
vote going we might see a switch to ecl in 3.2.1 or 3.3.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

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




On Nov 23, 12:32 pm, Jaap Spies [EMAIL PROTECTED] wrote:
 Carl Witty wrote:
  On Nov 23, 8:56 am, Jaap Spies [EMAIL PROTECTED] wrote:
 [...]
  

  /home/jaap/work/downloads/sage-3.2.1.alpha0/devel/sage-main/sage/structure/
   ../ext/cdefs.pxi:32:0: 'sage.libs.gmp.all.pxd' not found

  This is because the file sage/libs/gmp/__init__.py is missing in the
  sage-3.2.1.alpha0 spkg .  (The file is present in the Mercurial
  repository, but it's not checked out.)

  You can probably fix this by doing hg update (or sage -hg update,
  if you don't have a separate copy of Mercurial) in the sage-main
  directory, and then restarting the build.

 Thanks, but just typing make did the job.

 real    112m26.207s
 user    104m21.590s
 sys     3m45.201s
 To install gap, gp, singular, etc., scripts
 in a standard bin directory, start sage and
 type something like
     sage: install_scripts('/usr/local/bin')
 at the SAGE command prompt.

 SAGE build/upgrade complete!
 [EMAIL PROTECTED] sage-3.2.1.alpha0]$ cd devel/sage
 [EMAIL PROTECTED] sage]$ hg update
 0 files updated, 0 files merged, 0 files removed, 0 files unresolved


Good.

I did an hg update -C followed by a sage -b and got an error due
to Cython that was only fixed by a sage -ba. I would very much claim
that I found another bug in the new setup.py, but I see if I can
reproduce this first before opening a ticket.

What is now more important is to fix the -sdist issue here fast for
alpha1.

 Jaap

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Vote for ecl/boehmgc and removal of clisp


On Nov 23, 1:03 pm, John Cremona [EMAIL PROTECTED] wrote:

Hi,

 Before I jump on the bandwagon, are there any arguments at all against
 this?

Not that I can see. The main reason we chose clisp over gcl for
example that it worked better than any other lisp implementation
supported by Maxima (and I am being generous when I write 'working'
here). There are other lisp implementations out there that support
building Maxima and are even faster than ecl for many things, i.e.
sbcl for example, but those are not self hosted, i.e. without a lisp
compiler you cannot compile sbcl. Since back in the day when Maxima
was added to Sage it did not support ecl the only choice was clisp and
considering the number of build and run time problems we had it is a
miracle that it took so long to dump clisp. To add to the list of
clisp issues: Most gcc 4.x releases lead to Maxima segfaulting when
clisp is build with more than -O0, so performance is worst than it
could be. On Solaris/Sparc *no* gcc after gcc 3.3 seems to result in a
working clisp binary. I have also played with clisp 2.46 and when I
run Maxima's test suite under valgrind I found a couple bad things
that clisp was doing. Unfortunately I no longer have that test setup
and I must have deleted the valgrind logs, so I never reported the
issue upstream.

One problem with ecl is that it requires a working gcc when you want
to compile lisp code, but the disadvantage here is greatly out weight
by the fact that all the bits we need from Maxima just work - so I
couldn't care less about the lisp compilation problems. I would assume
that the number of people installing Sage to use it for its lisp are
about zero :)

So in the end that leads me to believe that the Sage project is
gaining here by replacing clisp by ecl.

 I can see the benefits, and the only cost is in someone other
 than me making it work...which makes it rather easy to vote +!

Yes, I always vote +1 on nice things other people do :)

 John

Cheers,

Michael

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

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




On Nov 23, 9:30 am, Carl Witty [EMAIL PROTECTED] wrote:
 On Nov 23, 8:56 am, Jaap Spies [EMAIL PROTECTED] wrote:

SNIP

 This is because the file sage/libs/gmp/__init__.py is missing in the
 sage-3.2.1.alpha0 spkg .  (The file is present in the Mercurial
 repository, but it's not checked out.)

 You can probably fix this by doing hg update (or sage -hg update,
 if you don't have a separate copy of Mercurial) in the sage-main
 directory, and then restarting the build.

Yep, the fix here is to add the file explicitly to MANIFEST.in. I have
made this #4598.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: changelog out of date




On Nov 23, 1:22 pm, Stan Schymanski [EMAIL PROTECTED] wrote:
 Hello everyone,

Hi Stan,

 This is not of a very high priority, but I just noticed that the
 newest entry inhttp://www.sagemath.org/src/changelog.txtis:

 July 09, 2008
 -

 Hello folks,

 Sage 3.0.4 has been released on July 9th, 2008.

 Is there another way of getting a summary of the changes in the
 releases since then?

Look at HISTORY.txt, but that one also goes only up to 3.1.2 I think.
I am in process of updating it for 3.1.3 to 3.2. I think we should get
rid of either changelog.txt or HISTORY.txt and only ship one of those
files so we don't forget to update either one. The file we chose
should be up on the website as well in the Sage distribution.

The best information on what is going on is always in trac - see
http://trac.sagemath.org/sage_trac/roadmap?show=all

 Cheers
 Stan

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] trac account name map to real names?


Hello folks,

when one wants to add people to the CC field in trac one can either
use a full email address or a person's trac account name. The later
one is strongly preferred since it will prevent spam harvesters from
collecting that email address. The problem now for many people seems
to be the mapping between names and account names, so I am willing to
add a trac wiki page that lists the real name of every trac account.
We currently have in excess of 150 accounts in the Sage trac, so
before I go off and do this I wanted to hear what people think. There
is a privacy issue, so should this be opt in or opt out?

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

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




On Nov 23, 2:05 pm, William Stein [EMAIL PROTECTED] wrote:
 On Sun, Nov 23, 2008 at 2:01 PM, Jaap Spies [EMAIL PROTECTED] wrote:

  mabshoff wrote:
  Hello folks,

  here goes 3.2.1.alpha0. Loads of merged patches all over the map. The
  total number of ticket with patches is down to 144 from 157, but I
  guess I don't need to point out that there is still plenty of patches
  to go around :). The door before the big ReST transition is slowly
  closing, but I would guess you have another ten days before 3.2.1 is
  out. The source tarball can be found at:

 http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/

  On Fedora 9, 32 bits:

  The following tests failed:

         sage -t  devel/sage/sage/rings/polynomial/multi_polynomial_ideal.py
         sage -t  
  devel/sage/sage/schemes/elliptic_curves/ell_rational_field.py
  Total time for all tests: 5315.2 seconds

  sage -t  
  devel/sage/sage/rings/polynomial/multi_polynomial_ideal.py* 
  *
  File 
  /home/jaap/work/downloads/sage-3.2.1.alpha0/devel/sage/sage/rings/polynomi 
  al/multi_polynomial_ideal.py, line 58:
      sage: S.a,b = R.quotient((x^2 + y^2, 17))
  Expected:
      verbose 0 ... Warning: falling back to very slow toy implementation.
  Got nothing
  **
  File 
  /home/jaap/work/downloads/sage-3.2.1.alpha0/devel/sage/sage/rings/polynomi 
  al/multi_polynomial_ideal.py, line 145:
      sage: I.groebner_basis()
  Expected:
      verbose 0 ... Warning: falling back to very slow toy implementation.
      [x + y + z, y^2 + y + 23234, y*z + y + 26532, 2*y + 158864, z^2 + 
  17223, 2*z + 41856, 164878]
  Got:
      [x + y + z, y^2 + y + 23234, y*z + y + 26532, 2*y - 6014, z^2 + 17223, 
  2*z + 41856, 164878]

 These are because you have the optional m2 installed.  Michael's going
 to change the above two doctests to be:

    # optional - no_macaulay2

 since they currently can't really be tested if you *do* have M2!

Hmm, the above looks more like an issue with M2 returning different
results on 32 bit boxen or different version of M2.

Jaap: do you have M2 installed and if so which release? If you don't
have M2 we have an issue with the toy implementation of Gbases over
ZZ.

  **
  1 items had failures:
     2 of  48 in __main__.example_0
  ***Test Failed*** 2 failures.
  For whitespace errors, see the file 
  /home/jaap/downloads/sage-3.2.1.alpha0/tmp/.doctest_multi_polynomial_ideal. 
  py
          [13.5 s]
  exit code: 1024

  sage -t  
  devel/sage/sage/schemes/elliptic_curves/ell_rational_field.py** 
  
  File 
  /home/jaap/downloads/sage-3.2.1.alpha0/devel/sage/sage/schemes/elliptic_cu 
  rves/ell_rational_field.py, line 1183:
      sage: EllipticCurve('14a1').three_selmer_rank()
  Exception raised:
  [...]
      TypeError: Unable to start magma because the command 'magma -n' failed.

 The above should be tagged with

   # optional - magma

 Michael -- can you take care of the above two tags?

Yes - this is now #4599

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Opensees



On Nov 23, 2:01 pm, ahmet alper parker [EMAIL PROTECTED] wrote:

Hi,

 Firstly, I want to use it with R and with some other packages in which I can
 signal process, optimize etc (there are many opportunities I think) and I
 want to exchange data with opensees. Yes it is opensource but with the
 restriction that you can distribute it for noncommercial purposes but you

This sounds unclear to me. Anything that is distributed with the
standard Sage has to be GPL V2+ compatible. The above sounds like it
wouldn't be, but IANAL.

 can not distribute (or integrate it) with commercial applications, but
 indeed you can use it for commercial purposes (which sounds to me very hard
 to control for which purposes I am distributing it!). You can find the
 latest modified license 
 athttp://opensees.berkeley.edu/cgi-bin/cvsweb.cgi/~checkout~/OpenSees/C...
 Also, yes it is built on tcl/tk and requires it for now.

The dependency on tcl/tk is also a large issue and would be a large
hurdle for the inclusion in standard Sage. But we will certainly be
happy to have an optional or experimental spkg of you want to provide
one.

 I think it will be great to use it with Sage too :)

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: trac account name map to real names?




On Nov 23, 2:10 pm, David Joyner [EMAIL PROTECTED] wrote:
 Sounds good to me.
 Isn't it correct that only account holders can view the wiki page you
 are planning?

We could restrict the page to people with logins, but that doesn't fix
the privacy issue.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: trac account name map to real names?




On Nov 23, 2:12 pm, Martin Albrecht [EMAIL PROTECTED]
wrote:
  We currently have in excess of 150 accounts in the Sage trac, so
  before I go off and do this I wanted to hear what people think. There
  is a privacy issue, so should this be opt in or opt out?

 Great idea but I think it should be opt in: better save than sorry.

+1

But I am lazy and do not want to write 150 emails to various
people :). So can people with trac accounts who read this opt in via
the list or add themselves at the bottom of 
http://trac.sagemath.org/sage_trac/wiki/WikiStart
. Editing that page might require admin privileges for the wiki.

I am opting in.

 Cheers,
 Martin

Cheers,

Michael

 --
 name: Martin Albrecht
 _pgp:http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x8EF0DC99
 _www:http://www.informatik.uni-bremen.de/~malb
 _jab: [EMAIL PROTECTED]
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: trac account name map to real names?




On Nov 23, 2:13 pm, William Stein [EMAIL PROTECTED] wrote:
 On Sun, Nov 23, 2008 at 2:04 PM, mabshoff [EMAIL PROTECTED] wrote:
  We currently have in excess of 150 accounts in the Sage trac, so
  before I go off and do this I wanted to hear what people think.

 Damn!  There are a lot of Sage developers.   If 150 people have actually got
 accounts to do Sage development, there must be at least 150 people who
 have directly contributed to development.   There are also 690 subscribers
 to the sage-devel mailing list.   Amazing!

Yeah, we need to open the Dev map since probably 25 or so people are
missing. It is on my ToDo list and probably should become a standard
ticket for each release, i.e. Add people to DevMap for Sage x.y.z.
release

 Matlab employs more than 2000 people according to
    http://www.mathworks.com/company/aboutus/
 so we have a lot of work in order to be similar in size.  Get your friends
 to become Sage developers.

:)

  -- William

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

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




On Nov 23, 2:15 pm, Jaap Spies [EMAIL PROTECTED] wrote:
 mabshoff wrote:

Hi Jaap,

  Jaap: do you have M2 installed and if so which release? If you don't
  have M2 we have an issue with the toy implementation of Gbases over
  ZZ.

 Macaulay 2, version 1.1
 with packages: Classic, Core, Elimination, IntegralClosure, LLLBases, Parsing,
                 PrimaryDecomposition, SchurRings, TangentCone

Ok, we are already tracking the issue of M2 being used here *if* it is
installed at #4593. The M2 that were used to create the doctest is
some svn release past 1.1 and it seems that various small issues have
changed, i.e. there are a couple other optional M2 doctests that
currently fail due to changes in pretty printing of results. No
tickets yet, but if anyone cares I can open them.

By the way: we are getting closer to a fully working -t -optional -
long and maybe in 3.3 we will finally make it :)

 Jaap

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: trac account name map to real names?




On Nov 23, 5:55 pm, Ronan Paixão [EMAIL PROTECTED] wrote:
 Em Dom, 2008-11-23 às 14:15 -0800, mabshoff escreveu:

  On Nov 23, 2:10 pm, David Joyner [EMAIL PROTECTED] wrote:
   Sounds good to me.
   Isn't it correct that only account holders can view the wiki page you
   are planning?

  We could restrict the page to people with logins, but that doesn't fix
  the privacy issue.

 Not entirely, but it does to some degree, since you control account
 creation. At least you know people who have accounts, shouldn't be
 harvesters.

The concern is not that people do not people would get spammed from me
(many do since they subscribe to sage-devel :)) or other devs on this
list, but that some people might not be publicly want to be listed as
Sage developers. Obviously William and I can resolve any account name
to some email address, but that does not mean all people with trac
accounts should. This for now is purely theoretical, but I would
consider it better if the disclosure of personal data on the net is
opt-in instead of opt-out.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Vote for ecl/boehmgc and removal of clisp




On Nov 23, 1:19 pm, William Stein [EMAIL PROTECTED] wrote:
 On Sun, Nov 23, 2008 at 1:13 PM, mabshoff [EMAIL PROTECTED] wrote:


SNIP

  I can see the benefits, and the only cost is in someone other
  than me making it work...which makes it rather easy to vote +!

  Yes, I always vote +1 on nice things other people do :)

 Well you're the other person this time Michael :-).

Yes, I am painfully aware of this, too :)

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: error in trying to use the numpy cython buffer interface




On Nov 24, 8:29 am, Jason Grout [EMAIL PROTECTED] wrote:
 Jason Grout wrote:

SNIP

 Can we get this patch (or an equivalent one) into Sage as soon as possible?

I assume we will upgrade to Cython 0.10.1 in Sage 3.2.1, so if Robert
either (a) releases Cython 0.10.2 or (b)  feels comfortable with the
patch to include it on top of 0.10.1 for the cython.spkg I feel pretty
much that it should go in.

Robert: Are you working on the updated cython.spkg or is that not on
your to do list? I am sure in that case somebody else will take care
of it.

 Thanks,

 Jason

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Vote for ecl/boehmgc and removal of clisp




On Nov 24, 7:19 am, Robert Dodier [EMAIL PROTECTED] wrote:
 mabshoff wrote:

Hi Robert,

  this has been discussed a bunch of time, but now finally the first
  official move: I would like to remove clisp and switch over to ecl as
  the base for Maxima as well as the optional FriCAS spkgs. ecl is
  faster, builds and works on way more platforms including 32 and 64 bit
  MSVC and has been supported by Maxima since the 5.16.x release.

 Michael, can you summarize the status of Maxima + ECL ?
 Compilation / installation issues, test suite, known strangeness ... ?
 By the way, which versions of Maxima and ECL are you using?
 In particular ECL is a rather quickly moving target.

My initial plan is to use 0.9l+one small patch that fixes a build
issue when using an external boehm_gc that is not installed in the
default system places, i.e. /usr or /usr/local. But I am open to
getting some recent git snapshot and giving it a try since ecl seems
to be making a lot of progress. My main testing concern will be the
more exotic platforms, i.e. Linux PPC, Solaris Sparc, Linux Mips 64
and I can hopefully get a guy I know to test it on AIX.

 For the record, there will be the now-usual December release of
 Maxima next month, to be followed by another April, etc.

Yes, I know since I pretty much read every email of the Maxima
developer mailing list. I am looking forward to all the integration
work that Dieter Kaiser has been doing. Once you have a 5.17.0 release
candidate I will try it out with Sage to give feedback about any issue
that pops up on our end so you guys know if there is any trouble and
Sage can always ship the latest stable Maxima release.

 Thanks a lot for your work on Maxima + ECL.
 I know that's only a tiny fraction of all the work you do.

Well, I didn't do much of the actual work so far, so no need to thank
me. But I am glad that ecl seems to be better and better supported by
Maxima and that ecl seems to be getting stronger and stronger.

 FWIW

 Robert Dodier

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: error in trying to use the numpy cython buffer interface




On Nov 24, 12:31 pm, Robert Bradshaw [EMAIL PROTECTED]
wrote:
 On Nov 24, 2008, at 9:49 AM, mabshoff wrote:

SNIP

  Robert: Are you working on the updated cython.spkg or is that not on
  your to do list? I am sure in that case somebody else will take care
  of it.

 Cython 0.10.1 wasn't very high on my list, 'cause it didn't directly  
 impact much in Sage, but I'll get a 0.10.2 with this out soon (today  
 or tomorrow I expect).

Great. I have made the upgrade to Cython 0.10.2 #4605 and in case you
can't do the spkg I am sure Jason or I can take care of it for you :)

 - Robert

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: addressing notion impedance




On Nov 24, 1:04 pm, Yegor Bryukhov [EMAIL PROTECTED] wrote:

Hi,

  Great!  Welcome!  What sort of library are you thinking of?

 Magnus - a package for finitely presented groups, may be.

We have talked to Tim Daly about this and so far nothing has happened
in that directory. At least there are python bindings for Magnus, so
that should make things easy.

  It's a possibility.  If there was a library that only worked for sparse
  matrices, but the user wanted to use a function on a dense matrix, I
  don't see any way around converting the matrix.

  Of course, the user could ask for a sparse version of their matrix, then
  call the library routine a thousand times, then convert back to dense,
  if they wanted.

 There obviously, will be some common ground between Magnus and GAP, so
 the same group can be represented as a GAP object and as a Magnus
 object.
 I guess, I don't really understand who will be responsible for the conversion.
 ...
 Ahm, I've just looked at Sage's reference manual section on
 GAP-Singular connection (http://www.sagemath.org/doc/ref/node100.html)
 and I'm kind of unimpressed. It's ugly.
 It looks like the only benefit of using Sage is a common runtime
 environment across its libraries. Libraries' types are kept completely
 disjoint.

There is a lot of code in the Sage library that implements a lot of
mathematical algorithms, i.e. looks at modular forms for example. Some
people do believe that Sage is pretty much a way to do computations
with the included systems like GAP or Maxima, but that is only a small
part of the code base.

 Why not to do such translations (from a polynomial to a polynomial)
 transparently to the user?

The section you looked at is actually a pretty ugly example indeed and
with the current Sage getting objects from one system to another is
much more elegant. But in case of GAP there will likely not he a fast
way to convert objects as long as GAP cannot be used as a shared
library and since their interpreter and memory model is not designed
to do that it will not likely happen anytime soon. Note that a lot of
functionality in Singular is used in Sage via libSingular.

 --
 Best regards,
 Yegor

Cheers,

Michael
 __
 Yegor Bryukhov,
 Research Associate
 Center for Algorithms and Interactive Scientific Software
 City College of New York
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] From the Maxima list:


Saw this on sci.math.symbolic and thought it might be of interest to
Maxima users and developers.

http://esd.mit.edu/Faculty_Pages/moses/Macsyma.pdf

Ray
___
Maxima mailing list
[EMAIL PROTECTED]
http://www.math.utexas.edu/mailman/listinfo/maxima


--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Python 2.6




On Nov 24, 1:59 pm, William Stein [EMAIL PROTECTED] wrote:
 On Mon, Nov 24, 2008 at 1:37 PM, Jason Grout

 [EMAIL PROTECTED] wrote:
  Okay, good, so you are looking at these things.  Securely executing
  python is a subject with a long history.  Recent developments include
  the ast module, though I think the high-level ast module is just in 2.6,
  and so is not usable in Sage just yet.  See
 http://docs.python.org/dev/library/ast.html

 Changing the thread -- Why isn't Python 2.6 in Sage yet?      Does
 numpy/scipy work with Python 2.6?

It is working in the 1.3 trunk of numpy on Linux and at least 32 bit
OSX, but there are still some bugs to be shaken out of numpy. Since
scipy 0.7 beta 1 has just been tagged hours ago we can hopefully
attempt to switch once numpy 1.3 and scipy 0.7 are out.

There is also an updated pyprocessing available for Python 2.6 which
we might want to switch to since the current one we have in tree is
broken (segfaults!) on FreeBSD.

Aside from that we have some issues with the with keyword in 2.6 via
either matplotlib or our matplotlib wrapper, but there is a ticket for
it.

Sympy 0.6.3 in 3.2.1.a0 works with Python 2.6 - all the other Python
stuff needs to be tested but I am certain that most issue we find will
be fixed upstream, so it would be a good time to upgrade the various
packages we ship. What could go wrong :)

 I'm asking this so I don't have to answer this when somebody else asks :-)

Well, some problems to be worked out, but we will get there.

  -- William

Cheers,

Michael

 --
 William Stein
 Associate Professor of Mathematics
 University of Washingtonhttp://wstein.org
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Vote for ecl/boehmgc and removal of clisp



Ok, I consider this vote closed and since there were only +1 votes
also a positive conclusion has been reached.

As a first step for 3.2.1.a1 I have created #4615 which makes boehm_gc
a default spkg. It is optional now and has gotten some decent build
testing via the optional M2.spkg, so things should be relatively
smooth here (famous last words).

Any more thoughts?

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: First Integral Test Suite




On Nov 25, 4:36 am, Ondrej Certik [EMAIL PROTECTED] wrote:
 On Tue, Nov 25, 2008 at 12:37 PM, Tim Lahey [EMAIL PROTECTED] wrote:

SNIP

  You're welcome. Since I prefer to use Git rather than Mercurial,
  I've created a Git repository for my code as I work on it. I've
  put up a second test suite (smaller than the first) but unfortunately,
  because of the nature of the integrals, most fail.

  I also need to figure out a better way of handling general results
  because some of the Schaum table results aren't listed in the suite
  due to the piecewise nature of the results.

Cool. I would suggest we open a ticket so that integration in Sage
defaults to any of MMA, Maple, Maxima, Axiom and Sympy. That way
running the test suite (at least for performance) would become trivial
and I would also think that many users might find that feature useful.
Extra points for making this a generic framework and then creating
categories for integration, limits and so on so that one could easily
make Sage use a default system for those categories.

  My Git repository:

 http://github.com/tjl/sage_int_testing/tree

  People can also download an archive there.

 Excellent! I also prefer git.

Flame war! Flame war! :)

 Ondrej

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Forward: [SciPy-user] CorePy 1.0 Release (x86, Cell BE, BSD!)


This looks very cool and was posted on the Scipy list:

Hi scipy-ers -

Some of you may remember CorePy from previous SciPy conferences.
Feedback from those meetings was very helpful for planning the future
of CorePy.

Without further ado...

Announcing CorePy 1.0 - http://www.corepy.org

We are pleased to announce the latest release of CorePy. CorePy is a
complete system for developing machine-level programs in Python.
CorePy lets developers build and execute assembly-level programs
interactively from the Python command prompt, embed them directly in
Python applications, or export them to standard assembly languages.

CorePy's straightforward APIs enable the creation of complex,
high-performance applications that take advantage of processor
features usually inaccessible from high-level scripting languages,
such as multi-core execution and vector instruction sets (SSE, VMX,
SPU).

This version addresses the two most frequently asked questions about
CorePy:

1) Does CorePy support x86 processors?
   Yes! CorePy now has extensive support for 32/64-bit x86 and SSE
   ISAs on Linux and OS X*.

2) Is CorePy Open Source?
   Yes!  CorePy now uses the standard BSD license.

Of course, CorePy still supports PowerPC and Cell BE SPU processors.
In fact, for this release, the Cell run-time was redesigned from the
ground up to remove the dependency on IBM's libspe and now uses the
system-level interfaces to work directly with the SPUs (and, CorePy is
still the most fun way to program the PS3).

CorePy is written almost entirely in Python.  Its run-time system
does not rely on any external compilers or assemblers.

If you have the need to write tight, fast code from Python, want
to demystify machine-level code generation, or just miss the good-old
days of assembly hacking, check out CorePy!

And, if you don't believe us, here's our favorite user quote:

CorePy makes assembly fun again!


__credits__ = 
  CorePy is developed by Chris Mueller, Andrew Friedley, and Ben
  Martin and is supported by the Open Systems Lab at Indiana
  University.

  Chris can be reached at cmueller[underscore]dev[at]yahoo[dot]com.


__footnote__ = 
  *Any volunteers for a Windows port? :)






___
SciPy-user mailing list
[EMAIL PROTECTED]
http://projects.scipy.org/mailman/listinfo/scipy-user


--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

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




On Nov 25, 12:11 pm, Jaap Spies [EMAIL PROTECTED] wrote:

Hi Jaap,

 On Fedora 10, 32 bits (released today!) I got a build error:

 
 === =
 BUILDING MATPLOTLIB
              matplotlib: 0.98.3
                  python: 2.5.2 (r252:60911, Nov 25 2008, 20:08:09)  [GCC
                          4.3.2 20081105 (Red Hat 4.3.2-7)]
                platform: linux2

 REQUIRED DEPENDENCIES
                   numpy: 1.2.0
               freetype2: 9.18.3

 OPTIONAL BACKEND DEPENDENCIES
                  libpng: 1.2.33
 Traceback (most recent call last):
    File setup.py, line 125, in module
      if check_for_tk() or (options['build_tkagg'] is True):
    File 
 /home/jaap/Download/sage-3.2.1.alpha0/spkg/build/matplotlib-0.98.3.p2/src/ 
 setupext.py,
 line 846, in check_for_tk
      explanation = add_tk_flags(module)
    File 
 /home/jaap/Download/sage-3.2.1.alpha0/spkg/build/matplotlib-0.98.3.p2/src/ 
 setupext.py,
 line 1106, in add_tk_flags
      module.libraries.extend(['tk' + tk_ver, 'tcl' + tk_ver])
 UnboundLocalError: local variable 'tk_ver' referenced before assignment
 Error building matplotlib package.

#4176

I will try to get a VMWare image and see if I can fix this.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Sage 3.1.3, 3.1.4 and 3.2 release notes and Sage release tour


Hello folks,

at http://trac.sagemath.org/sage_trac/ticket/4567 you can find my
attempt to finally catch up with the release notes of the last three
Sage releases. I know, I know, I am rather late, but things keep
getting in the way. What is now needed to push the official button on
3.2 is a listing of the main new features. This is also required for
3.1.3  - 3.1.4 was a bug fix release so there is little left to do.

And if you looks at http://wiki.sagemath.org/RecentChanges right now
you can see that even more Sage Release tours need to be fleshed out,
i.e. for

 * 3.0.3
 * 3.0.4
 * 3.0.5
 * 3.0.6

besides the ones I mentioned above. So feel free to do some good work
here and add some material of what you did in those releases.

On 3.1.3 and 3.2 I will push the button in about an hour to get the
releases out the door. Fixes then can go into the Wiki as well as
HISTORY.txt.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.1.3, 3.1.4 and 3.2 release notes and Sage release tour




On Nov 25, 9:42 pm, Minh Nguyen [EMAIL PROTECTED] wrote:
 On Wed, Nov 26, 2008 at 4:29 PM, William Stein [EMAIL PROTECTED] wrote:

  On Tue, Nov 25, 2008 at 5:10 PM, mabshoff [EMAIL PROTECTED] wrote:

  Hello folks,

  athttp://trac.sagemath.org/sage_trac/ticket/4567you can find my
  attempt to finally catch up with the release notes of the last three
  Sage releases. I know, I know, I am rather late, but things keep
  getting in the way. What is now needed to push the official button on
  3.2 is a listing of the main new features. This is also required for
  3.1.3  - 3.1.4 was a bug fix release so there is little left to do.

  Michael has expressed a strong interest in somebody else taking
  over the role for a while of official release notes maker.  Is anybody
  interested.  This doesn't l33t coding skills, but is an extremely important
  task, and could be an excellent way for you (yes you) to volunteer
  and help make Sage better.  This isn't something you would have to do
  forever -- most things with Sage are like a relay race.

 Yeah, I'm willing to help out with making a release note that is part
 of each Sage distro, although I'm stilling learning my way through
 Sage itself. Please remind me of the process I need to follow. For
 example, if I have a partial release note for an upcoming release (or
 a current release), which server do I upload that note to? etc.

What I primarily need is someone to take care of the Sage Release Tour
bit of the release notes - everything else I do while I merge patches.
Then in the end it would be useful if someone does spell and fact
check the end result. Right now for example there is draft2 of the
3.1.3, 3.1.4 and 3.2 release notes at #4567 and I am sure they could
use some checking.

What is even more important is to do the work for the main features,
i.e. the Sage Release Tour in the wiki during development and not as
an afterthought. The best results there have always been had when the
patch authors did the changes themselves. It would also be great to
clean up the old release tours since many of them are rather
rudimentary.

Cheers,

Michael

 --
 Regards
 Minh Van Nguyen

 Web:http://nguyenminh2.googlepages.com
 Blog:http://mvngu.wordpress.com
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.1.3, 3.1.4 and 3.2 release notes and Sage release tour




On Nov 25, 9:50 pm, William Stein [EMAIL PROTECTED] wrote:
 On Tue, Nov 25, 2008 at 9:47 PM, mabshoff [EMAIL PROTECTED] wrote:

  On Nov 25, 9:42 pm, Minh Nguyen [EMAIL PROTECTED] wrote:
  On Wed, Nov 26, 2008 at 4:29 PM, William Stein [EMAIL PROTECTED] wrote:

   On Tue, Nov 25, 2008 at 5:10 PM, mabshoff [EMAIL PROTECTED] wrote:

   Hello folks,

   athttp://trac.sagemath.org/sage_trac/ticket/4567youcan find my
   attempt to finally catch up with the release notes of the last three
   Sage releases. I know, I know, I am rather late, but things keep
   getting in the way. What is now needed to push the official button on
   3.2 is a listing of the main new features. This is also required for
   3.1.3  - 3.1.4 was a bug fix release so there is little left to do.

   Michael has expressed a strong interest in somebody else taking
   over the role for a while of official release notes maker.  Is anybody
   interested.  This doesn't l33t coding skills, but is an extremely 
   important
   task, and could be an excellent way for you (yes you) to volunteer
   and help make Sage better.  This isn't something you would have to do
   forever -- most things with Sage are like a relay race.

  Yeah, I'm willing to help out with making a release note that is part
  of each Sage distro, although I'm stilling learning my way through
  Sage itself. Please remind me of the process I need to follow. For
  example, if I have a partial release note for an upcoming release (or
  a current release), which server do I upload that note to? etc.

  What I primarily need is someone to take care of the Sage Release Tour
  bit of the release notes - everything else I do while I merge patches.
  Then in the end it would be useful if someone does spell and fact
  check the end result. Right now for example there is draft2 of the
  3.1.3, 3.1.4 and 3.2 release notes at #4567 and I am sure they could
  use some checking.

 Cool -- so here Minh can (1) proofread whatever you make, and (2) make sure
 that you didn't miss something (i.e., look for differences between what
 trac said happened and what you list in the notes).

Yes.

  What is even more important is to do the work for the main features,
  i.e. the Sage Release Tour in the wiki during development and not as
  an afterthought. The best results there have always been had when the
  patch authors did the changes themselves. It would also be great to
  clean up the old release tours since many of them are rather
  rudimentary.

 So here Minh could bug the relevant people, ask questions, etc.  For
 example, Minh might directly email me and say -- Ok, explain what
 sage -only_optional is all about, in case trac and the relevant help
 in Sage isn't very helpful, and I'll answer, and he can proofread and
 post the result into the tour.    (?)

Exactly. It would be very nice if the release tours were consistent in
style, had plenty of examples and so on. I have always liked the Magma
release notes since they gave you a very good idea what had happened
in the 2.14.x to 2.14.x+1 release.

Having excellent release notes is very important IMHO especially for
people who do not live in trac and just get an email every 2 to 4
weeks that there is a new Sage release. And that is why I made the
release notes a trac ticket so I get credit for them because often I
spend more time on release notes than fixing individual bugs :)

  -- William

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.1.3, 3.1.4 and 3.2 release notes and Sage release tour




On Nov 25, 9:53 pm, Minh Nguyen [EMAIL PROTECTED] wrote:
 On Wed, Nov 26, 2008 at 4:45 PM, William Stein [EMAIL PROTECTED] wrote:

SNIP

  I'm really glad you volunteered, since you have *amazing* attention
  to detail.   You can upload release notes to a trac ticket -- there should
  be one such ticket for each release.   The format of the release notes
  is just what it has been -- and to figure out what goes in there you just
  have to use trac to figure out what tickets were closed for a given
  release, and who was involved (both patch authors and reviewers).
  And Michael Abshoff can answer any question you might have.

 Sounds good to me. OK, let me try being a release note maker/checker
 for a while.

Excellent.

Another long term project I never got to do is the cleanup of
HISTORY.txt. There are several things to do:

 (a) fix all the spelling issues
 (b) format consistently to 72 characters and wrap lines properly
 (c) get all the names consistent since I can't seem to spell certain
people correctly for each ticket
 (d) rewrite the old releases properly, i.e. SAGE-2.8.12 is not
consistent in style
 (e) improve the default template for releases, i.e. what I currently
do is organically grown and could certainly use the touch of a good PR-
smith.

This cleanup should be done section by section and I would suggest of
you want to work on this do the following:

 (a) copy HISTORY.txt to HISTORY.txt.orig
 (b) Fix one release in HISTORY.txt and make a diff to
HISTORY.txt.orig
 (c) open a ticket in trac and post the diff and let me and others
review

Then once we have agreed on form and style and so on it is all lather,
rinse repeat until HISTORY.txt is done. It would also be great if you
were willing to do Sage Release Tours for the releases where there
is none yet. This probably makes sense to a certain point, i.e. not
back all the way, but we will see. I think if you did this it wold be
a great service to the Sag project.

Cheers,

Michael


 --
 Regards
 Minh Van Nguyen

 Web:http://nguyenminh2.googlepages.com
 Blog:http://mvngu.wordpress.com
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.1.3, 3.1.4 and 3.2 release notes and Sage release tour



Oh yeah: Another thing I haven't done in ages is to get the info from
the contributors list and have them added to the Dev Map. This should
also be a ticket for each release in case we have somebody new
contributing.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage patch licenses




On Nov 25, 10:38 pm, Jason Grout [EMAIL PROTECTED] wrote:
 root wrote:
  Standard industry practice on half a million open source projects
  does not include an I have signed over my copyright on this particular
  patch button. A general copyright judgement making the current practice
  illegal would wipe out the free software movement overnight (except for
  the FSF work, but they have paid lawyers).

 To my understanding, David is not asking people to sign over their
 copyright, only for the people to explicitly license their contribution
 (but retain copyright).

Yes, that is the exact intention, i.e. we do not want the copyright of
the Sage library to be held by some legal body, but that it remains
with the original author. The goal here is to implement a cleaner
process so that if we ever have to deal a legal issue we have
everything in writing. I cannot see how anyone could misunderstand the
license of the Sage library, but the law is not about obvious
correctness, but the letter and as we have all seen the current
Amercian legal system is a little different than one would expect,
i.e. the whole set of SCO lawsuits which were merit less from the get
go but dragged on to this day in court.

 -Jason

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.1.3, 3.1.4 and 3.2 release notes and Sage release tour




On Nov 25, 10:53 pm, Jason Grout [EMAIL PROTECTED] wrote:
  What is even more important is to do the work for the main features,
  i.e. the Sage Release Tour in the wiki during development and not as
  an afterthought. The best results there have always been had when the
  patch authors did the changes themselves. It would also be great to
  clean up the old release tours since many of them are rather
  rudimentary.

  So here Minh could bug the relevant people, ask questions, etc.  For
  example, Minh might directly email me and say -- Ok, explain what
  sage -only_optional is all about, in case trac and the relevant help
  in Sage isn't very helpful, and I'll answer, and he can proofread and
  post the result into the tour.    (?)

 To this end, why don't we make this another criteria for a positive
 review?  I'm proposing that our criteria for a positive review be raised
   to something like:

 1. Patch that works (of course)

You don't say :)

 2. Doctests that document the function or show that the bug is fixed

 3. If a (major?) feature is added or changed, a short paragraph is
 posted to trac describing the addition or change.  This goes in the
 release tour (or a high-level API changelog, if it is a change of behavior).

Yes, I agree, but what is a major feature? Up to now I have looked at
the tickets closed and picked out what I considered major and then
gave people time to add what they themselves considered major. Since
it is a wiki page I have no problem to add plenty of stuff if people
are willing to provide the info. I just don't want the Release tour to
read like a 50% copy and paste of ticket subjects. I.e. a Sage Release
Tour entry should come with whole sentences including verbs :)

For a while I thought that any trac ticket which has a summary line
without a verb needs to be fixed - I hate non-desrcript tickets,
too ;)

 Thanks,

 Jason

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: how to call Sage from Lisp, was: Re: [sage-devel] Re: First Integral Test Suite




On Nov 25, 11:38 pm, Martin Rubey [EMAIL PROTECTED] wrote:

SNIP

 I admit, I'd be extremely interested in using Sage from FriCAS (i.e., the
 other way round), because I tried Python a fair bit meanwhile (I even used it
 for teaching) and I find it awful.

 The main problem to get started is to call python from lisp.  I posted a
 question on this topic a while ago in comp.lang.lisp, comp.lang.python, and
 here, but I didn't get the final answer.  It seems to be relatively easy to
 do it text based, but I don't think that makes too much sense.

Yes, that is what pexpect is doing and while it is not too bad to get
it working it isn't great for performance.

 For the record, here is the thread:

 http://groups.google.com/group/comp.lang.lisp/browse_thread/thread/36...

 The very last message links to text-based communication.

 It seems to boil down to: does Sage need the python interpreter, or is it
 possible to have Sage as a library?

In theory one could embed Python into an shared library and have that
Python interpreter run Sage. Then one would need to deal somehow with
the C library interface from lisp. It sounds doable with the right low
level knowledge, but AFAIK no one has ever done it with Sage. It would
be an interesting exercise. You would also create a derivative of
Sage, so the whole think (if you chose to distribute it) would be
under the GPL, but IANAL :)

 Martin

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage patch licenses




On Nov 26, 4:36 am, Tim Lahey [EMAIL PROTECTED] wrote:

SNIP

 My only real concern is the specific statement about GPL V2 (or later)  
 in
 what David wrote. While my test suite I'm licensing under BSD (which is
 stated at the top of each .sage file), I'm not a fan of GPL V3, so I'd
 likely license any other code under GPL V2, not GPL V2 (or later). It's
 my understanding that there already is code as part of Sage that's  
 licensed
 that way.

Nope, there isn't. We want GPL V2+ or compatible. If you prefer BSD
that if fine too, obviously. GPL V2 only code will not be merged in
the Sage library - we had that discussion a while back and all people
who submitted code as GPL V2 only relicensed the code as GPL V2+ or
compatible.

 Cheers,

 Tim.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage patch licenses




On Nov 26, 4:43 am, David Joyner [EMAIL PROTECTED] wrote:
 I know of no code which in Sage which is GPLv2 only. William or Michael, 
 please
 correct me if I am wrong.

Yes, as I mentioned above there is none.

 I think that code which is GPLv2 (only) is not GPLv2+ compatible,
 since GPL2+ says the
 modifications can be released under either GPL2 or GPL3 (at your choice).
 GPLv2 only restricts that choice.

Yes, and as is the standard Sage library cannot be GPL V2 only since
we have Apache 2 licensed code in the tree. We have that code as BSD
licensed code, so one can replace that, GSL and GNUTLS and
dependencies by GPL V2 licensed releases and the end result will be a
GPL V2 only Sage.

In general this discussion depends on how one interprets combined
work since with Python we use dlopn(), i.e. we don't link by some
people's definition. IANAL and it is irrelevant to the discussion
here, so I will stop.

In the very end we decided that the Sage library code needs to be GPL
V2+ compatible and it would take a major act to change this. It will
also have to pass the JSage panel (in case the vote would be say GPL
V2 only) and I don't see that happening.

re GPL V3: I am personally no fan of either the FSF or the GPL V3, but
I certainly like the GPL V2. But other people around here like the GPL
V3, but in the end we decided on GPL V2+.

Cheers,

Michael

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage patch licenses




On Nov 26, 4:47 am, Tim Lahey [EMAIL PROTECTED] wrote:

SNIP

  Nope, there isn't. We want GPL V2+ or compatible. If you prefer BSD
  that if fine too, obviously. GPL V2 only code will not be merged in
  the Sage library - we had that discussion a while back and all people
  who submitted code as GPL V2 only relicensed the code as GPL V2+ or
  compatible.

 I thought one of the packages (Singular maybe?) was GPL V2 only or
 did that get changed? I remember the discussion and I knew the Sage code
 itself was fine.

Nope, Singular is GPL V2 or V3. The Singular team changed the license
at our request.

 Cheers,

 Tim.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Sage 3.2.1.alpha1 released


Hello folks,

here goes 3.2.1.alpha2. This one should actually build out of the box.
Various setup.py issues have been fixed and the Magma doctests should
now all pass. In addition performance improvements to homespace and
integral_points have been merged. There is also the latest upstream
Cython.

Sources are as usual in

http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sage-3.2.1.alpha1.tar

There are currently about 137 tickets with patches in trac, so in case
you have nothing better to do  ;)

Cheers,

Michael


Merged in Sage 3.2.1.alpha1:

#3891: John Palmieri: polynomial sqrt method [Reviewed by Carl Witty]
#4320: David Joyner: linear codes improvements [Reviewed By Robert
Miller, Dan Gordan, Michael Abshoff]
#4341: Carlo Hamalainen: Optimisations + corrections to latin.py
[Reviewed by David Joyner]
#4381: Mike Hansen: sage -wthread not passed correctly to ipython
[Reviewed by Jaap Spies]
#4399: William Stein: Sage 3.1.4: magma related optional doctest
failure in sage/matrix/matrix1.pyx [Reviewed by Michael Abshoff]
#4401: William Stein: Sage 3.1.4: magma related optional doctest
failure in sage/crypto/mq/mpolynomialsystem.py [Reviewed by Michael
Abshoff]
#4463: Craig Citro: modular/abvar/homspace.py doctests are long
[Reviewed by William Stein]
#4482: William Stein: Sage 3.2.rc0: optional Magma doctest failure in
devel/sage/sage/rings/polynomial/pbori.pyx [Reviewed by Michael
Abshoff]
#4525: John Cremona: LLL-reduction of elliptic curve bases (with
resulting speed enhancement to integral_points()) [Reviewed by William
Stein, Tobias Nagel]
#4536: John Cremona: Various number field order and ideal utilities
[Reviewed by David Loeffler]
#4541: Jason Bandlow: kschur functions don't properly convert to
schur's [Reviewed by Mike Hansen]
#4553: John Palmieri: a few new methods for FiniteFieldElement
[Reviewed by John Cremona]
#4572: Robert Bradshaw: maxima output has misleading precision
[Reviewed by Michael Abshoff]
#4580: Robert Bradshaw: move mpfr declarations to a pxd [Reviewed by
Carl Witty]
#4592: Craig Citro: new setup.py dependency checking does not handle
Cython built-in pxd files [Reviewed by Carl Witty]
#4597: Craig Citro: setup.py dependency checker does not invalidate
cache correctly [Reviewed by Carl Witty]
#4598: Michael Abshoff: add sage/libs/gmp/__init__.py to MANIFEST.in
[Reviewed by Ondrej Certik]
#4599: Michael Abshoff: sage/schemes/elliptic_curves/
ell_rational_field.py doctest failure due to missing
#optional [Reviewed by Jaap Spies]
#4600: William Stein: followup issue on sage -only_optional [Reviewed
by Michael Abshoff]
#4601: William Stein: optional magma interface -- fix all broken
optional doctests by introducing _magma_init_(self, magma) signature
[Reviewed by Michael Abshoff]
#4602: Minh Nguyen: typos in files under sage/catalogue [Reviewed by
Michael Abshoff]
#4603: Minh Nguyen: trivial typos in files under sage/categories
[Reviewed by Michael Abshoff]
#4605: Robert Bradshaw: Update Cython to 0.10.2 (latest stable
upstream) [Reviewed by Michael Abshoff]
#4609: William Stein: Sage 3.2.1.a1: Make two optional magma doctests
also depend on database_gap [Reviewed by Michael Abshoff]
#4620: Craig Citro: setup.py: if the cythonization fails then next
sage -b starts to build extensions [Reviewed by Michael Abshoff]


--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.alpha1 released




On Nov 26, 12:56 pm, David Joyner [EMAIL PROTECTED] wrote:
 There was a problem with the installation on an amd64 ubuntu 8.10:

 ...

 building 'sage.libs.ntl.ntl_ZZ' extension
 creating build/temp.linux-x86_64-2.5/sage/libs/ntl
 gcc -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall
 -Wstrict-prototypes -fPIC
 -I/home/wdj/sagefiles/sage-3.2.1.alpha1/local//include
 -I/home/wdj/sagefiles/sage-3.2.1.alpha1/local//include/csage
 -I/home/wdj/sagefiles/sage-3.2.1.alpha1/devel//sage/sage/ext
 -I/home/wdj/sagefiles/sage-3.2.1.alpha1/local/include/python2.5 -c
 sage/libs/ntl/ntl_ZZ.cpp -o
 build/temp.linux-x86_64-2.5/sage/libs/ntl/ntl_ZZ.o -w
 gcc: sage/libs/ntl/ntl_ZZ.cpp: No such file or directory
 gcc: no input files
 error: command 'gcc' failed with exit status 1
 sage: There was an error installing modified sage library code.

 ERROR installing SAGE


Yep, just hit the same issue. I assume it is #4620, so I reverted that
patch temporarily and am doing a sage -ba since a sage -b doesn't
fix it. Craig?

And Jason seems to have found another issue: He mentions at #4206

   With either sage version, you might have to delete the Cython cache
by
   removing the file SAGE_ROOT/devel/sage/.cython_deps before doing
sage -br.
   This is because I remove a Cython file in the patch.

So I guess we need to open a ticket for that one, too.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.alpha1 released




On Nov 26, 1:36 pm, mabshoff [EMAIL PROTECTED] wrote:
 On Nov 26, 12:56 pm, David Joyner [EMAIL PROTECTED] wrote:



  There was a problem with the installation on an amd64 ubuntu 8.10:

  ...

  building 'sage.libs.ntl.ntl_ZZ' extension
  creating build/temp.linux-x86_64-2.5/sage/libs/ntl
  gcc -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall
  -Wstrict-prototypes -fPIC
  -I/home/wdj/sagefiles/sage-3.2.1.alpha1/local//include
  -I/home/wdj/sagefiles/sage-3.2.1.alpha1/local//include/csage
  -I/home/wdj/sagefiles/sage-3.2.1.alpha1/devel//sage/sage/ext
  -I/home/wdj/sagefiles/sage-3.2.1.alpha1/local/include/python2.5 -c
  sage/libs/ntl/ntl_ZZ.cpp -o
  build/temp.linux-x86_64-2.5/sage/libs/ntl/ntl_ZZ.o -w
  gcc: sage/libs/ntl/ntl_ZZ.cpp: No such file or directory
  gcc: no input files
  error: command 'gcc' failed with exit status 1
  sage: There was an error installing modified sage library code.

  ERROR installing SAGE

 Yep, just hit the same issue. I assume it is #4620, so I reverted that
 patch temporarily and am doing a sage -ba since a sage -b doesn't
 fix it.

Reverting #4620 temporarily allows me to build the tree. But we need
that fix for another issue, so we need a fix for the fix :)

 Craig?

 And Jason seems to have found another issue: He mentions at #4206

    With either sage version, you might have to delete the Cython cache
 by
    removing the file SAGE_ROOT/devel/sage/.cython_deps before doing
 sage -br.
    This is because I remove a Cython file in the patch.

 So I guess we need to open a ticket for that one, too.

Actually no: He just mentioned in IRC to me that it isn't the case and
he should have mentioned that this was without several fixes. We
should definitely try to remove a file and then see what happens here.
Volunteers?

 Cheers,

 Michael

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.alpha1 released




On Nov 26, 2:04 pm, Jaap Spies [EMAIL PROTECTED] wrote:
 mabshoff wrote:
  Hello folks,

  here goes 3.2.1.alpha2. This one should actually build out of the box.

 alpha1 I hope? Else I'm not keeping up pace!

Well, since I screwed up alpha1 there will be an alpha2 tonight.

 ERROR installing SAGE

See above how to fix this. William got an idea what the problem is and
is writing patch.

  There are currently about 137 tickets with patches in trac, so in case
  you have nothing better to do  ;)

 I have something better to do, but in case I find some time I'll dive
 into it :)

Well, at least the weather sucks 8)

 Jaap

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage patch licenses




On Nov 26, 10:43 am, Jason Grout [EMAIL PROTECTED] wrote:
 David Joyner wrote:
  This is less than what google or sun does. However, GAP does nothing like 
  this.
  On the other hand, GAP is organized around modules (often single-authored
  and sometimes with non-GPL'd licenses), with a small number of people
  contributing to the kernel. I don't think Maxima does this either. But
  as I pointed out
  in the original post, the book by Van Lindberg seems to be indicating
  that this is
  something he recommends thinking about.

 Linux is a huge open-source project to which lots of huge corporations
 are committing code, as well as single people.  What do they do?  What
 about other projects that have lots of people committing code?

They don't do anything, but there are author and signed-off-by (think
review) tags.

 I agree it's better to be safe than sorry, but I also am pulling for
 making the contributing process streamlined.

It seems that there are certainly disadvantages here, i.e. the
university might as its lawyers since they employ people as someone
just pointed out. So it might be best to

 (a) make it clear in trac via the upload page as RobertWB suggested
that submissions are GPL V2+ unless otherwise stated
 (b) have people voluntarily submit a CLA if they want
 (c) otherwise employ a don't ask, don't tell like policy

The Linux kernel seems to be able to manage without a CLA, so we ought
to be fine.

IANAL obviously and I don't play one on TV :)

 Jason

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.alpha1 released




On Nov 26, 2:30 pm, Jaap Spies [EMAIL PROTECTED] wrote:
 mabshoff wrote:

  On Nov 26, 2:04 pm, Jaap Spies [EMAIL PROTECTED] wrote:
  mabshoff wrote:

 Hi Michael,

hi Jaap,

  Hello folks,
  here goes 3.2.1.alpha2. This one should actually build out of the box.
  alpha1 I hope? Else I'm not keeping up pace!

  Well, since I screwed up alpha1 there will be an alpha2 tonight.

 Maybe you can merge in trac #4176, so I can try alpha2 on Fedora 10
 without hassle :).

Yep, last night/this morning I did ping you in IRC to get it in on
time for alpha0, but you were busy. At the minimum #4624 and #4628
need to get fixed and merged respectively, too, before an alpha2. But
I want to wait for more reviews today before cutting alpha2.

And for the record: Where would be fun be if an alpha didn't even
compile some of the time - otherwise people would star expecting me to
be perfect and we all know that won't happen ;)

 Jaap

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.alpha1 released


One more thing: Before doctesting run hg update -C on the local/bin
repo due to

[EMAIL PROTECTED]:/scratch/mabshoff/release-cycle/sage-3.2.1.alpha2/local/
bin$ hg sta
! ipy_profile_sage.py

I cought that on the way out, but my manual fix in the scripts spkg
was insufficient. I know the fix and there is a ticket at #4624.

My bad, this alpha1 was really terrible :(

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: First Integral Test Suite




On Nov 26, 4:58 pm, Carl Witty [EMAIL PROTECTED] wrote:

SNIP

 I'm still planning to work on this for most of the basic Sage types,
 but I don't know when I'll get to it; if anybody wants to help, let me
 know!  (The basic framework is in place in sage/misc/sage_input.py,
 and there's quite a bit of documentation on how to write the per-type
 code at the top of that file.)

 Carl

Hi Carl,

could it be done so that our coverage tool find classes with missing
sage_input functionality and then gives us a list and a score to see
what needs to be done?

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage Integral Test Suite




On Nov 26, 4:54 pm, Bill Page [EMAIL PROTECTED] wrote:
 On Wed, Nov 26, 2008 at 12:28 AM, Tim Lahey wrote:

SNIP

Hi Bill,

 In order to run these tests, it is also necessary to make some simple
 additions to the 'axiom.py' interface:

 [EMAIL PROTECTED]:~/sage-3.1.4/devel/sage-main/sage/interfaces$ hg diff
 diff -r ed3f78f99d2a sage/interfaces/axiom.py
 --- a/sage/interfaces/axiom.py  Tue Nov 25 23:45:43 2008 -0500
 +++ b/sage/interfaces/axiom.py  Wed Nov 26 19:43:59 2008 -0500
 @@ -729,7 +729,10 @@
          s = P.eval('unparse(%s::InputForm)'%self._name)
          if 'translation error' in s or 'Cannot convert' in s:
              raise NotImplementedError
 -        s = multiple_replace({'\r\n':'', # fix stupid Fortran-ish
 +        s = multiple_replace({'\r\n':'', # fix stupid Fortran-ish
 +                              'DLOG(':'log(',
 +                              'DEXP(':'exp(',
 +                              '::(':'', ',Symbol)':'',
                                'DSIN(':'sin(',
                                'DCOS(':'cos(',
                                'DTAN(':'tan(',

 

 These integrals produce some additional Fortran-style names and a
 coercion that have to be translated before the input form can be
 processed by Sage.

SNIP

Please open a ticket and attach a patch so this can get merged in
3.2.1.

There is also #4036 still open which has various improvements for the
panAxiom interface. Only a little review is required, so let's also
get this in.

 Regards,
 Bill Page.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage Integral Test Suite




On Nov 26, 5:13 pm, Tim Lahey [EMAIL PROTECTED] wrote:
 On Nov 26, 2008, at 7:54 PM, Bill Page wrote:

Hi Tim,

  One thing that I wanted to do with your code is to include comparisons
  of the answers produced by both Maxima and FriCAS as well as the
  comparison to the Schaum's tabulated value. Here is a small patch to
  'integral_test1.sage' (changes to other files are identical):

 Thanks for these additions. What I think I'll do is maintain a branch
 with these changes until the FriCAS interface changes make it into
 Sage. Do you want to submit a Trac ticket with interface changes?

I asked Bill to do so, but so far nothing has happened.

 I don't have a Trac account as of yet.

Send me an email off list after reading the bit about account names
and password at http://wiki.sagemath.org/TracGuidelines

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.alpha1 released




On Nov 26, 6:32 pm, Jaap Spies [EMAIL PROTECTED] wrote:

SNIP

 The following tests failed:

         sage -t  devel/sage/sage/rings/polynomial/multi_polynomial_ideal.py

Mmmh, M2 installed? Maybe a 32 vs. 64 bit thing for the toy
implementation?

         sage -t  devel/sage/sage/interfaces/psage.py
         sage -t  devel/sage/sage/interfaces/sage0.py
         sage -t  devel/sage/sage/misc/trace.py
         sage -t  devel/sage/sage/misc/randstate.pyx

All those are caused by #4624 - run hg update -C in the scripts
repo.  This is fixed in alpha2 which should be out in a jiffie - I am
merging the last two patches there before doing some testing this
time :)

 Total time for all tests: 5337.0 seconds

 If interested, ask me for details tomorrow.

 Jaap

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.alpha1 released




On Nov 26, 7:38 pm, John H Palmieri [EMAIL PROTECTED] wrote:

Hi John,

 On Intel Mac OS X.5: after jumping through all of the appropriate
 hoops to make this version,

:)

 sage -testall -long had four failures, two
 of which are familiar:

 1. #3758 sage -t -long devel/sage/sage/crypto/mq/sr.py
 2. #3760 sage -t -long devel/sage/sage/schemes/elliptic_curves/
 ell_finite_field.py

 Two were new to me:

 3. numerical noise (in which some dots ... seem to be ignored?) in
 devel/sage/sage/schemes/elliptic_curves/ell_rational_field.py

 File /Applications/sage-3.2.1.alpha1/devel/sage/sage/schemes/
 elliptic_curves/ell_rational_field.py, line 4071:
     sage: a = E.integral_points([P1,P2,P3], verbose=True)
 Expected:
     Using mw_basis  [(2 : 0 : 1), (3 : -4 : 1), (8 : -22 : 1)]
     e1,e2,e3:  -3.01243037259331 1.0658205476962... 1.94660982489710
     Minimal eigenvalue of height pairing matrix:  0.63792081458500...
     x-coords of points on compact component with  -3 =x= 1
     [-3, -2, -1, 0, 1]
     x-coords of points on non-compact component with  2 =x= 6
     [2, 3, 4]
     starting search of remaining points using coefficient bound  5
     x-coords of extra integral points:
     [2, 3, 4, 8, 11, 14, 21, 37, 52, 93, 342, 406, 816]
     Total number of integral points: 18
 Got:
     Using mw_basis  [(2 : 0 : 1), (3 : -4 : 1), (8 : -22 : 1)]
     e1,e2,e3:  -3.01243037259330 1.06582054769621 1.94660982489710
     Minimal eigenvalue of height pairing matrix:  0.637920814585007
     x-coords of points on compact component with  -3 =x= 1
     [-3, -2, -1, 0, 1]
     x-coords of points on non-compact component with  2 =x= 6
     [2, 3, 4]
     starting search of remaining points using coefficient bound  5
     x-coords of extra integral points:
     [2, 3, 4, 8, 11, 14, 21, 37, 52, 93, 342, 406, 816]
     Total number of integral points: 18

#4634

 4. numerical noise in devel/sage/sage/plot/plot.py, seems to be
 related to #4572, and in particular '4572-maxima-float-fixes.patch':

 File /Applications/sage-3.2.1.alpha1/devel/sage/sage/plot/plot.py,
 line 4576:
     sage: adaptive_refinement(sin, (0,0), (pi,0),
 adaptive_tolerance=0.01)
 Expected:
     [(0.125*pi, 0.38268343236508978), (0.1875*pi,
 0.7023301960218), (0.25*pi, 0.70710678118654746), (0.3125*pi,
 0.83146961230254524), (0.375*pi, 0.92387953251128674), (0.4375*pi,
 0.98078528040323043), (0.5*pi, 1.0), (0.5625*pi, 0.98078528040323043),
 (0.625*pi, 0.92387953251128674), (0.6875*pi, 0.83146961230254546),
 (0.75*pi, 0.70710678118654757), (0.8125*pi, 0.7023301960218),
 (0.875*pi, 0.38268343236508989)]
 Got:
     [(0.125*pi, 0.38268343236508978), (0.1875*pi,
 0.7023301960218), (0.25*pi, 0.70710678118654746), (0.3125*pi,
 0.83146961230254512), (0.375*pi, 0.92387953251128674), (0.4375*pi,
 0.98078528040323043), (0.5*pi, 1.0), (0.5625*pi, 0.98078528040323043),
 (0.625*pi, 0.92387953251128674), (0.6875*pi, 0.83146961230254546),
 (0.75*pi, 0.70710678118654757), (0.8125*pi, 0.7023301960218),
 (0.875*pi, 0.38268343236508984)]

#4635

   John

I can post two quick patches and if you can doctest them fast I can
wait for half an hour before doing 3.2.1.a2 which is otherwise ready
to go

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Sage 3.2.1.alpha2 released


Hello,

let's forget 3.2.1.alpha1 ever happened :)

3.2.1.alpha2 fixes the build issues from its predecessor (I did a full
build cycle before announcing here, so no need to do an alpha3 in the
next 24 hours) and adds a couple additional patches. One very
interesting patch set is #463 by William which will allow

 ./sage -upgrade foo.org/home/bar/sage-3.4.5.alpha2

in the future, i.e. you can upgrade to any install either via
webserver or even by directory on a local disk. But nothing like that
is bug free and since the infrastructure to do the in place upgrade to
other versions isn't in anything but 3.2.1.alpha2 yet the upgrade is
still a little rough - see http://trac.sagemath.org/sage_trac/ticket/4638
for details and a story on how to get from 3.2 to 3.2.1.alpha2 - it
isn't for the faint of heart. Once we have 3.2.1.alpha3 it will be
interesting to see how the upgrade from 3.2.1.alpha2 works. The
sources are in the usual place at

http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/

Please build, test and report issues as usual. This release stands a
chance to actually compile on Fedora Core 10, but we will see. No
binary for sage.math until someone fixes #4317 :)

To our American Brethren: Happy Turkey day.

Cheers,

Michael

Merged in Sage 3.2.1.alpha2:

#463: William Stein: sage -upgrade: sage -upgrade URL will install
all *newer* spkg's from the given URL, which can also be a local
directory [Reviewed by Michael Abshoff]
#4176: William Stein: matplotlib build failure due to broken tcl/tk
detection [Reviewed by Jaap Spies, Michael Abshoff]
#4613: Robert Bradshaw: doctests for big-o [Reviewed by Craig Citro]
#4624: William Stein: Sage 3.2.1.a1: add ipy_profile_sage.py to list
of files copied when sdisting [Reviewed by Michael Abshoff]
#4627: Nick Alexander: CRT_list in HNF dominates computation [Reviewed
by Craig Citro]
#4628: William Stein: sage-3.2.1.alpha1 -- setup.py build system is
foobar'd [Reviewed by Craig Citro]
#4634: Michael Abshoff: Sage 3.2.1.a1: numerical noise in sage/
schemes/ elliptic_curves/ell_rational_field.py [Reviewed by Nick
Alexander]
#4635: Michael Abshoff, John Palmieri: Sage 3.2.1.a1: numerical noise
in sage/plot/plot.py [Reviewed by Nick Alexander]


--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.alpha2 released




On Nov 27, 10:50 am, Jaap Spies [EMAIL PROTECTED] wrote:

SNIP

Hi Jaap,

 On Fedora 10, 32 bits all tests passed!

Excellent. My FC 10 live dev image refuses to boot like a coward and
dies with a kernel oops with VMWare and Virtualbox. Oh well, I guess I
will have to do a download and real install then.

 On Fedora 9, 32 bits the M2 issue with multi_polynomial_ideal.py.

Can you post the output? I assume it is just that earlier versions
of M2 return a slight different GBase in that case, i.e. the tail of
one generator is different.

 Jaap

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.alpha2 released

On Nov 27, 8:25 am, William Stein [EMAIL PROTECTED] wrote:
On Thu, Nov 27, 2008 at 1:34 AM, mabshoff [EMAIL PROTECTED] wrote:

Hello,

let's forget 3.2.1.alpha1 ever happened :)

3.2.1.alpha2 fixes the build issues from its predecessor (I did a full
build cycle before announcing here, so no need to do an alpha3 in the
next 24 hours) and adds a couple additional patches. One very
interesting patch set is #463 by William which will allow

./sage -upgrade foo.org/home/bar/sage-3.4.5.alpha2

in the future, i.e. you can upgrade to any install either via
webserver or even by directory on a local disk.

(pulling from a local disk isn't implemented yet)

My bad, I clearly needed sleep when I wrote the release notes. :)

But nothing like that
is bug free and since the infrastructure to do the in place upgrade to
other versions isn't in anything but 3.2.1.alpha2 yet the upgrade is

You can try it out with any 3.2.1.*alpha* build in pretty much any broken
or whatever state. Since you're probably going to throw away such builds
anyways, why not try this out. Just do:

./sage
-ihttp://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sa...

./sage
-upgradehttp://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sa...

The first line installs the upgraded scripts spkg, which has the new
upgrade command. The second line upgrades from Michael's tree. Note
that this may be surprisingly fast, since we no longer do sage -ba
to upgrade the core library.

Note that if you do the above you need to have a Sage with IPython
0.8.4 installed since the scripts repo contains fixes that are
dependent on its presence. Other than that give it a try and let us
know if/how it blows up. Future releases will not have that problem
since -upgrade would install all of those dependencies before the
scripts repo. It will be very cool and convenient to have once the
bugs are ironed out.

I plan to put the files required for upgrades alongside the tarball,
ie.

./sage -upgrade
http://sage.math.washington.edu/home/mabshoff/release-cycles-x.y.z/sage-x.yz.[alphaX|rcX|final]

should be the canonical place to upgrade from for my dev version
sage-x.yz.[alphaX|rcX|final]. Due to space constraints I will likely
delete those directories when x.y.z is released just like I now delete
source and binary tarballs.

On the other hand it might just not work at all -- this is a totally new
feature
and it definitely has problems:

Yep.

Cheers,

Michael

SNIP
--
William Stein
Associate Professor of Mathematics
University of Washingtonhttp://wstein.org
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Problem with Integer()




On Nov 27, 11:24 am, Jason Grout [EMAIL PROTECTED] wrote:
 Ronan Paixão wrote:
  I just found a problem with Integer(). It doesn't seem to work fine with
  float strings.
  Those work fine:
  Integer(1)
  Integer(1.)

  But this doesn't:
  Integer(1.)

 More data:

 Integer(RR('1.')) works
 Integer(RR('1.0')) works

 Integer('1.0') doesn't work

 I think that at least '1.' ought to be converted to an integer.

Seems like a reasonable request. I would even allow ($FOO.0). Care
to open a ticket?

 Jason

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Problem with Integer()




On Nov 27, 12:34 pm, William Stein [EMAIL PROTECTED] wrote:
 On Thu, Nov 27, 2008 at 12:30 PM, mabshoff [EMAIL PROTECTED] wrote:

  On Nov 27, 11:24 am, Jason Grout [EMAIL PROTECTED] wrote:
  Ronan Paixão wrote:
   I just found a problem with Integer(). It doesn't seem to work fine with
   float strings.
   Those work fine:
   Integer(1)
   Integer(1.)

   But this doesn't:
   Integer(1.)

  More data:

  Integer(RR('1.')) works
  Integer(RR('1.0')) works

  Integer('1.0') doesn't work

  I think that at least '1.' ought to be converted to an integer.

  Seems like a reasonable request. I would even allow ($FOO.0). Care
  to open a ticket?

 I strongly disagree, since pure Python does not allow this, and
 Sage's string conversion of integers should be consistent with that:

Ok, that is certainly a killer argument against this.

SNIP

But how about some functions that do convert 1.0 and 1. to an
Integer object? I have no good suggestion how to name there or where
to stick them, but it seems that they could come in useful. One could
always use regular expressions to transform the string since this is
all about getting pexepct output from Scilab to play nice with Sage.

Cheers,

Michael

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: How strong is the 100% doctest coverage policy?




On Nov 28, 7:48 am, William Stein [EMAIL PROTECTED] wrote:
 On Fri, Nov 28, 2008 at 4:49 AM, Simon King [EMAIL PROTECTED] wrote:

  Dear developers,

Hi,

  I have a couple of basic methods (such as save part of the attributes
  in some file or put some data on a to-do-list used by another
  method). I wonder if their doc strings need examples, for the
  following reasons:

  1. I think they are of internal use only, and a normal user doesn't
  even need to know about their existence. So, the user doesn't need to
  see an example for the basic method.

But developers will. And users who hit a bug can start reading and
debugging themselves.

  2. The methods are heavily used by high-level methods, so the basic
  methods are in fact tested by the doc tests of the high-level methods.
  But since they *are* tested, there is no need for a separate test of
  the basic methods.

The doctests provide examples on how to use the method and that is
invaluable. See also the next argument.

On top of that: We are usually hunting for memory problems by
valgrinding the examples. In the future we will also use muppy to look
or leaks in the python heap which are very hard to find via valgrind.
One problem right now is for example that a very high level modular
forms computation leaks. We have an idea what leaks thanks to muppy,
but buy sheer accident we then found a case where _echelonize() leaks.
That is an internal function :) - and once we run muppy over every
docstring in the Sage library we will find all such leaks. And having
*every* function including all the low level and internal stuff
provide doctest examples is *absolutely* essential here. The same
applies to the already existing -timeit doctest mode.

  3. A developer might care about the basic methods. But since the basic
  methods just comprise 5-10 lines, an example might not be needed. And
  I have comments in the code telling what the basic method does.

When one does doctesting on a new platform one often runs into strange
bugs. The more low level the doctest failure the easier it is for
someone less familiar with the code to make a precise bug report. This
is not just theoretical: On Solaris/Sparc we seem to have trouble when
passing commands to Singular using a file. The doctest failures we saw
caused by this bug are very strange and it let me to believe that
pexpect was at fault. Had we had a doctest that tested the passing
command by file this would have likely been much quicker to determine
the problem here.

  So, I tend to have the following doc-string for a basic 'export'
  method used in a high-level method 'blah'
   Of internal use only. Export data to disk. Implicit test in 'blah'

  What is the official opinion on that matter?

 I would reject any patch with functions like that which aren't
 doctested.

I would also consider this doctest policy absolute with one exception:
the deallocation of certain structures like the gray tables in m4ri
cannot be tested without segfaulting Sage. So that one gets a pass,
but there are maybe three or four such cases in all of Sage.

So all of the above leads me to believe that we must have a 100%
doctest coverage policy. As soon as we start giving out free passes
people will start to argue that their code should be exempted due to
BLAH BLAH BLAH and arguing with various people will take longer than
writing the damn doctest in the first place. Doctests are what enables
us to develop at this pace and find bugs, i.e. I consider this one a
huge advantage of Sage and the 100% policy is good for Sage. Just
imaging how many bugs and leaks will be found by doctesting for
example the padics code to 100%. That code got in since the consensus
at SD 7 was that leaving it out would have been painful, but if I were
confronted with the same problem today I would actually vote -1 on
merging that code since a year and a couple months after SD 7 when the
code was merged it is still not properly doctested.

  -- William

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.alpha2 released




On Nov 28, 2:44 pm, John Cremona [EMAIL PROTECTED] wrote:
 Built fine on 64-bit Suse linux, but devel/sage/sage/plot/plot.py
 fails:

 sage -t  devel/sage/sage/plot/plot.py
 **
 File /home/jec/sage-3.2.1.alpha2/devel/sage/sage/plot/plot.py, line
 4576:
     sage: adaptive_refinement(sin, (0,0), (pi,0),
 adaptive_tolerance=0.01)
 Expected:
     [(0.125*pi, 0.38268343236508978), (0.1875*pi,
 0.7023301960218), (0.25*pi, 0.70710678118654746), (0.3125*pi,
 0.831469612302545...), (0.375*pi, 0.92387953251128674), (0.4375*pi,
 0.98078528040323043), (0.5*pi, 1.0), (0.5625*pi, 0.98078528040323043),
 (0.625*pi, 0.92387953251128674), (0.6875*pi, 0.83146961230254546),
 (0.75*pi, 0.70710678118654757), (0.8125*pi, 0.7023301960218),
 (0.875*pi, 0.3826834323650898...)]
 Got:
     [(0.125*pi, 0.38268343236508978), (0.1875*pi,
 0.7023301960218), (0.25*pi, 0.70710678118654746), (0.3125*pi,
 0.83146961230254524), (0.375*pi, 0.92387953251128674), (0.4375*pi,
 0.98078528040323043), (0.5*pi, 1.0), (0.5625*pi, 0.98078528040323043),
 (0.625*pi, 0.92387953251128674), (0.6875*pi, 0.83146961230254535),
 (0.75*pi, 0.70710678118654757), (0.8125*pi, 0.7023301960218),
 (0.875*pi, 0.38268343236508989)]
 **

 which just looks like minor tweaking.

 John


Hi John,

I have seen two other machines with similar small numerical noise
issues and I will post a patch in a little while. But notice that due
to the plot/* refactoring present in 3.2.1.rc0 (which should be out
tongiht) the patch needs to be based on that tree, so let me or
somebody else with access to that tree do the fix.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Creation of a sage-devel-announce mailing list?


Hello folks,

from time to time various issues come up where we would like to reach
all Sage developers, i.e. all people with trac accounts and various
other people closely tied to Sage development. But not all Sage
developers read sage-devel since it can be a rather high volume
mailing list. So I would suggest we create a sage-devel-announce
mailing list with maybe a couple emails a month and probably some
discussion.

The following issue is currently hot: We need to deal with stale
tickets and we need to sort out some kinks in the review process.
Others and I have complained about the problem here and on IRC, but we
are not reaching all the people that we should. So having a separate
mailing list for the really hot button issues would be a useful thing.

Thoughts?

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Creation of a sage-devel-announce mailing list?




On Nov 28, 3:51 pm, David Joyner [EMAIL PROTECTED] wrote:

Hi David,

 No objections of course, but just out of curiousity:
 Would this be a sage-trac-announce list

That sounds like a much better name :)

or would there be non-trac issues as well?

I would assume that nearly all discussion will center around patch
status, i.e. some weekly update. So it would probably be a good idea
to restrict the subject to trac related business.

Cheers,

Michael

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: how to qualify as a ticket reviewer?




On Nov 29, 6:18 pm, Minh Nguyen [EMAIL PROTECTED] wrote:
 Hi folks,

Hi,

 I know that the subject of this post is strange/trivial (is it?) --- of
 course one can always determine who is/are the reviewers by looking
 through the relevant ticket. But I just want to know in some detail the
 criteria that are used to determine whether someone is considered a
 reviewer of a ticket. Also, I just want a record of these criteria to be
 lying around somewhere on the web. If one exists already and you have a
 link to it, please let me know.

There is no documentation about this. Generally any person
contributing to the resolution of a ticket gets credit. as an author.
Reviewer patches give a person reviewer credit, so sime times this is
a judgement call and depends on the situation, i.e. if the reviewer
call itself needs to be reviewed. I generally record this when I merge
tickets in my notes.

 If, say, Jane reviews ticket x and then gives x a positive review, then
 Jane qualifies as a reviewer of ticket x. The same thing goes for other
 folks who review and then give positive reviews to patches attached to
 x. OK, that's all fine and good. On to a more difficult example.

 Now, let say Jane reviews patch p_1 of ticket x, and then gives p_1 a
 thumb-up, then Jane is a reviewer of x. Before x is closed by the
 release manager, another patch p_2 is attached to x such that p_2 makes
 p_1 obsolete. Alice now reviews p_2 and gives this new patch a positive
 review, hence qualifying Alice as a reviewer of x. Note that p_1 is now
 obsolete and that p_2 (not p_1) should be merged into the current
 development branch. When it comes to making the reviewer list, which one
 of following should we do?

 (1) list only Alice in the reviewer list

 (2) list both Jane and Alice in the reviewer list

This case is not about reviewing issues, but credit issues since both
authors posted patches. As mentioned above I am recording all the
needed info while merging tickets.

 If this sounds a bit abstract, have a look at ticket #4534, which is a
 concrete example similar to what I've described above:

 http://trac.sagemath.org/sage_trac/ticket/4534


 Regards,
 Minh Van Nguyen

Cheers,

Michael

 Web:http://nguyenminh2.googlepages.com
 Blog:http://mvngu.wordpress.com
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: how to qualify as a ticket reviewer?




On Nov 29, 6:18 pm, Minh Nguyen [EMAIL PROTECTED] wrote:
 Hi folks,

Hi Minh,

SNIP

 Now, let say Jane reviews patch p_1 of ticket x, and then gives p_1 a
 thumb-up, then Jane is a reviewer of x. Before x is closed by the
 release manager, another patch p_2 is attached to x such that p_2 makes
 p_1 obsolete. Alice now reviews p_2 and gives this new patch a positive
 review, hence qualifying Alice as a reviewer of x. Note that p_1 is now
 obsolete and that p_2 (not p_1) should be merged into the current
 development branch. When it comes to making the reviewer list, which one
 of following should we do?

 (1) list only Alice in the reviewer list

 (2) list both Jane and Alice in the reviewer list

Sorry, my last remark was an off by one: This is the answer to this
question:

It depends. Usually if the reviewer for p_1 had a valid point (like in
the case below) and the second patch by the same person is the result
of that point the person does get credit. Even if another person
writes the followup patch the situation is the same. But if p_1 was
rubbish and the first review too and p_2 was implemented by somebody
else with another reviewer than p_1 only the author and reviewer of
p_2 would get credit. But I do not recall such a situation, so this
must be a rare occurrence.

In general my rule of thumb is to be generous with credit. And the
order of the listing for multiple authors should reflect the order of
their contributions, but that can some times be hard to judge. If
anybody feels that a given ticket has been misattributed in
HISTORY.txt and/or the release notes please let me know and I will
correct the issue and/or raise the issue with the other parties
involved.

 If this sounds a bit abstract, have a look at ticket #4534, which is a
 concrete example similar to what I've described above:

 http://trac.sagemath.org/sage_trac/ticket/4534

That ticket has two independent patches, one each reviewed by two
different people even though RobertWB's comment never was formally a
review, just a comment. Only the second patch was merged in that
particular case and only Jaap got formal reviewer credit in that case.

To get back to release notes in general: Are you planning to write
that part of the release notes since I record that info (and other
info, too) while merging patches. The individual changes for alphas
and rcs are usually pasted after the release notes, so if you wanted
to verify what has been noted I would greatly prefer it to get an
email on list pointing out potential issues. Once we get closer to a
final release someone needs to proof read my draft and potentially add
a bunch of additional boilerplate to what I have written. Another
thing that would be nice if you could handle it is the Sage Release
tour in the wiki since that can easily be done while the release is
progressing and since it is in the wiki it is trivial to do with
multiple parties at the same time.

One last thing: Can you take a look and review the various draft2 text
files #4567? In case you do please post a diff with your changes - I
really want to send the official notices out, but have been waiting
for you.

Cheers,

Michael

 --
 Regards,
 Minh Van Nguyen

 Web:http://nguyenminh2.googlepages.com
 Blog:http://mvngu.wordpress.com
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Sage 3.2.1.rc0 released


Hello folks,

here goes 3.2.1.rc0. This will hopefully be the next to last release
in the 3.2.1 cycle since we plan a final 3.2.1 source tarball in the
next 48 hours. We will very likely do an rc1 before that since some
patches I want to get in are still outstanding and the number of
merges since alpha2 is significant, so I figured it is better to cut
an extra rc than to keep merging for another 24 hours. Nothing crazy
went in that should cause any trouble, but as you know those are
famous last words.

You can try out to upgrade from alpha2 via

 ./sage -i 
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sage-3.2.1.rc0/

or download the new complete tarball at

  
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sage-3.2.1.rc0.tar

Please build, test and report issue. It would also be nice to see
reports about working and not so well working upgrades from
3.2.1.alpha2. There are still known issues with numerical noise in
plot.py - there is no ticket yet, but once I have done testing I will
open one unless somebody else beats me to it.

Cheers,

Michael

#815: Arnaud Bergeron: doctesting is broken on .sage files [Reviewed
by William Stein]
#3102: Gary Furnish: debugging output in p-adics with print mode
digits [Reviewed by William Stein, Craig Citro]
#3621: Chris Swierczewski, Brett Nakashima, William Stein:
sage.finance - add expand and refine finance.Stock [Reviewed by
William Stein, Tom Boothby]
#4057: Andrzej Giniewicz: Underlines instead of headings in notebook
version of docstring for R functions [Reviewed by William Stein]
#4266: Robert Bradshaw: overflow error in SR approx [Reviewed by
William Stein]
#4334: Jaap Spies: Updated experimental Mayavi2 spkg [Reviewed by
William Stein]
#4383: Rob Beezer: composition_series() returns no generators for
trivial subgroup [Reviewed by William Stein]
#4431: Wilfried Huss: conversion of maxima matrices to sage matrices
[Reviewed by Mike Hansen]
#4432: Wilfried Huss, Mike Hansen, Burcin Erocal: symbolic gamma and
factorial [Reviewed by Mike Hansen, Burcin Erocal]
#4433: Wilfried Huss: Replace factorial with a symbolic version
[Reviewed by Mike Hansen]
#4481: Nicolas Thiery: Fix cached_function to accept functions without
func_doc or func_name [Reviewed by Mike Hansen]
#4488: Timothy Clemans: notebook -- login page not given when logged
out and trying to view your worksheets [Reviewed by William Stein]
#4522: Burcin Erocal: polynomial interface improvements [Reviewed by
William Stein]
#4535: Mike Hansen: refactoring in plot/* [Reviewed by William Stein,
Michael Abshoff]
#4537: David Loeffler: inverse_mod for number field ideals [Reviewed
by William Stein]
#4568: Simon King: Dangerous doc test of save_session [Reviewed by
William Stein]
#4575: Wilfried Huss: Option to show nested lists as html tables
[Reviewed by William Stein]
#4587: Simon King: Installation of the latest version of a package
[Reviewed by William Stein]
#4615: Michael Abshoff: Make boehm_gc a standard spkg [Reviewed by
William Stein]
#4632: Carl Witty: .roots(ring=QQbar) fails for polynomials with
enormous (rational) coefficients [Reviewed by Nick Alexander]
#4641: Steve Klee: -notebook commandline option should take trailing
options [Reviewed by William Stein]
#4642: William Stein: Limit sage-flags.txt to vector math flags
[Reviewed by Michael Abshoff]
#4645: Michael Abshoff: in setup.py module_list.py is hidden with no
comment [Reviewed by Craig Citro]
#4647: Michael Abshoff: Disable dependency code cacheing in setup.py
for now [Reviewed by Craig Citro]


--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.rc0 released




On Nov 29, 12:28 am, mabshoff [EMAIL PROTECTED] wrote:
 Hello folks,

SNIP

 You can try out to upgrade from alpha2 via

  ./sage 
 -ihttp://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sa...

Sigh - brain fart. Obviously

 ./sage -upgrade  
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sage-3.2.1.rc0/

Sorry for the dumb mistake.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: how to qualify as a ticket reviewer?




On Nov 29, 7:37 pm, Minh Nguyen [EMAIL PROTECTED] wrote:
 Hi Michael,

Hi Minh,

 mabshoff wrote:

 [...]

  If this sounds a bit abstract, have a look at ticket #4534, which is a
  concrete example similar to what I've described above:

 http://trac.sagemath.org/sage_trac/ticket/4534

  That ticket has two independent patches, one each reviewed by two
  different people even though RobertWB's comment never was formally a
  review, just a comment. Only the second patch was merged in that
  particular case and only Jaap got formal reviewer credit in that case.

 OK, this an answer I've been waiting for. So you're saying that the
 reviewer(s) of a merged patch get credit. Is that it?

Yep, that is it in 99.5% of the cases. There are some tickets that are
messier, but those are usually a gut call.

  To get back to release notes in general: Are you planning to write
  that part of the release notes since I record that info (and other
  info, too) while merging patches.

 OK, since you're handling this as a milestone progresses, then I don't
 want to duplicate effort here.

Ok, good to know. It can't hurt to check the credits, but I don't
think this is something we have had significant problems with in the
past. I do recall maybe two or three emails about the credits in the
release notes since we do list the credit for reviews.

  The individual changes for alphas
  and rcs are usually pasted after the release notes, so if you wanted
  to verify what has been noted I would greatly prefer it to get an
  email on list pointing out potential issues. Once we get closer to a
  final release someone needs to proof read my draft and potentially add
  a bunch of additional boilerplate to what I have written.

 I assume that such a draft for each milestone is uploaded to trac, the
 draft is attached to a ticket, and that ticket is assigned to the said
 milestone. If that's the case, then I'd be more than happy to check your
 draft and add some high-level stuff if need be. But my little bit of
 concern is, how do I know when you've created such a ticket with a draft
 of your release note? For example, would the notification be via email
 to sage-devel, or some other means of notification?

Usually the final release notes are written once the sage-x.y.z
tarball has been released since we only announce once binaries have
been build and uploaded. That usually gives you and me a 24 to 48 hour
windows before the announcement goes out. It might be better if the
final tarball would already contain the latest release notes, but that
does cut it pretty close. In the end most things can be checked and
the boilerplate can be filled in once we get close to the final
planned rc, but we would have to see how that works out.

  Another
  thing that would be nice if you could handle it is the Sage Release
  tour in the wiki since that can easily be done while the release is
  progressing and since it is in the wiki it is trivial to do with
  multiple parties at the same time.

 Yes, I think I can do that, with some bugging of folks on sage-devel
 when I seem to be confused about particular tickets.

Yep, feel free to bother people since that works well :)

  One last thing: Can you take a look and review the various draft2 text
  files #4567? In case you do please post a diff with your changes - I
  really want to send the official notices out, but have been waiting
  for you.

 Sorry about my lateness in replying to this issue. (I have a full-time
 job this 2008/2009 Australian summer :-)

Most of us have to work for a living, so don't worry about it. I was
just curious since you seemed to have dropped from the net for a
couple days after being enthusiastic.

 I'm doing some basic checking
 right now. I'll upload a diff to #4567 within one hour from this post.

Thanks. I believe the greatest impact will be if the Release Tour is
nice and polished. The HISTORY.txt cleanup project is also something
worth doing and that one has the advantage that it is not time
critical.

In general if anybody else wants to help out that person would be more
than welcome since there is more than enough work to go around for
everybody. So don't hesitate to pipe up, even if you have only little
free time to contribute. Every bit is deeply appreciated and in the
end it is great fun :)

 --
 Regards,
 Minh Van Nguyen

Cheers,

Michael

 Web:http://nguyenminh2.googlepages.com
 Blog:http://mvngu.wordpress.com
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.1.3, 3.1.4 and 3.2 release notes and Sage release tour




On Nov 29, 1:28 am, Minh Nguyen [EMAIL PROTECTED] wrote:
 On Tue, Nov 25, 2008 at 10:04 PM, mabshoff [EMAIL PROTECTED] wrote:

SNIP

  Exactly. It would be very nice if the release tours were consistent in
  style, had plenty of examples and so on. I have always liked the Magma
  release notes since they gave you a very good idea what had happened
  in the 2.14.x to 2.14.x+1 release.

 So, for example, can you please provide me with such a release note
 for a Magma version? I don't have Magma and I've never seen a release
 note for a Magma version. In case you're unable to provide such a
 note, can you please describe what you like about those notes?

They used to be online on one large text page at the Magma website,
but now they have been reformatted into html and split up into
individual pages. See

http://magma.maths.usyd.edu.au/magma/htmlhelp/rel/rel.htm

and

http://magma.maths.usyd.edu.au/magma/ReleaseNotes/ReleaseNotes.html

I need to poke around - maybe I will find something still in pure test
form.

  That
 is, let's take the release note for sage-3.2 as a bare minimum. What
 other good things do you want to add to newer Sage release notes?

Well, a better introduction what Sage is could be more useful. I would
have a loot at the various software announcements at lwn.net and then
pick one where you instantly would be curious because that maybe half
page blurb just explained very well what $FOO is all about. What we
currently have is such an attempt, but I am sure it can be improved

 --
 Regards
 Minh Van Nguyen

Cheers,

Michael

 Web:http://nguyenminh2.googlepages.com
 Blog:http://mvngu.wordpress.com
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Final Sage 3.2.1 prerelease is coming up


Hello folks,

the time frame to get patches into 3.2.1 is nearing its end with a
planned release in 48 hours. Anything going into 3.2.1 at this point
should be well debugged and tested and be critical or blockers. Any
other tickets should automatically get assigned to the next milestone.
This release is about half a week earlier than initially planned since
alpha2 seemed much more stable and with fewer problems than
anticipated. Since the release cycle of about once a month for the
last three months has been too long we have been more aggressive of
pushing for quicker releases and want to hit 7 to 10 days for bug fix
and about 12 to 18 for major releases. Obviously such a release cycle
will vary due to unforeseen issues. After all: This is software
development and not engineering :)

Unlike the initial plan from two weeks ago we will shove in an
additional stable release, aka 3.2.2, but it should also be on the
short side. This is meant to merge patches from trac and also to get
as much of the sage-combinat code that is ready in before the big 3.3.
ReST conversion. So if you have code sitting around please try to get
it polished and into 3.2.2. There will be tools for the ReST
transition, so if you miss the merge window before 3.3 it won't be too
bad.

Thoughts?

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.rc0 released




On Nov 29, 4:33 am, Jaap Spies [EMAIL PROTECTED] wrote:

Hi Jaap,

 On Fedora 9, 32 bits upgrade went fine, but:

 [EMAIL PROTECTED] sage-3.2.1.alpha2]$ ./sage
 --
 | Sage Version 3.2.1.rc0, Release Date: 2008-11-29                   |
 | Type notebook() for the GUI, and license() for information.        |
 --

 **
 WARNING!  This Sage install was built on a machine that supports
 instructions that are not available on this computer.  Sage will
 likely fail with ILLEGAL INSTRUCTION errors! The following processor
 flags were on the build machine but are not on this computer:

 pebs pge clflush vme tsc xtpr constant_tsc pat bts lm msr fpu fxsr tm pae 
 acpi cx8 mce de mca pse est ht apic monitor cid ss ds_cpl pbe cx16 pse36 mtrr 
 dts

 Emailhttp://groups.google.com/group/sage-supportfor help.
 **

 sage:

 but /proc/cpuinfo says otherwise!

This is due to #4642 since we now only track relevant flags now.
Delete $SAGE_ROOT/local/lib/sage-flags.txt and the problem goes away.

 --
 The following tests failed:

         sage -t  devel/sage/sage/rings/polynomial/multi_polynomial_ideal.py
         sage -t  devel/sage/sage/misc/functional.py
 Total time for all tests: 5563.9 seconds
 Please see /home/jaap/downloads/sage-3.2.1.alpha2/tmp/test.log for the 
 complete log from this test.
 [EMAIL PROTECTED] sage-3.2.1.alpha2]$

 The first is a known issue, but the second:

 sage -t  devel/sage/sage/misc/functional.py               
 **
 File 
 /home/jaap/work/downloads/sage-3.2.1.alpha2/devel/sage/sage/misc/functiona 
 l.py, line 891:

SNIP

 some missing \mbox.

*Very* strange. This was introduced by #4575. Mike Hansen just raised
some design issues with that patch in general, so we might just revert
it depending on the discussion that will hopefully happen here soon.

 Jaap

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.rc0 released




On Nov 29, 7:19 am, John Cremona [EMAIL PROTECTED] wrote:

SNIP

 On a 64-bit Suse I ha dthe plot.py failure which is known.  No problem
 with the builds.

 John

Hi John,

can you open a ticket for the plot.py failure with the exact failure
from rc0?

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: question about integer.pyx




On Nov 29, 10:42 am, Robert Bradshaw [EMAIL PROTECTED]
wrote:
 On Nov 29, 2008, at 9:42 AM, John H Palmieri wrote:

SNIP

  What goes wrong if we delete it?  I mean, I deleted it and ran 'sage -
  b' then 'sage -testall' (since I had a new distribution to test
  anyway), and it ran without any failures.

 Sorry, I was thinking you were referring to the .pxd file. Deleting  
 it from the .pyx file should be fine.

 - Robert

John,

can you open a ticket and post a patch? This is trivial enough to make
it into 3.2.1.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.rc0 released




On Nov 29, 10:35 am, John Cremona [EMAIL PROTECTED] wrote:

Hi John,

 It is now at #4655.


Thanks, I should post a patch shortly.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.rc0 released




On Nov 29, 10:19 am, mabshoff [EMAIL PROTECTED] wrote:

Hi,

  sage -t  devel/sage/sage/misc/functional.py               
  **
  File 
  /home/jaap/work/downloads/sage-3.2.1.alpha2/devel/sage/sage/misc/functiona 
  l.py, line 891:

 SNIP

  some missing \mbox.

 *Very* strange. This was introduced by #4575. Mike Hansen just raised
 some design issues with that patch in general, so we might just revert
 it depending on the discussion that will hopefully happen here soon.

Jaap, John or anybody else who can reproduce this failure: can you see
if Mike Hansen's patch at #4575 fixes the issue for you? I don't think
it will and I cannot understand how something that should be
completely independent of pointer size like the LaTeX representation
could change. If this patch doesn't resolve this someone needs to
start poking around ...


Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.rc0 released




On Nov 29, 1:55 pm, John Cremona [EMAIL PROTECTED] wrote:
 2008/11/29 Jaap Spies [EMAIL PROTECTED]:



  Jaap Spies wrote:

  I'll apply #4575 and see.

  Mike's take-two patch failed to apply

 Same here.

 John

Mike will rebase the patch in a little while. Also note that once the
patch is applied you have to doctest sage/misc/html.py also since the
code moved there.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: FLINT 1.0.17 released



On Nov 29, 4:03 pm, Bill Hart [EMAIL PROTECTED] wrote:

Hi Bill,

 I have just released a new bug fix for FLINT, available 
 athttp://www.flintlib.org/

 This fixes the following issues:

 * A segfault in the division and pseudo division functions

 * The bound that was being used in fmpz_poly_gcd_modular was as far as
 I know, not proven. I have replaced it with a proven bound and cited
 the relevant paper. This makes little difference to the timings.

 * A bug in the profiling code for fmpz_poly related to the top bit of
 n bit random coefficients always being set has been fixed.

 * I identified an issue that might potentially have caused wrong
 results in polynomial multiplication. However I checked that in fact,
 it cannot be triggered in FLINT 1.0.17 code (I also ran specifically
 constructed tests to verify that this is in fact the case). The code
 will be completely rewritten for FLINT 1.1.

 I recommend Sage upgrade to FLINT 1.0.17 as the first bug is critical
 and can occur in live code (I actually hit it myself).

Ok, Burcin did an updated spkg for FLINT 1.0.16, but it should be
trivial for him to upgrade it to 1.0.17. It will miss the 3.2.1 merge
window, but a quick 3.2.2 is right on its tail.

 FLINT 1.0.17 will likely be the last 1.0.x series release before FLINT
 1.1 which should be available for use in Sage in the next few weeks.
 The interface for FLINT 1.1 should be pretty much the same as for
 FLINT 1.0.x, however there will be a large quantity of new functions
 and a large number of substantial speedups which Sage will be able to
 take advantage of.

 I intend to issue beta/release candidates in about 11 days. The
 todo.txt file in FLINT 1.0.17 lists the tasks which need to be
 completed before the release.

 Over the next few days I will be working on code which will appear in
 FLINT 2.0, specifically a matrix module F_mpz_mat over the new F_mpz
 integer library I have coded up for FLINT 2.0 and an F_mpz
 implementation of fpLLL's fast module.

 I am about a third of the way through implementation of F_mpz_poly for
 FLINT 2.0. It features a completely rewritten polynomial module over
 the new FLINT integer format F_mpz and David Harvey's KS2 algorithm,
 which gives *up to* a 30% increase in speed for polynomial
 multiplication for lengths between about 45 and 9000.

Nice, *really* looking forward to this :)

 Bill.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: SageAndLinux




On Nov 30, 1:59 am, Harald Schilly [EMAIL PROTECTED] wrote:
 On Nov 30, 12:38 am, William Stein [EMAIL PROTECTED] wrote:

  We could make a modified version of AndLinux and rebrand it say
  SageLinux, which would
  be the above but with Sage preinstalled, and maybe a slightly larger drive.

 For me, this sounds good and seems to be a better solution than the
 vmware image. One big point is accessing sage notebook files, i hope
 that's easier.
 There should also be a dedicated start button in the andLinux menu and
 perhaps even a regular start menu entry (if it is possible to start
 something inside andlinux from the outside).Then, packaging this as an
 MSI package would be very attractive, too.

Yep, that would be nice.

  Note, I don't think you can do any of this on a 64-bit windows box.

 Im not so familiar with all the windows details, but isn't it possible
 to modify the startup conditions for programs? run as or something.
 Or has this no effect for 32 vs. 64?

I think the issue here is that with a 64 bit kernel you need 100% 64
kit drivers and since coLinux provides drivers that are (were?) 32
bits only it won't work. RunAs has nothing to do with that.

 harald

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Final Sage 3.2.1.rc1 bug fixing effort today


Hello folks,

over the next couple hours we hope to fix and merge all nine
outstanding issues for 3.2.1 - see

http://trac.sagemath.org/sage_trac/query?status=newstatus=assignedstatus=reopenedmilestone=sage-3.2.1order=priority

So feel free to pop into IRC and help out if you have some time. We
ended up merging some larger patches than I had planned, but all of
them are low risk (famous last works) and would have bit rotted
quickly.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: name space pollution


SNIP

 I really like

   sage: finance.[tab]

 I don't like explicitly forcing people to import stuff before they can use it
 at all.  Thus I much prefer

 $ sage
 
 sage: finance.[tab]

 and I don't like

 $ sage
 ...
 sage: import sage.finance as finance
 sage: finace.[tab]

 I do like various domains with lots of functions to have their
 functionality gathered together under
 a namespace.     That said, I'm not for some massive reorganization of
 the current global namespace, since that wold break a huge amount of
 existing code -- both in Sage and out (e.g., the examples at
 wiki.sagemath.org/interact).

 And it's not the end of the world that len(globals()) is large.  It's
 only a problem to me when there are specific reasons it is a problem.

    -- William

Ok, that is pretty much what I wanted to express, i.e. having most
things of a given subsystem gathered under $SUBSYSTEM.[tab]. I did not
mean that one would have to import things, so my use of global
namespace was not in the pythonic way.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Request for additions to the Sage 3.2.1 Release Tour


Hello folks,

3.2.1 is about done (rc1 should be announced officially in about 2
hours once it passes my build testing and a full test run, but it is
in the usual place if you want to get going with it now). My main
request is for people to add items to the Sage Release tour at
http://wiki.sagemath.org/sage-3.2.1

We have not been doing the best possible job there and actually need
to do some fixing for earlier releases where only some rudimentary
documentation exists. The Sage Release tour is meant for people not so
tightly connected to the development group to gather what are the
major new features in Sage. It can also be used very well to showcase
one's contribution to Sage [hint hint :)]. I think that for example
malb has done a spectacular job documenting some of his contributions
to Sage by providing a little blurb and then some code examples that
demonstrate the new functionality for many of the features he added/
was part of the team implementing them.

In the long term I hope that we can take the data from the Sage
Release tour wiki pages and integrate it into the new ReST
documentation by extracting the info in some automated fashion from
the wiki so that even offline we will have a very nice overview of
what has been happening in Sage development. If anybody wants to help
pitch in here please let me know so I can direct you to various
construction sites in the Sage documentation :)

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Christmas once again ...




On Dec 1, 2:47 am, David Joyner [EMAIL PROTECTED] wrote:
 That p-adic one is actually my design! Here is another 
 one:http://www.usna.edu/Users/math/wdj/greeting.jpg
 It's a Barnsley fractal I programmed in C long ago, though I've lost the code.
 I'll try to recreate it in Sage.

 On Mon, Dec 1, 2008 at 4:56 AM, Harald Schilly [EMAIL PROTECTED] wrote:

  Fromhttp://www.walkingrandomly.com/?p=395featuring some Sage code
  for a card, and a mathematica snowflake, ...

  
  You[r] task is to design a Christmas message with a mathematical theme
  using any mathematical system or programming language of your choice.
  Your design must be generated algorithmically (so you can't design it
  in Photoshop and import it into Mathematica for example) and it must
  include source code.  Ideally, you should include a quick explanation
  of the mathematics you featured in your design.
  

Very nice. We should definitely encourage people to participate and
get them to donate their Sage code to expand the gallery we have for
Sage :)

  greetings Harald

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Sage 3.2.1.rc1 released


Hello folks,

it took a couple hours longer than planned, but here goes 3.2.1.rc1.
The changes merged went a little deeper than planned, i.e. the two
biggest changes are massive improvements to the Magma interface by
William and the overhaul of module_list.py by Craig. The changes by
Craig will force you to rebase any patch adding extensions, but not
the file is prettied up and most importantly there aren't any
duplicates any more. In 3.2.2 we will also merge code written by Craig
that allows building of the Sage library extensions in parallel, so it
was well worth it. Other than that the usual assortment of bug fixes,
among them some long awaited fixes for make install. We also fixed a
bug that prevented binaries on sage.math to work properly (see #4317
for the gory details), so form now on I will roll binaries for
sage.math again.

As usual sources and the sage.math-only binary can be found in

   http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/

You can also upgrade 3.2.1.alpha2 or higher via

  sage -upgrade 
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sage-3.2.1.rc1/

What is left for 3.2.1.final is to potentially fix the exponentiation
leak [which is likely 99.9% coercion related :)], but since 3.2.2 will
be also a rather short release cycle we will release without such a
fix.

Please build, test and report any issues. The official 3.2.1 sources
should be out in 24 hours unless something goes very wrong and be
followed in about another day or two by binaries.

Cheers,

Michael

Merged in Sage 3.2.1.rc1:

#3122: Michael Abshoff: after make install, sage tries to write in /
usr/local [Reviewed by William Stein]
#4254: Martin Albrecht: mq.SR improvements for convenience [Reviewed
by William Stein]
#4261: Willem Jan Palenstijn: sympow Configure fails to handle aliases
[Reviewed by William Stein, Mark Watkins, Michael Abshoff]
#4308: Philippe Theveny: make mpc an optional spkg [Reviewed by
William Stein, Michael Abshoff]
#4317: William Stein: Fix easy-install.pth after moving Sage [Reviewed
by Michael Abshoff, Craig Citro]
#4321: Alexander Dreyer, Michael Abshoff: wrong Unix permissions in
some PolyBoRi files
#4352: Marshall Hampton: add support for weight vectors to gran/
groebner_fan [Reviewed by William Stein]
#4402: William Stein: Sage 3.1.4: magma related optional doctest
failure in tut.tex [Reviewed by Michael Abshoff]
#4412: John Cremona: extend the local information function for
elliptic curves over number fields [Reviewed by William Stein, Minh
Nguyen]
#4576: Marshall Hampton: biopython optional package upgrade to
1.49beta [Reviewed by William Stein]
#4582: Guillaume Moroz: use Singular's capabilities for computing over
fraction fields [Reviewed by Martin Albrecht]
#4619: Michael Abshoff: Sage 3.2.1.a1: Update HISTORY.txt with the
3.1.3, 3.1.4 and 3.2 release notes [Reviewed by William Stein]
#4654: John Palmieri: for 'sage -testall': put sage version in test
log [Reviewed by Michael Abshoff]
#4655: William Stein: doctest failure in plot.py with 3.2.1.rc0 on 64-
bit SuSe linux [Reviewed by Michael Abshoff]
#4657: Michael Abshoff: OSX: gnuplot doesn't start due to dreaded
libpng conflict [Reviewed by William Stein]
#4658: William Stein: magma -- get rid of redundant caching: just have
_magma_init_ [Reviewed by Michael Abshoff]
#4659: John Palmieri: remove an extra 'cdef class Integer' line from
integer.pyx [Reviewed by Robert Bradshaw]
#4660: William Stein: mark inline fortran and inline cython examples
optional [Reviewed by Michael Abshoff]
#4661: Craig Citro: clean up module_list.py [Reviewed by Michael
Abshoff]
#4664: Michael Abshoff: Sage 3.2.1.rc1: Fix documentation build issues
[Reviewed by Craig Citro]
#4668: Michael Abshoff: libSingular's header have too tight
permissions [Reviewed by Craig Citro]


--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.rc1 released




On Dec 1, 6:53 am, mhampton [EMAIL PROTECTED] wrote:
 All tests passed on an upgrade from rc0, on an intel mac (10.5).

 Three cheers for the more flexible upgrade option!

 -M. Hampton

Yeah, for me it is the killer feature of 3.2.1 - no disrespect to all
the other great features :)

But for testing Sage rc releases on about a dozen boxes it is very
convenient, especially once we have to push out two or three fixes at
the very end of a release cycle and building from scratch does take a
while. As mentioned earlier 3.2.2 will have experimental build Sage
library extensions in parallel, so just like parallel doctesting and
recently parallel cythonization and now dev-upgrades it is a feature
that once I use it I cannot understand how I ever did development work
without it.

Now all we need is an idiot proof way to pull all dev repos from my
merge tree to a remove install and upgrade, but that isn't too hard
either technically, someone just has to do it.

Cheers,

Michael
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-devel?hl=en
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.rc1 released




On Dec 1, 7:27 am, Jaap Spies [EMAIL PROTECTED] wrote:
 mabshoff wrote:

SNIP

 Upgrade from rc0 on Fedora 9 has the known issues in
 sage/rings/polynomial/multi_polynomial_ideal.py

 Jaap

Hi Jaap,

can you repost the output? I made another one of those GBasis over ZZ
computations optional for now since I observed different results on
various boxen.

Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

[sage-devel] Re: Sage 3.2.1.rc1 released