[Python-Dev] some notes from the first part of the lang summit

Fri Feb 19 16:50:19 CET 2010

My notes from the session I led:
+ argparse
 - Same issues brought up.
+ Hg transition
 - Just updated everyone; Dirkjan said everything I did in his email update.
+ Stdlib breakout
 - Mentioned; nothing planned beyond a PEP at some point.
+ Extension module policy
 - If you write C code just for performance, you must provide a pure Python
 version (and both are tested).
 - When the stdlib is broken out, say ctypes-based versions are possible as
 fallback implementations.
 - Non-CPython VMs should contribute their pure Python implementations of
 modules back to the stdlib (e.g. datetime).
+ Proposing language changes
 - Need thorough dev docs.
 - People should vet ideas first, then PEP and code vetting, then submit for
 consideration.
+ Off-topic discussion
 - Need a "languishing" state in the tracker.
 - Probably should have a paid admin to help keep things such as
the Roundup tracker in
 tip-top shape to take load off of people like Martin (e.g. bug
fixes, new features, etc).
On Thu, Feb 18, 2010 at 16:56, Trent Mick <trentm at activestate.com> wrote:
> (http://trentmick.blogspot.com/2010/02/other-python-vms-upcoming-python.html)
>> Note that this was just from the first 15 minutes or so...
>>>>> Some quick notes about the coming plans by the "other" Python
>> implementations
>> from today's Python Language Summit at PyCon 2010:
>>>> - IronPython:
>>    - plan is to do Python 2.7 first, focus for this year
>>    - python 3.2 for the end of next year hopefully
>>    - other work on IDE stuff
>> - Pynie (i.e. Parrot) -- Allison Randall:
>>    - about 4 major features away from pure Python syntax (did dicts last
>>      night)
>>    - targetting py3k repo and test suite: should be on track for python
>> 3.2
>> - Jython:
>>    - plan to target 2.6 (b/c 2to3 depends on 2.6)
>>    - temporarily skip 2.7 and target 3.x (probably 3.2)
>>    - then if 3.x adoption isn't fully there, then go back and add Python
>> 2.7
>>    - will require JDK 2.7 for Python 3 support (b/c of new support for
>>      dynamic languages)
>> - PyPy (Holger):
>>    - plan is Benjamin will port to Python 2.7 in the summer
>>    - only have slight deviations from CPython: idea is to merge back with
>>      CPython so don't have deviations. Typcically 1 or 2 line changes in
>> ~25
>>      modules.
>>>>> Trent
>> --
> Trent Mick
> trentm at activestate.com
> http://trentm.com/blog/
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> http://mail.python.org/mailman/options/python-dev/brett%40python.org
>