Hi, On 1 fév, 14:01, Minh Nguyen <nguyenmi...@gmail.com> wrote: > Hi, > > On Tue, Feb 2, 2010 at 5:29 AM, jplab <jeanphilippela...@gmail.com> wrote: > > <SNIP> > > > My computation are considerably slowed down by this bug and I would be > > very happy to find a solution! Help! If you need more info, let me > > know! > > My best guess is that mixing Sage 4.3 and 4.3.1 with Mac OS X 10.5 and > 10.6 can be problematic. As you know, Sage versions prior to 4.3.1 > were unstable on Mac OS X 10.6 due to how Python was compiled on that > platform. As of Sage 4.3.1, Python is now configured to properly > compile on Mac OS X 10.6, which got rid of the annoying bug tracked at > ticket #7095 [1]. One solution would be to use Sage 4.3.1 for all your > Mac OS X 10.6 machines, or indeed for all your Mac OS X machines. Hope > that helps.
Good, we will try that by changing the image on all the Mac... But what is annoying is that on the intel server with 10.5 and sage 4.3, it does work! But I hope 10.6 & sage4.3.1 will solve the problem! > > [1]http://trac.sagemath.org/sage_trac/ticket/7095 > > -- > Regards > Minh Van Nguyen Thanks! I will keep you posted on that. JP Labbé -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
