Mailman 3 April 2003 - Python-Dev

Tagging the tree
by Guido van Rossum April 25, 2003

April 25, 2003

I'm tagging the CVS tree now. Please no more checkins until the release is announced or unless I specifically ask you! --Guido van Rossum (home page: http://www.python.org/~guido/)

1 0

Python 2.3b1 documentation
by Fred L. Drake, Jr. April 25, 2003

April 25, 2003

I've already formatted the documentation for Python 2.3b1; please don't touch the Doc directory until the final release has been announced. Thanks! -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation

1 0

Cryptographic stuff for 2.3
by A.M. Kuchling April 25, 2003

April 25, 2003

A while ago Paul Rubin proposed adding a Rijndael/AES module to 2.3. (AES = Advanced Encryption Standard, a block cipher that's likely to be around for a long time). Rubin wanted to come up with a nice interface for the module, and has posted some notes toward it. I have an existing implementation that's 2212 lines of code; I like the interface, but opinions may vary. :) Do we want to do anything about this for 2.3? A benefit is that AES is useful, and likely to remain so for the next 20 … [View More]

14 27

Re: PyRun_* functions
by wesley henwood April 25, 2003

April 25, 2003

How do I make certain that FILE* parameters are only passed to these functions if it is certain that they were created by the same library that the Python runtime is using? _________________________________________________________________

2 1

New test failure on Windows
by Tim Peters April 25, 2003

April 25, 2003

Last-second re changes don't appear to be going in the right direction <wink>: C:\Code\python\PCbuild>python ../lib/test/test_re.py Running re_tests test suite test_basic_re_sub (__main__.ReTests) ... ok test_constants (__main__.ReTests) ... ok test_escaped_re_sub (__main__.ReTests) ... ok test_flags (__main__.ReTests) ... ok test_limitations (__main__.ReTests) ... ERROR test_pickling (__main__.ReTests) ... ok test_qualified_re_split (__main__.ReTests) ... ok test_qualified_re_sub (… [View More]

5 10

draft PEP: Trace and Profile Support for Threads
by Jeremy Hylton April 25, 2003

April 25, 2003

