> I got swamped by teaching, SAGE Days 4, SIMUW, and... buying a house
> this week (!), so I haven't been able to move anything forward.
> Fortunately, I have no formal responsibilities for the next two
> months, so a lot is likely to happen in the near future.

Nice!

> My plan is to start working on Friday very hard on making a release of
> SAGE-2.7.  I anticipate this will take less than 2 days.
>
> SAGE-2.7 will include scipy as a *standard* package (and will require
> gfortran as a dependency on linux, and install gfortran on os x).
> In order to get this release out in a timely fashion, my plan is to
> use the existing spkg's, i.e., not switch to the versions that
> Didier created, since that would add a lot of extra time,
> and delay a much-needed release that is basically ready to go.
> Then as soon as SAGE-2.7 is released, the next goal will be to
> make another release, e.g.,  SAGE-2.7.1, where the main
> change will be moving to the new package structure.  In summary:
>
>    1. Monday, July 16: Release SAGE-2.7
>
>    2. Friday, July 20: Release SAGE-2.7.1, which is SAGE-2.7.1, but
>       with the package system reworked, and the build issues with
>       lots of people installing scipy that will undoubtedly arise
>       mostly fixed.
>
> What do you think?

The timing will work out fine.  We will begin getting all of our
packages into the new format and put them on sage.math.  Once you have
the packages system reworked, we can't think about merging our spkgs
with yours.  Unfortunately I am leaving on a 2 week trip/vacation (up
to the San Juans) starting the 21st, so the merging might not be able
to take place until early August.  But all of our spkgs should be on
sage.math in the new format before then.

Brian

> The src subdirectory here:
>
>    http://modular.math.washington.edu/home/was/sage2.7/
>
> has the latest version of my versions of packages.   Most of the
> new work in SAGE-2.7 involves the fortran package, the scipy package,
> the lapack package, and changes to the standard SAGE Python
> library code.   On many test systems it all does build and work together
> now.  It doesn't work on powerpc OS X, but we've figured out how
> to fix that.
>
>  -- William
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to