Derek: On Mon, 25 Mar 2002, Derek Homeier wrote:
> On Sunday, March 24, 2002, at 11:17 PM, Derek Homeier wrote: > > I had a few other minor problems: > > Some packages, such as scientificpython and pil install into > /sw/lib/python2.1/site-packages/ , though they don't explicitly require > python2.1. They are thus invisible to python2.2 unless you create symlinks > into /sw/lib/python2.2/site-packages. All extension modules need to be rebuilt with each new minor revision of python. When you rebuild, they will be put into the correct directory for the version of python you have installed. This is what Guido recommends, mainly because you can't assume the bytecode will be compatible from one version to the next. We probably should make these packages depend on a specific version of python though, for the sake of the binary distribution. > > Then, I found that env would fail to execute "#!/usr/bin/env python" > scripts with "env: python : No such file or directory". > Of course, /sw/bin is in my path, but how do I make that known to env? Works for me. Are you sure /sw/bin is in your path (in the environment that you're trying to execute the python script)? -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 Meteorologist FAX : (303)497-6449 NOAA/OAR/CDC R/CDC1 Email : [EMAIL PROTECTED] 325 Broadway Web : www.cdc.noaa.gov/~jsw Boulder, CO, USA 80303-3328 Office : Skaggs Research Cntr 1D-124 _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