I've been working a little on the trace module lately, trying to get it to work correctly with Zope. One issue that remains open is how to handle multi-threaded programs. The PEP below proposes a solution. Jeremy PEP: XXX Title: Trace and Profile Support for Threads Version: $Revision: 1.1 $ Last-Modified: $Date: 2002/08/30 04:11:20 $ Author: Jeremy Hylton <jeremy(a)alum.mit.edu> Status: Active Type: Standards Track Content-Type: text/x-rst Created: 22-Apr-2003 Post-History: 22-Apr-… [View More]2003 Abstract ======== This PEP describes a mechanism for attaching profile and trace functions to a thread when it is created. This mechanism allows existing tools, like the profiler, to work with multi-threaded programs. The new functionality is exposed via a new event type for trace functions. Rationale ========= The Python interpreter provides profile and trace hooks to support tools like debuggers and profilers. The hooks are associated with a single thread, which makes them harder to use in a multi-threaded environment. For example, the profiler will only collect data for a single thread. If the profiled application spawns new threads, the new threads will not be profiled. This PEP describes a mechanism that allows tools using profile and trace hooks to hook thread creation events. This mechanism would allow tools like the profiler to automatically instrument new threads as soon as they are created. The ability to hook thread creation makes a variety of tools more useful. It should allow them to work seamlessly with multi-threaded applications. The best alternative given the current interpreter support is to edit a multi-threaded application to manually insert calls to enable tracing or profiling. Background ========== There are two different hooks provided by the interpreter, one for tracing and one for profiling. The hooks are basically the same, except that the trace hook is called for each line that is executed but the profile hook is only called for each function. The hooks are exposed by the C API [1] and at the Python level by the sys module [2]. For simplicity, the rest of the section just talks about the trace function. A trace function [3] is called with three arguments: a frame, an event, and an event-dependent argument. The event is one of the following strings: "call," "line," "return," or "exception." The C API defines trace function that takes an int instead of a string to define the trace event. The sys.settrace() function sets the global trace function. A global trace function is called whenever a new local scope is entered. If the global trace function returns a value, it is used as the local trace function. If it returns None, no local tracing occurs. Thread creation event ===================== The proposed mechanism is to add a thread creation event called "thread" and PyTrace_THREAD. When thread.start_new_thread() is called, the calling thread's trace function is called with a thread event. The frame passed is None or NULL and the argument is the callable argument passed to start_new_thread(). If the trace function returns a value from the thread event, it is used as the global trace function for the newly created thread. Implementation ============== The bootstrap code in the thread module (Modules/threadmodule.c) must be extended to take trace functions into account. A thread's bootstate must be extended to include pointers to the trace function and its state object. The t_bootstrap() code must call the trace function before executing the boot function. Compatibility and Limitations ============================= An existing trace or profile function may be unprepared for the new event type. This may cause them to treat the thread event as some other kind of event. The thread event does not pass a valid frame object, because the frame isn't available before the thread starts running. Once the thread starts running, it is too late to generate the thread event. The hook is only available when a thread is created using the Python thread module. If a custom C extension calls PyThread_start_new_thread() directly, the trace function will not be called for that thread. It's hard to judge whether this behavior is good or bad. It is driven partly by implementation details. The implementation of PyThread_start_new_thread() can not tell when or if Python code will be executed by the thread. References ========== .. [1] Section 8.2, Profiling and Tracing, Python/C API Reference Manual (http://www.python.org/dev/doc/devel/api/profiling.html) .. [2] Section 3.1, sys, Python Library Reference (http://www.python.org/dev/doc/devel/lib/module-sys.html) .. [3] Section 9.2, How It Works (Python Debugger), Python Library Reference (http://www.python.org/dev/doc/devel/lib/debugger-hooks.html) Copyright ========= This document has been placed in the public domain. [View Less]

6 12

why is test_socketserver in expected skips?
by Skip Montanaro April 24, 2003

April 24, 2003

test_socketserver seems to be in all the expected skip lists except for (oddly enough) os2emx. It correctly bails if the network resource isn't set and the 2.2 branch version seems to complete for me on my Mac OS X system. When run like: % ./python.exe ../Lib/test/test_socketserver.py the 2.3 branch version fails because the network resource isn't enabled: Traceback (most recent call last): File "../Lib/test/test_socketserver.py", line 5, in ? test_support.requires('… [View More]

4 5

netrc.py
by Raymond Hettinger April 24, 2003

April 24, 2003

Bram Moolenaar > > Please at least do not produce the NetrcParseError when the > > "login" field is omitted. This can be done by changing the > > "else:" above "malformed %s entry" to "elif not password:". > > That is the minimal change to make this module work on my > > system. Bram is requesting netrc.py be modified to exclude entries without a login field. An example use case is for mail servers: machine mail password fruit If the change is … [View More]

5 7

vacation
by Neal Norwitz April 24, 2003

April 24, 2003

I'm going on vacation from Apr 26 - May 6. I will probably not be available during this period. Sometime in the next month or so, I plan to run valgrind and pychecker over everything. I should be done before beta2. Also, the snake farm still has some issues. I will try to improve the snake farm status in May or June. But if anybody wants to volunteer to fix any of the issues, feel free. :-) http://www.lysator.liu.se/xenofarm/python/latest.html Some test failures are: … [View More]

3 6

Changes to gettext.py for Python 2.3
by Barry Warsaw April 24, 2003

April 24, 2003

Hi I18n-ers, I plan on checking in the following changes to the gettext.py module for Python 2.3, based on feedback from the Zope and Mailman i18n work. Here's a summary of the changes, hopefully there aren't too many controversies <wink>. I'll update the tests and the docs at the same time. - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset … [View More]

3 13