Mailman 3 January 2004 - Python-Dev

Re: Tracebacks into C code
by Edward C. Jones Jan. 22, 2004

Jan. 22, 2004

*Martin v. Löwis wrote:* > Edward C. Jones wrote: > >/ Suppose: /> >/ I have a Python extension written in C. /> >/ "My_Func" is a function in the extension which is visible at the /> >/ Python level. /> >/ "My_Func" calls the C function "C_func1". /> >/ "C_func1" calls the C function "C_func2". /> >/ "C_func2" raises an exception by calling something like /> >/ "PyErr_SetString". />/ How do I make the Python traceback include "C_func1" and "C_func2"? /> > You need to create frame objects. See Modules/pyexpat.c for an example. That looks complicated. > Regards, > Martin > > P.S. This is OT for python-dev. I should have directly asked: Should some traceback-through-C capability be put in the Python API?

3 3

PEP 11 mistake?
by Skip Montanaro Jan. 21, 2004

Jan. 21, 2004

Looking at the future unsupported platforms I saw this: Name: MacOS 9 Unsupported in: Python 2.4 Code removed in: Python 2.4 Surely the code shouldn't removed until 2.5, right? Skip

3 3

Python in 2003 summary
by A.M. Kuchling Jan. 21, 2004

Jan. 21, 2004

