Thanks to your comments, I think I'm making some progress here ...
On Dec 20, 2004, at 10:21 AM, Bob Ippolito wrote:
Apache starts as root with root's default environment. It's not going to have /sw/bin in its path, so /usr/bin/env python is not going to run Fink python. You might as well replace it with #!/sw/bin/python.
that didn't work. We needed the compound line #!/sw/bin/env /sw/bin/python in the scripts
Why the hell does Fink have its own env, anyway?
you're asking me?
Darwinports Python and the vendor Python play together perfectly nicely, with no obscure disasters anywhere that I've seen. If you are having conflicts between Fink and vendor Python, then it must be caused by Fink. Probably due to the init script in your .bashrc / .tcshrc that sets up your environment in such a way that everything you do can end up using or linking to Fink-built stuff. Darwinports doesn't have any such hacks, and never mangles your environment like that.
in my home directory I have neither .bashrc nor .tcshrc I did have a .profile and a .pythonrc I renamed both, Quit terminal and restarted and got new symptoms
208-186-56-189:/sw/bin jis$ idle -bash: idle: command not found 208-186-56-189:/sw/bin jis$ /sw/bin/idle Fatal Python error: Interpreter not initialized (version mismatch?) Abort trap
208-186-56-189:/sw/bin jis$ cat /sw/bin/idle2.3 #!/sw/bin/python
from idlelib.PyShell import main main()
so I tried it manually
208-186-56-189:/sw/bin jis$ /sw/bin/python
Python 2.3.4 (#1, Nov 7 2004, 14:21:14)
[GCC 3.3 20030304 (Apple Computer, Inc. build 1495)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from idlelib.PyShell import main
>>> main()
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/sw/src/root-python23-2.3.4-2/sw/lib/python2.3/idlelib/PyShell.py", line 1274, in main
File "/sw/lib/python2.3/lib-tk/Tkinter.py", line 1564, in __init__
self.tk = _tkinter.create(screenName, baseName, className)
_tkinter.TclError: this isn't a Tk applicationcouldn't connect to display ":0.0"
I ran startx in a separate terminal window...
>>> main() >>>
this time it worked (and within idle, vpython worked)
so there's something different about running idle from the command line versus from within python????
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Jon Schull, Ph.D. Associate Professor Information Technology Rochester Institute of Technology 102 Lomb Memorial Drive Rochester, New York 14623 [EMAIL PROTECTED] 585-738-6696
_______________________________________________ Pythonmac-SIG maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/pythonmac-sig
