This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Bleve
Recipients Bleve, iMil, pitrou
Date 2011-04-10.09:14:00
SpamBayes Score 3.5527137e-15
Marked as misclassified No
Message-id <1302426841.66.0.571269434115.issue11810@psf.upfronthosting.co.za>
In-reply-to
Content
Plone ships with a "universal installer" which expects particular versions of python (and PIL etc etc) which makes it easy to build on, for example, many Linux distros, but it's just not working on Open[Solaris|Indiana] and also NetBSD (pkgsrc's python2.6 is broken too, but we're working on that).  The only time the installer gets bumped is when new versions of Plone get released, which means that only the bleeding edge might work.  This is a problem for many integrators who are tied to older versions of Plone|Zope that are unlikely to get migrated to more recent releases in any sort of a reasonable timeframe.

Is it really not possible to fix up python2.6 to solve this issue?
History
Date User Action Args
2011-04-10 09:14:01Blevesetrecipients: + Bleve, pitrou, iMil
2011-04-10 09:14:01Blevesetmessageid: <1302426841.66.0.571269434115.issue11810@psf.upfronthosting.co.za>
2011-04-10 09:14:01Blevelinkissue11810 messages
2011-04-10 09:14:00Blevecreate