On Tue, Aug 25, 2009 at 10:54 AM, Tim Lahey<tim.la...@gmail.com> wrote: > > > On Aug 25, 2009, at 1:46 PM, William Stein wrote: >> >> I'm fine with switching to the framework build for Sage if it "just >> works". What are the drawbacks? When I think about the drawbacks now >> the only thing I can think of is "Michael Abshoff didn't want to >> switch to it". But I can't think of anything else. >> >> Sage originally wasn't a framework build on OS X, since when I ported >> Sage to OS X in the first place, I had never heard of framework >> builds. I think that not being a framework build is mainly just >> inertia from that. >> > > One of the nice things about Framework builds is that they're nice and > contained. Everything is in one directory, much like Sage. So, all the > python details would be contained in there. Plus, they support > versioning.
In that case, I love Frameworks! > Framework builds are required for any non-X11 GUI work on OS X with > python. So, if we want to support those python add-ons, we need a > framework build. > > The only problem I can possibly see is a conflict with the system python > Framework if it is a "python" framework versus a Sage framework. > > Cheers, > > Tim. > --- > Tim Lahey > PhD Candidate, Systems Design Engineering > University of Waterloo > http://www.linkedin.com/in/timlahey > > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
