Snow Leopard Issues

September 10, 2009 python, Uncategorized

For some reason, I upgraded to Snow Leopard at my first opportunity. To tell the truth, the end-user improvements are pretty modest and it is difficult to perceive Snow Leopard’s slight speed improvements. That is not to say that the upgrade did not have impact. Some software that I regularly use stopped working. I am all up and working now and here is now.

Problem Solution
Oxygen 9.3 stopped working I upgraded to Oxygen 10.3 for $147
My macport MySQL, Apache, PHP setup broke I tried to do port upgrade of MySQL and PHP and it failed. Compiling my own PHP didn’t work either. I wound up installing the MySQL package from the MySQL site and using the Apache and PHP (5.3) that comes with Snow Leopard.
My eZ Publish development environment broke This was because I upgraded to PHP 5.3. This was easily fixed by re-installing eZ Publish because eZ Publish is compatible with PHP 5.3
My Drupal development environment broke Drupal is not compatible with PHP 5.3. Until it is, I am running it on MAMP.
Python MySQL did not easy_install for Python 2.6 This is the problem that I struggled most with. I followed the instructions here. The compile and build worked but I could not import the library. I finally solved the problem by re-installing the 32 bit version of MySQL, setting Python to run in 32 bit, and following these simple instructions.
1Password 2.x is incompatible with Snow Leopard I pre-purchased version 3 and enrolled in the 3.0 beta program. The UI looks really slick and I am happy that I upgraded.
Cornerstone is incompatible with Snow Leopard I am waiting for the next release of Cornerstone (due this month) that will be Snow Leopard compatible and also support Subversion 1.6.

Looking back, it would have made more sense to wait on the upgrade and see what other people on the mailing lists said about their experiences. But, since I figure I would share what I learned.

  • James Scrimshire

    Interesting.. I was just about to purchase the upgrade, I may leave it until xmas now though, I can’t have it buggering up my flex/mysql/jboss and drupal environements..

  • http://ecmarchitect.com Jeff Potts

    Seth,

    You made me nervous but I upgraded anyway. I was most concerned about my MacPorts install, PHP, and Drupal. After the upgrade, installing XCode, and installing the latest MacPorts binary, everything is a-okay. PHP 5.2.9 still works, Drupal still works, MySQL still works, apache still works. Either I got lucky or we’ve got something different in our setup that worked out in my favor.

    Best of all, and worth the risk of hosing my MacPorts apps, I’ve kicked Entourage to the curb and I can now see my Exchange mail/calendar and my Google mail/calendar in the same mail/calendar client. Sweet.

    Jeff

    • http://www.contenthere.net seth

      Did you try a “port upgrade installed”? I think that is what hosed me. Exchange support may be the biggest new feature in Snow Leopard but it doesn’t help me that much.

  • Jon Keane

    So I found your post on another blog explaining how to get 64 bit mysql to work with 64 bit python using MySQLdb built as a 64 bit. I ran into the same problem as you after what seemed like a successful build:

    >>> import MySQLdb
    Traceback (most recent call last):
    File “”, line 1, in
    File “build/bdist.macosx-10.6-universal/egg/MySQLdb/__init__.py”, line 19, in
    File “build/bdist.macosx-10.6-universal/egg/_mysql.py”, line 7, in
    File “build/bdist.macosx-10.6-universal/egg/_mysql.py”, line 6, in __bootstrap__
    ImportError: dynamic module does not define init function (init_mysql)

    After a lot of googleing I finally found the problem: python setup.py clean will not actually clean the build/ directory if you’ve built without the proper architecture flags. In order to do this delete everything in the build/ directory with rm * or the like, and then build with the instructions above and everything will work out. cf http://www.mangoorange.com/2008/08/01/installing-python-mysqldb-122-on-mac-os-x/?cp=all comment 10.

    Just thought I would let you know, even though you seemed to have solved your problem by downgrading everything to 32bit.

    • http://www.contenthere.net seth

      Great information. Thanks Jon!

  • http://www.contenthere.net seth

    Done

  • rda

    Oxygen… I was using 10.0 and it worked fine with Leopard
    I didn’t need to upgrade anything, so I downloaded their newest build (Oxygen 10.3) and copied one file from the new version to the old one.

    The file is jide.jar, in the lib folder. It’s apparently a 3rd party component that Oxygen uses