Re: [Mailman-Developers] Python-2.2 disaster

2002-03-06 Thread Ron Jarrell
At 11:50 AM 3/5/02 -0500, Barry A. Warsaw wrote: >> "CG" == Carson Gaspar <[EMAIL PROTECTED]> writes: > >CG> *sigh* The problems with running such a low market share >CG> platform like Solaris/SPARC *snort* > >Ah, okay. Well, I tried to get into the Solaris machines on the SF >compil

Re: [Mailman-Developers] Python-2.2 disaster

2002-03-05 Thread Dan Mick
> FYI, 2.2 is completely DOA on Solaris 8/SPARC. I'm using 2.2 daily on Solaris 8/SPARC. ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers

Re: [Mailman-Developers] Python-2.2 disaster

2002-03-05 Thread Chuq Von Rospach
On 3/5/02 9:30 AM, "Chuq Von Rospach" <[EMAIL PROTECTED]> wrote: > Python 2.2 on Solaris isn't that tough. I should note: my boxes are solaris 2.5 through Solaris 7. I haven't really started on 8 yet. YMMV. -- Chuq Von Rospach, Architech [EMAIL PROTECTED] -- http://www.chuqui.com/ The Cliff'

Re: [Mailman-Developers] Python-2.2 disaster

2002-03-05 Thread Barry A. Warsaw
> "CG" == Carson Gaspar <[EMAIL PROTECTED]> writes: CG> FYI, 2.2 is completely DOA on Solaris 8/SPARC. After I got it CG> to compile (and gained more grey hair), it ends up hanging on CG> SMTPlib.connect(), somewhere in the bowels of hostname CG> resolution. Either something

Re: [Mailman-Developers] Python-2.2 disaster

2002-03-05 Thread Chuq Von Rospach
On 3/5/02 8:50 AM, "Barry A. Warsaw" <[EMAIL PROTECTED]> wrote: > CG> *sigh* The problems with running such a low market share > CG> platform like Solaris/SPARC *snort* > > Ah, okay. Well, I tried to get into the Solaris machines on the SF > compile farm, but I couldn't seem to scp up a Pyt

Re: [Mailman-Developers] Python-2.2 disaster

2002-03-05 Thread Carson Gaspar
--On Tuesday, March 05, 2002 11:35 AM -0500 "Barry A. Warsaw" <[EMAIL PROTECTED]> wrote: > I, and lots of people, are using Python 2.2 today. I do all my > primary testing on Python 2.2, so I feel confident in recommending > it. FYI, 2.2 is completely DOA on Solaris 8/SPARC. After I got it t

Re: [Mailman-Developers] Python-2.2 disaster

2002-03-05 Thread Barry A. Warsaw
> "DW" == Dan Wilder <[EMAIL PROTECTED]> writes: DW> From this I get the feeling that many things which worked DW> under Python 1.5 do not work under 2.1 or 2.2. If you mean Python 1.5 instead of 1.5.2 then you might be right. While both are extremely old, the latter was the gold st

Re: [Mailman-Developers] Python-2.2 disaster

2002-03-05 Thread Barry A. Warsaw
> "CG" == Carson Gaspar <[EMAIL PROTECTED]> writes: CG> *sigh* The problems with running such a low market share CG> platform like Solaris/SPARC *snort* Ah, okay. Well, I tried to get into the Solaris machines on the SF compile farm, but I couldn't seem to scp up a Python 2.2. tarb

Re: [Mailman-Developers] Python-2.2 disaster

2002-03-05 Thread Barry A. Warsaw
> "CG" == Carson Gaspar <[EMAIL PROTECTED]> writes: CG> Now to try and fix audioop and fpectl... You won't need these modules for Mailman, so if that's the only app you care about, I wouldn't bother. -Barry ___ Mailman-Developers mailing lis

Re: [Mailman-Developers] Python-2.2 disaster

2002-03-05 Thread Barry A. Warsaw
> "CG" == Carson Gaspar <[EMAIL PROTECTED]> writes: CG> What !@#$% idiot did the python 2.2 build system!? It CG> bombs out trying to compile the extensions, because _someone_ CG> got "clever" and decided to write the build system in CG> Python. And got it wrong. So it doesn

Re: [Mailman-Developers] Python-2.2 disaster

2002-03-05 Thread Dan Wilder
On Tue, Mar 05, 2002 at 02:07:15AM -0800, James J. Besemer wrote: > > Carson Gaspar wrote: > > > Can one of the Python gurus here tell me if I just missed an obvious > > "correct" way to fix this, or if this is really a broken build process? > > Dunno. [Real helpful, I know.] > > But FWIW I'm

Re: [Mailman-Developers] Python-2.2 disaster

2002-03-05 Thread James J. Besemer
Carson Gaspar wrote: > Can one of the Python gurus here tell me if I just missed an obvious > "correct" way to fix this, or if this is really a broken build process? Dunno. [Real helpful, I know.] But FWIW I'm running 2.0.8 and despite the documentation I couldn't get things to install or run

Re: [Mailman-Developers] Python-2.2 disaster

2002-03-05 Thread Carson Gaspar
The other module problems: audioop needed a "libraries = ['m']" fpectl needed a "libraries = ['sunmath', 'm']" These are probably Solaris-specific, and it looks like sunmath is Forte (nee SunPRO) specific. But it makes it compile on my SPARC SunOS 5.8 box with Forte 6.x. *sigh* The problems w

Re: [Mailman-Developers] Python-2.2 disaster

2002-03-05 Thread Carson Gaspar
OK, I "fixed" the _socket problem by hacking setup.py to change how it found ssl_incs and ssl_libs, and by adding 'runtime_library_dirs = ssl_libs' to the exts.append clause. Can one of the Python gurus here tell me if I just missed an obvious "correct" way to fix this, or if this is really a

[Mailman-Developers] Python-2.2 disaster

2002-03-05 Thread Carson Gaspar
What !@#$% idiot did the python 2.2 build system!? It bombs out trying to compile the extensions, because _someone_ got "clever" and decided to write the build system in Python. And got it wrong. So it doesn't compile or link properly. And after chasing through _8_ levels of indirection withou