Nehemiah Dacres wrote:
> so we're still not supporting Apple's shipped python?
Well, Apple does what Apples does. Every single version of python that
they have shipped as had at least one bug (or misfeature), and they have
never provided an update within an OS-X version. (For example, if
nothin
On 19 Dec, 2007, at 7:05, Jamie Quint wrote:
> I am attempting to install PIL on Leopard from source, it all
> appears to be working, the build summary gives an all ok (see below)
The build process is a bit to lenient to my taste, it will automaticly
detect which C libraries are available an
Nehemiah Dacres wrote:
> perhaps you should send this to macports.
Or forget macports, install the 2.5 macpython Universal framework build
and as many of the packages you need that you can find on:
http://pythonmac.org/packages/py25-fat/index.html
Then try to build/install the rest of the on
I've noticed strange behavior with PythonLauncher on Leopard (I'm using
the standard build of MacPython 2.5.1).The expected behavior with
PythonLauncher is that when I double-click on a Python script, a
Terminal window will launch and cd to the script's working directory,
and then Python wi
perhaps you should send this to macports. you see, Mac Ports normally
installs stuff in /opt/local/bin. but that is not where this code is being
ran from according to your traceback.
"Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/django/db/backends/postgresql_psycopg2
