Great, glad to see this!  Thanks for the updated spkg.

On Jul 26, 9:47 pm, Marshall Hampton <hampto...@gmail.com> wrote:
> Ok, I posted my spkg at:
>
> http://trac.sagemath.org/sage_trac/ticket/6634
>
> It would be great if you (tkeller) got a trac account, since currently
> I don't know any other sage developers who have any real interest in
> this (partial exception of William Stein but clearly he has a lot on
> his plate).
>
> -Marshall
>
> On Jul 26, 12:25 pm, Marshall Hampton <hampto...@gmail.com> wrote:
>
> > Hi,
>
> > Thanks for pointing that out.  I have made a 1.51b spkg, but decided
> > to wait a week or two for the final 1.51 to come out.  But I didn't
> > realize that the 1.49b install was broken.
>
> > Anyway if you have any interest in helping out, you should get a trac
> > account.  Just email William Stein for one.
>
> > I am excited about their cleanup too, I think with a little more work
> > biopython can be made a standard part of sage, but that will require a
> > developer vote.
>
> > -Marshall Hampton
>
> > On Jul 26, 12:05 pm, tkeller <thomas.e.kel...@gmail.com> wrote:
>
> > > Thanks for all the recent work upgrading the base python distribution
> > > to 2.6, I imagine it was quite a task. I noticed that installing the
> > > biopython-1.49b spkg is broken from the upgrade . I have upgraded the
> > > spkg to 1.51b and it installs and works fine on my sage-4.1
> > > installation. Is there a place to upload supplemental spkg's , or
> > > should I get a trac account?
>
> > > A side benefit to upgrading the spkg is that the last few patches
> > > finally removed the mxText dependency, so it is now a clean install
> > > aside from requiring Numpy.
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to