Toward Python's future article

[Ville Vainio]

>>>>> "daniel" == daniel narf <vegeta.z at gmail.com> writes:

    daniel> Hi i am sure most of you have read the article of Andrew
    daniel> Kuchling about focusing more in the standart library than
    daniel> language newFeatures/tweaking and probably i

Tweaking/optimizing the interpreter is all right IMO. Language
features, esp. genexps are welcome too. I'm still not sure whether we
are at the local maximum yet.

Actually, what I'd like to see is (with a strong FWIW disclaimer, of
course):

1. Stabilize the language for Python 2.x series. 

2. Start thinking about the important stuff that will go into py3.0 -
   especially the major design issues like optional type declarations
   that will pay off in products like IronPython.

3. Collect lots of "best of breed" stuff in a psedo-official "extra
   batteries" distribution. This should include useful and
   API-stable-ish frameworks. Some of the current standard libraries
   could be moved to the extra batteries.

4. Publish a canonical type inference system for Python source code,
   implemented in Python of course. 

5. Put some effort in maturization of pydev+eclipse, making it the
   "obvious" choice for the freeloaders who still want a mature IDE.

Yes, point 5 has very little to do with python standard libraries,
just something that would accelerate corporate penetration among the
uninitiated programmers, and is tightly mingled with point 4.

    daniel> i am personaly very interested in improving the stdlib
    daniel> which is very messy in my opinion right now.

I'm kinda surprised about the negative press the stdlib has been
getting as a result of AMK's blog entry. I still think stdlib is
beautiful :-).

    daniel> the article(several comments): 

    daniel> http://www.amk.ca/diary/archives/cat_python.html#003382


-- 
Ville Vainio   http://tinyurl.com/2prnb