[Mailman-Developers] [Mailman-Users] OS X & Mailman & Python

[Barry Warsaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sep 28, 2006, at 8:45 PM, Larry Stone wrote:

> This all made me curious. I'm just a user of Mailman on Mac OS X - no
> development of any sort by me - so I'm good with 2.1.9 and Python  
> 2.3.5 on
> 10.4.7 - but this topic made me look at the Python 2.5 package at
> python.org. I finally figured out that the MacOS X python installer  
> installs
> a new version in /usr/local/bin (as well as other places) separate  
> from the
> Tiger provided version in /usr/bin. But how would you get mailman  
> to use the
> user installed version? mailmanctl has #! /usr/bin/python at the  
> top which
> will send it to the Tiger provided version. Of course you could modify
> mailmanctl but that would be subject to being overwritten when a  
> new version
> of mailman is installed. Or is that the way it would need to be done?

I'm assuming you built Mailman from source.  If so, run configure  
with --with-python=/usr/local/bin/python or put that python on your  
$PATH first, and Mailman will use that one.

If you look at the source, you'll see that the #! line is actually  
@PYTHON@ which gets substituted by configure at build time.  I forget  
exactly why, but the standard #! /usr/bin/env python invocation  
caused problems for people, so now we hardcode it via configure.

- -Barry



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iQCVAwUBRRyCCnEjvBPtnXfVAQKYxAP+Ibg1hUcx6nE/7/hH8g6sbJ/m82+ApBl9
WkSNuR3e01gyLm0ogIu3npk0pQeflVrmsvjqSCP6iBw81gaO+oeo7zkrIyFag7Ck
bqMCPIBkSDzblEUrueyTPhBvlpDlP4+vaaQSHe/EGDYSz+r/nzY/PJR6PU+lLgn4
c3SF+iHwsWU=
=FnoT
-----END PGP SIGNATURE-----