Idan Gazit wrote:
On Oct 19, 2008, at 8:12 PM, Kevin Walzer wrote:
Not sure if 2.6 does the same, but I thought it did. It certainly
doesn't touch /etc/paths.d, nor should it. ~/.MacOSX/environment.plist
isn't affected either as far as I know.
A little bit of rooting around inside the installer packages /
subpackages shows two postflight scripts, one in PythonFramework and one
in PythonSystemFixes. Neither one of them seems to take any action
regarding the path at all.
That being said my understanding of installer packages is roughly zero.
If I could be clued into where these post-install scripts are supposed
to be I can attempt some detective-work on my own.
Thanks,
Idan
Not sure what the problem is. As I said before, if the installer no
longer modifies your $PATH, then something has changed in the
installation process over the past year or so.
Can any of the Python maintainers on the Mac shed some light on this?
Ronald, any ideas? Or is someone else putting together the official
python.org build? In any event, it is seriously broken, and I hope that
someone puts together a new build in the near future.
--
Kevin Walzer
Code by Kevin
http://www.codebykevin.com
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