[Cc'ed to python-dev, marketing-python; trim followups accordingly] Here's a first draft of a summary of significant Pythonological matters in 2003. * What significant things did I miss? * Are there additional pages I should link to? * Can anyone help fill out the conferences section? For example, are the papers for OSCON, PythonUK, or EuroPython available online anywhere? Does anyone have pages with photos/conference reports/anything? If you don't want to read ReST source, an HTML-formatted version is at http://www.amk.ca/python/writing/2003 . Please don't link to or weblog it yet; when it's done, it'll go on python.org. --amk ================================================== In 2003, there was one new major release of Python and several minor bugfix releases. The Python Software Foundation began to assume a greater role and visibility in the community, organizing the first PyCon conference. A number of noteworthy books were published, and the conference calendar was also full. The Python Language ============================ Python 2.3 was released in July. Compared to last year's Python 2.2 release, 2.3 was fairly conservative, making relatively few changes to the language itself such as some new built-in functions, and a true Boolean type. There were also a number of low-level changes such as new import hooks, minor optimizations, and a specialized object allocator. The real action was in the standard library, where new packages were added for date/time handling, sets, heaps, logging, bzip2 data compression, reading and writing tar files, word-wrapping paragraphs, command-line parsing, and importing Python modules from ZIP archives. Some external packages were absorbed into the standard library such as the latest version of IDLE and the PyBSDDB wrapper for BerkeleyDB. Another new feature in 2.3 was support for cataloging Python modules and applications in the Package Index. The list of packages can be browsed and searched at http://www.python.org/pypi . Since the release of 2.3, three bugfix releases have been issued. All of them were ably coordinated by Anthony Baxter. The current version is Python 2.3.3: http://www.python.org/2.3.3/. For the highlights of the new features, see "What's New in Python 2.3": http://www.python.org/doc/2.3.3/whatsnew/. For a full list of changes to 2.3, see the release notes at http://www.python.org/2.3/NEWS.txt. There was also a bugfix release of Python 2.2. Python 2.2.3 was released in May, coordinated by Barry Warsaw. http://www.python.org/2.2.3/. The Python Software Foundation ================================================== The Python Software Foundation, or PSF, is the copyright holder for current versions of Python. This year the PSF became a 501(c)(3) charity for the purposes of US taxation, so donations to the PSF are now tax-deductible in the US. To donate funds, go to http://www.python.org/psf/donations.html ; you can use PayPal or mail a cheque. In December the ownership of the python.org domain name was transferred from CNRI, which has held it since the mid-1990s, to the PSF. The largest PSF activity in 2003 was organizing the first PyCon conference, held in Washington DC in late March. Conferences =================== PyCon '''''' PyCon DC 2003 was held in Washington DC in late March, organized by the PSF. The conference had an experimental, informal flavor. While several tracks of refereed presentations were on the program, there was also a lot of free time for informally scheduled presentations and discussions, and a few development sprints took place before the official beginning of the conference. Links to papers and slides from PyCon 2003 are at http://www.python.org/cgi-bin/moinmoin/PyConPapers . Various people posted pictures: http://www.python.org/cgi-bin/moinmoin/PyConPhotos Mike Orr had a writeup of the conference in the Linux Journal: http://www.linuxjournal.com/print.php?sid=6800. A.M Kuchling wrote about his impressions of PyCon at http://www.amk.ca/diary/2003/03/27#2003-03-27-2 and http://www.amk.ca/diary/2003/03/28. Coming Soon: PyCon 2004 """""""""""""""""""""""""""" The production work for PyCon 2004 is well under way. The conference will be from March 24-26 in Washington DC. Mitch Kapor will be a keynote speaker. The deadline for proposals is January 15 2004; early bird registration ends February 1 2004. See the conference web pages at http://www.python.org/pycon/dc2004/ for more information. OSCON '''''''' The Python 11 conference was held as part of O'Reilly's OSCON2003 in Portland, Oregon in July. The schedule for Python 11 is at http://conferences.oreillynet.com/pub/w/23/track_python.html . XXX is there a page with links to papers and slides? The Python 12 conference will be part of OSCON 2004, July 26-30 in Portland. The conference site is http://conferences.oreillynet.com/os2004/ . EuroPython '''''''''''''''''''' EuroPython, the major European Python conference, was held in Charleroi, Belgium, in June. Links to papers and slides from EuroPython 2003 are at http://www.europython.org/sessions/talks/slidespapers (for now, anyway). The conference organizers interviewed various participants, available from http://www.europython.org/other/interviews . PythonUK '''''''''''''' The PythonUK conference was held in Oxford in April, organized with the assistance of the Association of C/C++ Users. XXX any links to papers? Workshop on Scientific Computing with Python '''''''''''''''''''''''''''''''''''''''''''''''''' The second SciPy conference was held in 2003, taking place at Caltech in Pasadena, California, in September. The conference site is at http://www.scipy.org/ . You can see the schedule at http://www.scipy.org/site_content/scipy03/scipy03sched.htm . Chuck Esterbrook wrote up his impressions: http://www.sandpyt.org/pipermail/sandpyt/2003-September/000271.html Community =================== At OSCON, a number of awards were given out to notable members of the Python community. * Mark Hammond won the ActiveState Programmer's Choice award for his work on the Windows and COM frameworks for Python. * Martin von Loewis won the Activator's Choice award for his constant and efficient work on maintaining the Python core and handling bugs and patches. * The Frank Willison award went to Fredrik Lundh, another skilled contributor who wrote the regular expression engine for Python 1.6, implemented XML-RPC, and wrote an introduction to the Python standard library. He also started the Daily Python-URL weblog, which posts Python-related news and links. His comments on receiving the award are at http://effbot.org/zone/frank-willison-award.htm. The daily Python-URL is at http://www.pythonware.com/daily/. There was one significant loss to the community; Bryan Richard, editor and publisher of the Py 'zine, had to abandon it due to other personal commitments. Py was taken over by beehive KG, the firm that's been publishing ZopeMag magazine, and will become an electronic-only publication. The Py web site is still at http://www.pyzine.com. New Books =================== A number of significant books about basic Python were released in 2003. O'Reilly released :title-reference:`Python in a Nutshell` by Alex Martelli. At 654 pages long it's a pretty large nutshell, but the book is an excellent one-volume Python reference. Soon after its release the book reached Amazon's list of top 100 bestsellers for a while. The second edition of :title-reference:`Learning Python` by Mark Lutz and David Ascher, another noteworthy title, also came out this past year; :title-reference:`Learning Python` is most commonly recommended as the book for beginning Python users, so this update was most welcome. The new edition brings the coverage up to Python 2.3, including features such as iterators and generators. One title went out of print and was resurrected as an e-book. Fredrik Lundh's :title-reference:`Python Standard Library` was published in 2001, but the electronic version has additional updates, including examples for some modules introduced in Python 2.2 and 2.3. See http://effbot.org/zone/librarybook-index.htm for the online edition. Some more specialized titles appeared. Two books on games appeared, Tom Gutschmidt's :title-reference:`Game Programming w/ Lua, Python, Ruby`, Sean Riley's :title-reference:`Game Programming with Python`. John Zelle's :title-reference:`Python Programming: An Introduction to Computer Science` uses Python as the vehicle for an introductory course. David Mertz's :title-reference:`Text Processing in Python` takes takes its chosen topic and carefully covers every possible aspect of it, mixing sections of reference material with tutorial explanations. A more complete listing of Python books is available in the Python Wiki: http://www.python.org/cgi-bin/moinmoin/PythonBooks

7 14

Issue with HTTP basic proxy authentication in urllib2
by Ivano Broz Jan. 21, 2004

Jan. 21, 2004

I have only been scripting in python for about 3 months and have mainly been performing HTTP requests to cgi scripts. I have had had a lot of trouble with POST method and believe I have tracked this down to the fact that I'm having to perform Basic Proxy authentication. When the HTTP header for Basic authentication is created in urllib2 the username and password are encoded using the encodestring() method of the base64 module. This adds a newline '\n' to the end of the returned encoded string (as documented). from urllib2.py def proxy_open(self, req, proxy, type): orig_type = req.get_type() type, r_type = splittype(proxy) host, XXX = splithost(r_type) if '@' in host: user_pass, host = host.split('@', 1) if ':' in user_pass: user, password = user_pass.split(':', 1) user_pass = base64.encodestring('%s:%s' % (unquote(user),Harry_Connick_Jr - She.albm unquote(password))) req.add_header('Proxy-authorization', 'Basic ' + user_pass) This newline then becomes the end of the HTTP Proxy authentication header: Proxy-authorization: Basic asdfSADFwaer%asfdas=\n When the HTTP request is assembled the required CRLF is added to the end of each header along with the one extra to indicate the end of the request headers. This would seem OK except some HTTP servers appear to interperet the newline after the proxy authentication header as an extra blank line in the request, thus missing any data sent through in the body of the request. This is not a problem with the GET method (obviously) or a POST method which is not sent though an HTTP Proxy server requiring authentication. I made the very simple addition to urllib2.py of user_pass=user_pass.rstrip() to remove the trailing '\n' from the encoded username/password before it was added to the HTTP headers and everything works without a problem. I'm not sure if this is an issue which has been raised before. I glanced through the summaries of the python-dev mailing list for the past year and found no mention of it. Technically I don't see it as a bug in urllib2.py but an incorrect implementation of HTTP header parsing by servers (The Proxy server may even be the culprit) Cheers PS. If there is any need to discuss this could I please be CC'd as I am not a member of the mailing, Thanks -- Ivano Broz Metabolic Research Unit, Pigdons Road, Waurn Ponds 3217, Victoria Australia Ph: 61 3 52272195 "the money I save won't buy my youth again"

2 1

nesws regarding vigros Bretons
by Quest Jan. 21, 2004

Jan. 21, 2004

simplest, How Vigras works. And you can better understand, what Vigras can do for you. If you are sensible about your health, reflect on what you can do for your seual health, to keep the chances that you will need Vigras as low as possible. dancers circuitous bleats, relented. http://www.effectiveherbs.com/index.php?pid=genviag Inrease Seks Drive Bost Seual Performance Fuller & Harder Erecions Inrease Stamna & Endurance Quicker Rechages conspire Syrianizes plucking, genders. Burch soles Georgia, prophetic. Happy holidays, Goethe

1 0

RE: [Python-Dev] dict.addlist()
by Moore, Paul Jan. 20, 2004

Jan. 20, 2004

From: Raymond Hettinger > [Bob Ippolito] >> d.setdefault(k, factory=list).append(v) ? > > That is somewhat nice and backwards compatible too. -1 How is it more expressive than d.setdefault(k, []).append(v)? As far as I can see, it's longer and contains an extra obscure(ish) term (factory). And I agree with the other posters that other defaults are often useful, and further complicating the dictionary interface isn't particularly helpful. If conciseness is important, def addlist(d, k, v): d.setdefault(k, []).append(v) Paul.

5 5

Re: [Python-checkins] python/dist/src/Lib/email/test test_email_codecs.py, 1.4, 1.5
by Barry Warsaw Jan. 20, 2004

Jan. 20, 2004

On Sat, 2004-01-17 at 09:29, perky(a)users.sourceforge.net wrote: > Update of /cvsroot/python/python/dist/src/Lib/email/test > In directory sc8-pr-cvs1:/tmp/cvs-serv14239/Lib/email/test > > Modified Files: > test_email_codecs.py > Log Message: > Add CJK codecs support as discussed on python-dev. (SF #873597) Should we backport this to 2.3? I still intend to backport 852347 when the branch is unfrozen <wink>. -Barry

7 19

PY_VERSION is undocumented
by Edward C. Jones Jan. 20, 2004

Jan. 20, 2004

PY_VERSION seems to be undocumented. Is anything else in the API undocumented?

2 1

isinstance(x, types.UnboundMethodType) feature
by Gareth Ladd Jan. 20, 2004

Jan. 20, 2004

Hello all, Whilst writing a routine to perform callbacks, I was performing a check to ensure the callback method is callable and bound. After checking "callable(x)" I then check that "x" is bound using "isinstance(x, types.UnboundMethodType)". It appears the latter returns true if "x" is a bound or an unbound class/instance method. Please have a look at the following example. I would expect #3 to return "False". <code> import types def hello(): print "hello" class C: def hello(self): print "hello" c=C() print isinstance(hello, types.UnboundMethodType) #1 print isinstance(C.hello, types.UnboundMethodType) #2 print isinstance(c.hello, types.UnboundMethodType) #3 # Check it is actualy bound f=c.hello f() #4 </code> <output> False True True hello </output> Am I missing an subtelty of bound/unbound-ness? Thanks in advance, Gareth.

3 3

RE: [Python-Dev] dict.addlist()
by Phillip J. Eby Jan. 20, 2004

Jan. 20, 2004

At 02:41 PM 1/20/04 +0000, Moore, Paul wrote: >From: Raymond Hettinger > > [Bob Ippolito] > >> d.setdefault(k, factory=list).append(v) ? > > > > That is somewhat nice and backwards compatible too. > >-1 > >How is it more expressive than d.setdefault(k, []).append(v)? As >far as I can see, it's longer and contains an extra obscure(ish) >term (factory). It's more expressive because it allows lazy evaluation: the list isn't created unless a new one is needed. For lists, that's not such a big deal. Indeed, it's entirely possible that the cost of adding the keyword argument to the function call would outweigh the cost of creating and discarding an emtpy list. But, when using a dictionary as a cache for an expensive computation, this notation is much more compact than writing an if-then or try-except block to do the same thing. Even so, compactness is actually less the point than clarity. The factory idiom is more readable (IMO) because it gets out of the way of the point of the code. It says, "oh by the way, the default for new members of 'd' is to be a new list, and now let's get on with what we're going to do with it."

1 0