Ed - Sorry to hear about your troubles with MacPorts; glad to hear
that you got them working, one way or the other.
On Dec 20, 2007, at 1:57 PM, Ed Criscuolo wrote:
For the time being, I got things to work by copying the packages
to python2.4/site-packages, and linking /usr/bin/pythonw to
I think the issue was a change to python24 on August 21 (2007):
removed the non-versioned binaries called “python” and “pythonw”.
IIRC, I went in and make symlinks to them in /opt/local/bin, which
did the trick. The reason why some py-XXX modules were being
installed in the 2.3 directory and some in 2.4 is that some modules
invoke (incorrectly) “python setup.py” - which would result in a 2.3
directory since “python” would be the Apple-provided one -, while
others (correctly) “/opt/local/bin/pythonX.Y setup.py” - which would
result in the 2.4 (or whatever version of Python is installed by
MacPorts in that directory). I know that the MacPorts folks are
transitioning to the explicit calling method, but I’m sure that there
are ports out there that do not yet use it.
The -best- solution would be to remove those site-packages that you
copied from 2.3 to 2.4, then, with the “python -V” returning “2.4”
correctly, have MacPorts uninstall those packages, then reinstall
them. They should appear in the 2.4 site-packages area.
a position across buffer modifications.
You can apply tags and insert marks without invalidating your
but any mutation that affects ‘indexable’ buffer contents (contents
that can be referred to by character offset)
will invalidate all outstanding iterators
THis might be caused by the copying of 2.3 site-packages to 2.4, but
who knows. Try reinstalling those packages correctly, then re-run
GRC to see if it works better. If not, then it’s best that Josh look
into this. - MLD