./configure didn't pick up bad python version (PR#227)

Bug #265296 reported by Bug Importer
2
Affects Status Importance Assigned to Milestone
GNU Mailman
Fix Released
Medium
Unassigned

Bug Description

Jitterbug-Id: 227
Submitted-By: <email address hidden>
Date: Tue, 18 Apr 2000 22:30:43 -0400 (EDT)
Version: 2.0beta2
OS: Linux (RedHat 6.0 with upgrades)

Mailman 2.0beta2 installed OK, but when run (via CGI) generated a Python
error
and stack traceback. Later realized that docs said Python version 1.5.2 was
required and I only had Python 1.5.1-10. Upgrading to Python 1.5.2-13 fixed
the
problem.

Should not ./configure have picked up the version problem?

====================================================================
Audit trail:
None

[http://sourceforge.net/tracker/index.php?func=detail&aid=214175&group_id=103&atid=100103]

Revision history for this message
Barry Warsaw (barry) wrote :

As of 2.0beta4, it does.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.