Jason Grout wrote: > William Stein wrote: >> On Thu, Oct 8, 2009 at 5:41 PM, Jason Grout <jason-s...@creativetrax.com> >> wrote: >>> Mike Hansen wrote: >>> >>> However, >>>> there are plenty of ones that we don't have a fix for -- see #7095. I >>>> think there are a couple threads on sage-devel about this. >>> Should we be holding up 4.1.2 for issues that (according to what you >>> say) don't have any solution, when the issue in question is supporting a >>> new platform (at least, a new release) that admittedly breaks lots of >>> software out there? Or should we release 4.1.2, declare OSX 10.6 not >>> supported for this release, and then follow up with 4.2 when we have >>> fixes for 10.6? >>> >> Jason, to move your suggestion forward, please referee this patch: >> >> http://trac.sagemath.org/sage_trac/ticket/7193
Looking at the patch, shouldn't we use the python platform module to test for platform identity? http://docs.python.org/library/platform.html In particular, this lets us test for 10.6 specifically: >>> platform.mac_ver() ('10.6.1', ('', '', ''), 'i386') We can just print a warning out when the person is running 10.6. On the other hand, it might be nice to warn someone that plans on upgrading that Sage will not work (for now) if they upgrade to 10.6. Should the warning be printed out for all OSX users, or just for people running on 10.6? Thanks, Jason -- Jason Grout --~--~---------~--~----~------------~-------~--~----~ 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 URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
