Mailman 3 October 2008 - Python-Dev

Transformation with ``parser`` ast
by Malthe Borch Oct. 13, 2008

Oct. 13, 2008

The ``compiler.ast`` module makes parsing Python source-code and AST manipulation relatively painless and it's straight-forward to implement a transformer class. However, I find that the ``compiler.pycodegen`` module imposes a hard limit on the length of functions since it calculates jump points in a recursion. I'm using this module to compile an XML dynamic template into Python code (akin to "Mako") and functions may grow to a rather large size. Now it seems that the ``parser`` module, … [View More]

2 1

Possible summits at PyCon (and question about sprinting implications)
by Brett Cannon Oct. 13, 2008

Oct. 13, 2008

Over in PyConLand, there has been talk about trying to set up a language summit the day before PyCon starts (the second day of tutorials). The idea is to give the core developers and Python VM implementers a day to sit around and talk about stuff without having to eat into the sprints (I am not leading the organizing of it, so I don't have any exact details beyond various ideas that have leaked over to the program committee mailing list). The idea was then floated about inviting the VM … [View More]

1 0

Re: [Python-Dev] [Python-checkins] r66863 - python/trunk/Modules/posixmodule.c
by "Martin v. Löwis" Oct. 12, 2008

Oct. 12, 2008

[switching to python-dev] Georg Brandl wrote: > Martin v. Löwis schrieb: >> Raymond Hettinger wrote: >>>> Merges should be handled by the original committer. >>> Respectfully disagree. Some people here having been taking >>> responsibility for keeping the branches in-sync >> Which people specifically? > > Specifically, Christian, Benjamin and myself have done larger merges > to the 3k branch in the past, and if svnmerge is used, I … [View More]

7 13

for __future__ import planning
by Benjamin Peterson Oct. 12, 2008

Oct. 12, 2008

So now that we've released 2.6 and are working hard on shepherding 3.0 out the door, it's time to worry about the next set of releases. :) I propose that we dramatically shorten our release cycle for 2.7/3.1 to roughly a year and put a strong focus stabilizing all the new goodies we included in the last release(s). In the 3.x branch, we should continue to solidify the new code and features that were introduced. One 2.7's main objectives should be binding 3.x and 2.x ever closer. -- Cheers, … [View More]

16 31

2 modifications in robotparser.py
by Taskinoor Hasan Oct. 12, 2008

Oct. 12, 2008

im a novice python programmer. i have made two changes to robotparser.py. i apologize if this is the wrong list to post this mail. 1. some sites /* specially wikipedia */ returns 403 when default User-Agent is used. so i have changed the code to use urllib2 and added a set_user_agent method. this is simple. 2. this problem is slight complicated. please check the robots.txt file from mathworld. http://mathworld.wolfram.com/robots.txt it contains 2 User-Agent: * lines. from http://www.… [View More]

2 2

Distutils/packaging sprint this weekend
by A.M. Kuchling Oct. 11, 2008

Oct. 11, 2008

Tarek Zidae' is organizing a sprint on general distutils/setuptools/packaging this weekend. Physically it's in Arlington VA, but participants will be hanging out in #distutils on freenode's IRC. More information at <http://www.openplans.org/projects/plone-conference-2008-dc/distribute>. --am"If you're in Fairfax County and need a lift, let me know"k

2 1

syntax change justification
by Jim Jewett Oct. 11, 2008

Oct. 11, 2008

Nick Coghlan's explanation of what justifies a syntax change (most of message http://mail.python.org/pipermail/python-dev/2008-October/082831.html ) should probably be added to the standard docs/FAQs somewhere. At the moment, I'm not sure exactly where, though. At the moment, the Developer FAQ (http://www.python.org/dev/faq/) is mostly about using specific tools (rather than design philosophy), and Nick's explanation may be too detailed for the current Explanations section of www.python.org/… [View More]

4 3

backporting tests [was: [Python-checkins] r66863 - python/trunk/Modules/posixmodule.c]
by Jim Jewett Oct. 10, 2008

Oct. 10, 2008

In http://mail.python.org/pipermail/python-dev/2008-October/082994.html Martin v. Löwis wrote: > So 2.6.0 will contain a lot of tests that have never been tested in > a wide variety of systems. Some are incorrect, and get fixed in 2.6.1, > and stay fixed afterwards. This is completely different from somebody > introducing a new test in 2.6.4. It means that there are more failures > in a maintenance release, not less as in the first case. If 2.6.1 has some (possibly accidental, … [View More]

1 0

Summary of Python tracker Issues
by Python tracker Oct. 10, 2008

Oct. 10, 2008

ACTIVITY SUMMARY (10/03/08 - 10/10/08) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 2105 open (+49) / 13818 closed (+21) / 15923 total (+70) Open issues with patches: 690 Average duration of open issues: 707 days. Median duration of open issues: 1884 days. Open Issues Breakdown open 2089 (+49) pending 16 ( +0) Issues Created Or Reopened (73) … [View More]

1 0

www.python.org/doc and docs.python.org hotfixed
by Jim Jewett Oct. 10, 2008

Oct. 10, 2008

> For the search engine issue, is there any way we can tell robots to > ignore the rewrite rules so they see the broken links? (although even > that may not be ideal, since what we really want is to tell the robot > the link is broken, and provide the new alternative) I may be missing something obvious, but isn't this the exact intent of HTTP response code 301 Moved Permanently http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.2 -jJ

1 0