It would help people trying to use rt if you could detect these kind
of problems and report an error about what they need to do to run rt
rather than generating "odd" errors.
Better yet, if you could either make rt always work with Chandler's
python or eliminate non-obvious failures that occur on the stock
pythons of each of our target platforms.
John
On Jun 18, 2007, at 8:08 PM, Mike Taylor wrote:
A couple of people have been bitten by this so I wanted to post a
note explaining what happened, why and how to fix it.
rt.py when run using the stock python and not Chandler's python,
which is how I always demonstrate it, will generate odd import
errors that you may not be expecting. The reason for this is that
rt.py has "#!/usr/bin/env python" at the top and for people running
on Intel based Macs this will reference Python 2.3.5 and since
rt.py now uses a number of modules that appeared starting with
version 2.4+, the import errors happen.
To fix this you need to download the OS X install image from
python.org and install it - the new installer will adjust all the
required system environment items to make sure the new python is
now the default python.
Others have started running into path issues with the new
localization check when running on WinXP with Cygwin and this is
because of subtle issues in the localization code that I have
quick fixed. I need to get with Brian K. to make sure my quick fix
has not broken something on his end.
thanks and apologies if I slowed down anyone's rt.py runs
---
bear
Build and Release Engineer
Open Source Applications Foundation (OSAF)
[EMAIL PROTECTED]
http://www.osafoundation.org
[EMAIL PROTECTED]
http://code-bear.com
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
