python-dev sprint at PyCon
Every PyCon has featured a python-dev sprint. For the past few years, hacking on the AST branch has been a tradition, but we'll have to come up with something new for this year's conference (in Dallas Texas; sprints will be Monday Feb. 27 through Thursday March 2). According to Anthony's release plan, a first alpha of 2.5 would be released in March, hence after PyCon and the sprints. We should discuss possible tasks for a python-dev sprint. What could we do? When the discussion is over, someone should update the wiki page with whatever tasks are suggested: <http://wiki.python.org/moin/PyCon2006/Sprints>. --amk
At 09:35 AM 11/1/2005 -0500, A.M. Kuchling wrote:
* PEP 343 implementation ('with:') * PEP 308 implementation ('x if y else z') * A bytes type Or perhaps some of the things that have been waiting for the AST branch to be finished, i.e.: * One of the "global variable speedup" PEPs * Guido's instance variable speedup idea (LOAD_SELF_IVAR and STORE_SELF_IVAR, see http://mail.python.org/pipermail/python-dev/2002-February/019854.html)
On 11/1/05, Phillip J. Eby <pje@telecommunity.com> wrote:
* PEP 328 - absolute/relative import * PEP 341 - unifying try/except and try/finally (I believe this was accepted; it's still marked Open in PEP 0)
-- --Guido van Rossum (home page: http://www.python.org/~guido/)
On 11/1/05, Guido van Rossum <guido@python.org> wrote:
I added the 4 PEPs mentioned and a few more ideas here: http://wiki.python.org/moin/PyCon2006/Sprints/PythonCore n
amk> Every PyCon has featured a python-dev sprint. For the past few amk> years, hacking on the AST branch has been a tradition, but we'll amk> have to come up with something new for this year's conference... This is just a comment from the peanut gallery, as it's highly unlikely I'll be in attendance, but why not continue with the AST theme? Instead of working on the AST branch, you could start to propagate the AST representation around. For example, you could use the new AST code to improve/extend/rewrite the optimization steps the compiler currently performs. Another alternative would be to rewrite Pychecker (or Pychecker 2) to operate from the AST representation. Skip
On 11/1/05, skip@pobox.com <skip@pobox.com> wrote:
That's an excellent suggestion. I think I will borrow the time machine and add it to the wiki. :-) It's up on the wiki. Brett also added an item for the peephole optimizer. Everyone should add whatever they think are good ideas, even if they don't plan to attend the sprints. n
At 09:35 AM 11/1/2005 -0500, A.M. Kuchling wrote:
* PEP 343 implementation ('with:') * PEP 308 implementation ('x if y else z') * A bytes type Or perhaps some of the things that have been waiting for the AST branch to be finished, i.e.: * One of the "global variable speedup" PEPs * Guido's instance variable speedup idea (LOAD_SELF_IVAR and STORE_SELF_IVAR, see http://mail.python.org/pipermail/python-dev/2002-February/019854.html)
On 11/1/05, Phillip J. Eby <pje@telecommunity.com> wrote:
* PEP 328 - absolute/relative import * PEP 341 - unifying try/except and try/finally (I believe this was accepted; it's still marked Open in PEP 0)
-- --Guido van Rossum (home page: http://www.python.org/~guido/)
On 11/1/05, Guido van Rossum <guido@python.org> wrote:
I added the 4 PEPs mentioned and a few more ideas here: http://wiki.python.org/moin/PyCon2006/Sprints/PythonCore n
amk> Every PyCon has featured a python-dev sprint. For the past few amk> years, hacking on the AST branch has been a tradition, but we'll amk> have to come up with something new for this year's conference... This is just a comment from the peanut gallery, as it's highly unlikely I'll be in attendance, but why not continue with the AST theme? Instead of working on the AST branch, you could start to propagate the AST representation around. For example, you could use the new AST code to improve/extend/rewrite the optimization steps the compiler currently performs. Another alternative would be to rewrite Pychecker (or Pychecker 2) to operate from the AST representation. Skip
On 11/1/05, skip@pobox.com <skip@pobox.com> wrote:
That's an excellent suggestion. I think I will borrow the time machine and add it to the wiki. :-) It's up on the wiki. Brett also added an item for the peephole optimizer. Everyone should add whatever they think are good ideas, even if they don't plan to attend the sprints. n
participants (6)
-
A.M. Kuchling -
Guido van Rossum -
Jeremy Hylton -
Neal Norwitz -
Phillip J. Eby -
skip＠pobox.com