On Feb 21, 6:20 pm, "Georg S. Weber" <georgswe...@googlemail.com> wrote: > Hi all, > > I finally could verify that the patch at trac 12161 is good, i.e. > heals not only the original problem for OS X 10.7, but the > "_PyUnicodeUCS4_AsUTF8String" incarnation, too (at least on one of my > own OS X 10.6 installations --- try starting a Sage "app" after > (closing all Sage and all terminal sessions, and) nuking/ > removing .sage, *and* do so on a system that boots up in 64bit mode, > i.e. by pressing "6" and "4" during startup --- but maybe the computer > just has to be "young enough" so that the OS X 10.6/10.7 installs > something different than on "older" ones, which would be 64bit > capable, but Apple does boot them only in 32bit mode; > seehttp://support.apple.com/kb/HT3773and http://support.apple.com/kb/HT3770). > > Anyway, would it make sense now to upload some official update of the > OS X 10.6 app (with only the trac 12161 patch as delta to the original > one currently in the download area)?
Unless 5.0 is coming within a week (and given the status of http://trac.sagemath.org/sage_trac/ticket/12024 and http://trac.sagemath.org/sage_trac/ticket/11881, that seems highly unlikely), I think this is a VERY good idea. As I've said before, my own laptop has something weird with a missing libtiff or something, so I am reluctant to do it, but hopefully anyone else could? Or the buildbot? And if someone can make Sage 4.8 binaries for Intel 10.4 and 10.5, that would be even better :) -- 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
