How much is set in stone?

[Delaney, Timothy]

You have a couple of options.

1. Choose a baselined version - usually, 1.5.2, 2.0.1 or 2.1.1 (soon to be
2.1.2?). Distribute the version with your app (if you are embedding it in an
app, this is almost certainly what you want to do).

2. Stick with the features in 2.1. Apart from the addition of the "yield"
keyword (and hence generators), no features of the language will change
until 3.0 (although you can access new features using from __future__
statements).

3. If there is a particular feature that you need that is missing from a
distribution, you can always add it yourself - perferably as a library, but
if you need to change the core, you can. It's unlikely that such a change
would make it into the standard distribution, but if you make a good enough
argument for it, and (most importantly) provide the source to the change, it
just may.

Tim Delaney
Cross Avaya R&D
+61 2 9352 9079

> -----Original Message-----
> From: Jive Dadson [mailto:jdadson at ix.netcom.com]
> Sent: Sunday, 4 November 2001 5:25 PM
> To: python-list at python.org
> Subject: How much is set in stone?
> 
> 
> I'm a newbie at Python, but I've been up to my ears in it for the last
> couple of days. -- Considering using it for a scripting language for a
> product at work.  I'm very impressed with the system.  Of course there
> are things I would like to change. :-)  So the question is, 
> how much is
> set in stone at this point?  Is the definition of 2.x now the 
> law of the
> land, or can we still make suggestions?
> 
> Jive
> -- 
> http://mail.python.org/mailman/listinfo/python-list
>