--On 20 July 2005 14:57:26 -0400 Barry Warsaw <[EMAIL PROTECTED]> wrote:
> On Wed, 2005-07-20 at 12:16, Ian Eiloart wrote: > >> Am I right in thinking this means that I need to downgrade my python >> version to make this work? > > No, but apparently does mean that you'll have to rebuild the codec > extensions that come with Mailman. I /think/ if you run Mailman's > config.status and then run make install again (against Python 2.4.1 of > course) you should be golden. > > Let us know if that works and I'll update the release notes. > > -Barry > OK. I'm having a go at this. I'm not sure how that's supposed to work, though. I've built Mailman 2.1.6 with Python 2.4.1, and it didn't work when installed with Python 2.4.1, and run along side Python 2.4.1 I've built Mailman 2.1.6 with Python 2.2.3, and it works fine. Doesn't matter whether I have Python 2.2.3 or 2.4.1. I'm trying again - but why would config.status do anything? Well, blimey. Everything seems hunky-dory now. Thanks, Barry! -- Ian Eiloart Servers Team Sussex University ITS _______________________________________________ Mailman-Developers mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
