[Python-Dev] AST branch patches (was Re: PEP 342/343 status?)
Nick Coghlan wrote: > Brett C. wrote: > >>I noticed Nick's PEP is still not >>up. Probably too busy with that fix for genexps in the AST branch, huh, >>Nick? =) > > Something like that. . . still, I finally got around to fixing the formatting > in > the text file and sending it back to David :) Add to that AST patches for the genexp scoping, lambda nested args and creation of distinct code objects for lambdas defined on different lines. I guess I finally got over the Python overdose resulting from trying to keep up with the PEP 340 discussion :) Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --- http://boredomandlaziness.blogspot.com ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] AST branch patches (was Re: PEP 342/343 status?)
Nick Coghlan wrote: > Nick Coghlan wrote: > >>Brett C. wrote: >> >> >>>I noticed Nick's PEP is still not >>>up. Probably too busy with that fix for genexps in the AST branch, huh, >>>Nick? =) >> >>Something like that. . . still, I finally got around to fixing the formatting >>in >>the text file and sending it back to David :) > > > Add to that AST patches for the genexp scoping, lambda nested args and > creation of distinct code objects for lambdas defined on different > lines. I guess I finally got over the Python overdose resulting from > trying to keep up with the PEP 340 discussion :) > Wow! Thanks, Nick! Now I am the slacker. =) To give you and everyone else a general timeline on the AST stuff, I am coming up on the last week of school for me. After this upcoming week I have a week to pack, graduation weekend, and then I start my internship in the Bay Area. My hope is to put in at least an hour into Python every other night after work (although, knowing me, that hour will morph into three hours at least =). I am planning to split this time between the AST branch, reworking the dev docs at python.org/dev, and finally writing the Python 3000 exceptions reorg PEP. I am hoping to making some decent headway on the branch this summer before I leave for UBC. For those of you who want to keep track of the progress of the AST branch, there is a running tracker item, bug #1191458 (http://www.python.org/sf/1191458), that lists the currently failing tests. Once that bug report is closed then the AST is semantically complete. I do, though, want to go through and clean up the syntax to match PEP 7 specs before it gets merged into the mainline once it is semantically working. -Brett ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] python/dist/src/Lib/test test_site.py, 1.6, 1.7
mwh> Fix test_site to not call open('...', 'wU'), as that now raises an
mwh> error.
mwh> Is anyone running the test suite regularly at the moment?
Whoops. I obviously failed to run it after applying that change. My
apologies.
Skip
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Request for dev permissions
[Reinhold Birkenfeld] > would anybody mind if I was given permissions on the tracker and CVS, for > fixing small > things like bug #1202475. I feel that I can help you others out a bit with > this and > I promise I won't change the interpreter to accept braces... Let's start out with CVS tracker permissions. When you have a patch that is really to apply, upload it to the tracker and assign to me. Raymond Hettinger ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Request for dev permissions
> Let's start out with CVS tracker permissions. > When you have a patch that is really to apply, > upload it to the tracker and assign to me. really --> ready ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] PEP 346: User defined statements (formerly known as PEP 3XX)
My erstwhile PEP now has a real number (PEP 346), and a home on python.org [1]. At my request, it was withdrawn immediately after submission - the parts I think are important, Guido is taking on board for PEP 343 [2]. Cheers, Nick. [1] http://www.python.org/peps/pep-0346.html [2] http://mail.python.org/pipermail/python-dev/2005-May/053885.html -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --- http://boredomandlaziness.blogspot.com ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Split MIME headers into multiple lines near a space
Hello,
I recently used Python to automatically send messages to my gmail
account. I was surprised to find out that some of the words in the
subjects of messages were split by a space character which came from
nowhere.
It turns out that the international (Hebrew) subject was split into
multiple lines by the email package, sometimes in the middle of words.
Gmail treats these line breaks as spaces, so words gets cut into two.
I've checked, and there are email clients which ignore the line
breaks, so the subject looks ok.
I added four lines to the _binsplit function of email.Header, so that
if there is a space character in the string, it will be splitted
there. This fixes the problem, and subjects look fine again. These
four lines (plus a comment which I wrote) are:
# Try to find a place in splittable[:i] which is near a space,
# and split there, so that clients which interpret the line break
# as a separator won't insert a space in the middle of a word.
if splittable[i:i+1] != ' ':
spacepos = splittable.rfind(' ', 0, i)
if spacepos != -1:
i = spacepos + 1
These lines should be added before the last three lines of _binsplit.
Do you think it's ok? Could this be added to email.Header?
(Should I send this as a patch? It's just that the patch list was full
of IDLE patches, and this change is really small, so I thought that it
would be easier to post it here. Please tell me if I was wrong.)
Thank you,
Noam Raphael
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
