HP3000-L Archives

September 2000, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"James B. Byrne" <[log in to unmask]>
Reply To:
James B. Byrne
Date:
Thu, 14 Sep 2000 12:29:43 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (47 lines)
On 13 Sep 2000, at 8:42, Shawn Gordon wrote:

> that said, I'm becoming a huge fan of Python these days, and my
> company is even working on some IDE's for visual Python
> development (multi-platform).  While PHP is more tag based like
> Cold Fusion, Python would be a full server side scripting
> language.

A looming problem with Python is that there is a very real
possibility that the language will divide into two or more
distinct dialects in the near future if a dispute over the
licensing terms is not resolved.  If this happens then the
current Python team leader will begin work on a new version
starting with the 1.5.2 code base rather than the latest 1.6
code base.  I am reproducing a portion of the message that I
received regarding this issue:

> It seems that the Python license, which is quite developer-
> friendly and workable for most people, is changing and not
> everyone is happy with the changes. The first change is based
> on Guido van Rossom, the Python team leader, moving from the
> Corporation for National Research Initiatives (CNRI), where
> he released several versions of Python. Python 1.6 was the
> last version released under the auspices of CNRI. For who
> track these things, the CNRI license is based on a BSDish
> model.
>
> What will happen with Python 2.0 is an open issue. It turns out
> that the CNRI license model uses language that incompatible with
> a true GNU Public License.  The controversy has led to
> discussions between the Python crew and Richard Stallman of the
> Free Software Foundation, including the broaching of the prospect
> of an FSF-led forking of Python at the 1.5.2 level. This leaves
> the small -- but real -- possibility of Python developers having
> to account for three different code bases.

Caveat Emptor

Regards,
Jim

---   *** e-mail is not a secure channel ***
James B. Byrne                Harte & Lyne Limited
vox: +1 905 561 1241          9 Brockley Drive
fax: +1 905 561 0757          Hamilton, Ontario
mailto:[log in to unmask]  Canada L8E 3C3

ATOM RSS1 RSS2