Re: [Mailman-Developers] Maybe it's time to release 2.1.6

[Ian Eiloart]

--On Friday, December 3, 2004 13:41:10 GMT +0900 Stephen J. Turnbull 
[EMAIL PROTECTED] wrote:

Ian == Ian Eiloart [EMAIL PROTECTED] writes:
Ian However, MacOSX and MacOSX Server have python Python 2.3 (#1,
Ian Sep 13 2003, 00:49:11), so requiring 2.4 could cause pain for
Ian anyone with a Mac installation of Mailman.
I'm not going to deprecate someone else's pain, but (1) Apple already
has a couple of multi-version applications standard (in particular,
GCC, see the gcc_select utility), and (2) I'm currently having no
problem with coexistence among the Apple-provided Python, two Fink
versions (2.2 and 2.3), and a DarwinPorts version (2.3).  I don't know
about Fink, but DarwinPorts has been providing a 2.4 package since the
alphas started (and maybe before).
Both Fink and DarwinPorts have their issues, but so far Python isn't
one of them.  (Actually, only ghc and the X distributions have given
me any trouble at all in DarwinPorts, and my issues with Fink mostly
are of the form too many applications that don't need to be linked to
GNOME are linked to GNOME.)
So it may not be all that difficult for admins of Apple boxes to work
around this.
Yes, of course it isn't a show stopper. Of course there are ways around the 
problem. However, the OP asked if requiring 2.4 would cause problems for 
anyone. The answer is yes: for users of MacOSX, and some other platforms 
apparently, the requirement would create extra work, and therefore inhibit 
some people from upgrading.

For each of those platforms, no doubt, there are workarounds. However, its 
not enough just to do the workaround. I have to be sure that some Apple 
update is not going to undo the workaround. I have to document the 
workaround, and educate my colleagues to understand it. I have to be sure 
that *I'm* going to remember what I did in six months time.

Yes, that's all doable, and I probably would do it. For some people though, 
it will be a show stopper. For others it will delay their implementation. 
For these reasons, it is necessary to be cautious about upping the install 
requirements.

--
Ian Eiloart
Servers Team
Sussex University ITS
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Re: [Mailman-Developers] Maybe it's time to release 2.1.6

[Dale Newfield]

Stephen J. Turnbull wrote:
(1) Apple already has a couple of multi-version applications 
standard (in particular, GCC, see the gcc_select utility)
gcc_select is completely broken, and doesn't work.  It assumes that the
only 3.x is 3.1 and fails even at what it claims to do.  I have tried 
and failed to fix the script, eventually doing all (I hope) the 
appropriate re-linking by hand.

Both Fink and DarwinPorts have their issues, but so far Python isn't
one of them.
I definitely agree with you on Fink (doesn't work at all right now 
because of gcc issue above, and it always had problems with various X 
implementations, but when it does work it's pretty nice), and only 
learned about DarwinPorts just now, so thank you!

So it may not be all that difficult for admins of Apple boxes to work
around this.
Oh, yeah, back to the topic.  Guess I don't have anything to add except 
to say that requiring all these bolt-on tools in order to install 
mailman is a bit harsh for non-admins...

-Dale
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Re: [Mailman-Developers] Maybe it's time to release 2.1.6

[John W. Baxter]

On 12/1/2004 6:05, Barry Warsaw [EMAIL PROTECTED] wrote:

 I have no problems requiring Python 2.4 for Mailman 2.2, although I
 would like to get some feedback from the community before we decide for
 sure.  I wouldn't be opposed to requiring at least Python 2.3, but I
 definitely think we should drop support for earlier Pythons since
 nothing earlier than 2.3 is being maintained any more.

The Debian part of the community in particular (of which I am not part).  I
wonder when Python 2.4 will wander into a Debian release.

Perhaps a query on the -users list about requiring Python 2.4 with Mailman
2.2 would produce a solid reason not to.

  --John
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org