Mailman 3 March 2003 - Python-Dev

Re: [Python-Dev] module extension search order - can it be changed?
by Bill Bumgarner 03 Mar '03

03 Mar '03

On Tuesday, Feb 25, 2003, at 15:04 US/Eastern, python-dev-request(a)python.org wrote: > python23.zip is good for end users of programs written in Python, but > not so good for Python programmers: AFAIK it won't show source lines > in tracebacks for modules loaded from the zip file. Speaking entirely from a point of ignorance, why are the source line #s not shown for frames that are implemented in modules loaded from zipimport? Assuming the ZIP archive could be exactly identical to what one might find in /usr/lib/python2.3/, the zip could contain all the py + pyc as found in the normal library? As such, it would be trivial for the developer to unzip the zip into-- for example-- /tmp/ for reference purposes. Assuming the developer has a copy of the 2.3 source lying around and has the zip with just the PYC, the lines numbers are still very useful. All things considered, I would think it would be highly desirable for the developer's Python development environment to be as much like a stock deployment environment as possible. Java made a grave mistake in this regard -- the whole class loader mechanism can cause massive problems-- very annoying and hard to debug problems-- when moving code from a development environment into deployment if the class loader that loads a particular class changes between the two environments. b.bum

7 8

Changes to logging in CVS
by Vinay Sajip 03 Mar '03

03 Mar '03

I see that recent changes were made in logging/__init__.py to replace the use of "apply(func, args)" with "func(*args)". Doesn't this cause "invalid syntax" problems with 1.5.2? I explicitly coded using apply because I thought it was needed for 1.5.2. There are a few places where I've eschewed use of +=, for the same reason. Any chance we could change back to using apply()? Regards Vinay

3 3

Weekly Python Bug/Patch Summary
by Skip Montanaro 02 Mar '03

02 Mar '03

Bug/Patch Summary ----------------- 342 open / 3393 total bugs (-16) 125 open / 1999 total patches (+5) New Bugs -------- Let assign to as raise SyntaxWarning as well (2003-02-23) http://python.org/sf/691733 LibRef 4.2.1: {m,n} description update (2003-02-23) http://python.org/sf/692016 tkinter.createfilehandler dumps core (2003-02-24) http://python.org/sf/692416 new.function() leads to segfault (2003-02-25) http://python.org/sf/692776 python always searches python23.zip (2003-02-25) http://python.org/sf/692884 new.function ignores keyword arguments (2003-02-25) http://python.org/sf/692959 Python does not build --with-pydebug on Tru64 with vendor cc (2003-02-25) http://python.org/sf/693094 2.3a2 site.py non-existing dirs (2003-02-25) http://python.org/sf/693255 2.3a2 import after os.chdir difference (2003-02-25) http://python.org/sf/693416 licence allowed, but doesn't work (2003-02-25) http://python.org/sf/693470 Can't multiply str and bool (2003-02-26) http://python.org/sf/693955 email.Parser trashes header (2003-02-26) http://python.org/sf/693996 os.popen() hangs on {Free,Open}BSD (2003-02-26) http://python.org/sf/694062 Python 2.3a2 Build fails on HP-UX11i (2003-02-27) http://python.org/sf/694431 setup.py imports pwd before it's built if HOME not set (2003-02-27) http://python.org/sf/694812 complex_new does not always respect subtypes (2003-03-01) http://python.org/sf/695651 Problems with non-greedy match groups (2003-03-01) http://python.org/sf/695688 New Patches ----------- Use datetime in _strptime (2003-02-23) http://python.org/sf/691928 fix bug 625698, speed up some comparisons (2003-02-25) http://python.org/sf/693221 fix for bug 639806: default for dict.pop (2003-02-26) http://python.org/sf/693753 fix for bug 672614 :) (2003-02-28) http://python.org/sf/695250 environment parameter for popen2 (2003-02-28) http://python.org/sf/695275 fix bug 678519: cStringIO self iterator (2003-03-01) http://python.org/sf/695710 Closed Bugs ----------- Compiler complaints in posixmodule.c (2001-11-28) http://python.org/sf/486434 import with undefineds can crash python (2001-12-02) http://python.org/sf/488184 mkcwproject: custom __initialize routine (2001-12-13) http://python.org/sf/492465 macfs.FSSpec and Carbon.File.FSSpec fail for "new" files (2002-07-24) http://python.org/sf/585923 OSA Python integration (2002-07-26) http://python.org/sf/586998 IDE should have "open recent" menu (2002-09-11) http://python.org/sf/607810 IDE output window (2002-09-11) http://python.org/sf/607821 IDE - Breakpoints don't stick to lines (2002-09-11) http://python.org/sf/608085 unicode alphanumeric regexp bug (2002-09-16) http://python.org/sf/610299 Reorganize MacPython resources on OSX (2002-10-19) http://python.org/sf/625725 remove debug prints from macmain.c (2002-11-08) http://python.org/sf/635570 ic module "path too long" error (2002-11-26) http://python.org/sf/644243 dynload_next needs better errors (2002-12-12) http://python.org/sf/652590 Compiling C sources with absolute path bug (2003-01-15) http://python.org/sf/668662 after using pdb readline does not work correctly (2003-01-28) http://python.org/sf/676342 Can't build C ext on OS X with 'altinstall' python (2003-01-29) http://python.org/sf/677293 python.exe expected in extension builds (2003-01-30) http://python.org/sf/677753 plistlib.py selftest fails (2003-02-07) http://python.org/sf/682317 Future division breaks mpz (2003-02-16) http://python.org/sf/687654 Bundlebuilder needs to pre-convert resource files (2003-02-17) http://python.org/sf/688007 macresource should handle readonly applesingle files (2003-02-17) http://python.org/sf/688011 IDLE does not work on Mac OS X (2003-02-17) http://python.org/sf/688266 64-bit int and long hash keys incompatible (2003-02-19) http://python.org/sf/689659 Docs page has no PEPs link (2003-02-19) http://python.org/sf/689826 2.3a2 build fails under IRIX 6.5 (2003-02-20) http://python.org/sf/690012 test_posix fails when run in non-interactive mode (2003-02-20) http://python.org/sf/690081 sys.last_type is missing (2003-02-20) http://python.org/sf/690109 lines run together on input (2003-02-20) http://python.org/sf/690285 2.3a2 Sol8 make fails at _iconv_codec. (2003-02-20) http://python.org/sf/690309 apply fails to check if warning raises exception (2003-02-20) http://python.org/sf/690435 _POSIX_C_SOURCE redefined (2003-02-21) http://python.org/sf/691005 shutil.copytree documentation bug (2003-02-22) http://python.org/sf/691276 codecs.open(filename, 'U', 'UTF-16') corrupts text (2003-02-22) http://python.org/sf/691291 Closed Patches -------------- Patch for sre bug 610299 (2002-11-04) http://python.org/sf/633359 array.append is sloooow (2003-02-16) http://python.org/sf/687598 2.3 .spec file for building RPMs. (2003-02-18) http://python.org/sf/688584

1 0

Traceback problem
by Christian Tismer 02 Mar '03

02 Mar '03

Hi py-dev, I got a problem report for Stackless today, that it seems to leak with tracebacks. After trying other Python versions, I found out that this is a "feature" of Python and not related to Stackless. The problem becomes only more visible, since people are keeping thousands of threads alive. Here the problem: When an exception has been raised in a frame, and it already is handled in an except clause, the exception is not cleared out from tstate and also stays alive in the frame object. Only when the frame is left, eval_frame calls reset_exc_info(tstate); which clear all these, breaking cycles. Question: Does this need to be so, and for what reason? Would it be equivalent if I cleared error info in the context of a finally: ? If not, please give me advice how to solve this problem. It exists in all long-running frames which have seen exceptions. Thanks a lot - chris -- Christian Tismer :^) <mailto:tismer@tismer.com> Mission Impossible 5oftware : Have a break! Take a ride on Python's Johannes-Niemeyer-Weg 9a : *Starship* http://starship.python.net/ 14109 Berlin : PGP key -> http://wwwkeys.pgp.net/ work +49 30 89 09 53 34 home +49 30 802 86 56 pager +49 173 24 18 776 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/

7 37

python-dev from 2003-02-16 through 2003-02-28
by Brett Cannon 02 Mar '03

02 Mar '03

Since this is falling on the weekends, you guys have until Monday night to tell me how I fouled up. +++++++++++++++++++++++++++++++++++++++++++++++++++++ python-dev Summary for 2003-02-16 through 2003-02-28 +++++++++++++++++++++++++++++++++++++++++++++++++++++ .. _comp.lang.python: .. _rest: .. _last summary: ====================== Summary Announcements ====================== Nothing specific about the Summary to mention. I am starting to lean more and more towards starting summaries out in Quickies_ and then making them a full-fledged summary when they end up requiring more than a short paragraph of explanation. Helps me keep my sanity since I plan on sticking with having some summarization for every thread on python-dev. But this summary is on the lean side because traffic was lower than normal. I am sure this is in reaction to what happened last month with the massive amount of emails and various negativity that sprung up around the list. Made my life easier. =) PyCon_ is moving forward! Early-bird registration is over, but regular registration for $200 is still available. It has already shaped up to be a fun conference. If you come you can hear me make a fool of myself trying to teach the conference reST_. =) T-shirts are also available so even if you don't go to the conference you can buy a shirt at http://www.cafeshops.com/pycon and fool people into thinking your went. =) As for the `pre-PyCon sprint`_, that is also shaping up. There is already a sprint for Zope_, Twisted_, and Webware_. And now there is a sprint in the works for working on the Python core! If you are interested just <XXX: waiting for Guido to tell me how he wants to be contacted>. .. _PyCon: http://www.python.org/pycon/ .. _pre-PyCon sprint: http://www.python.org/cgi-bin/moinmoin/SprintPlan .. _Zope: http://www.zope.org/ .. _Twisted: http://twistedmatrix.com/ .. _Webware: http://webware.sourceforge.net/ =========================== `RELEASED: Python 2.3a2`__ =========================== __ http://mail.python.org/pipermail/python-dev/2003-February/033537.html Guido released `Python 2.3a2`_ on Feb. 19. Please download it, run the regression tests, and then test some of your own code. The more bugs we can squash before we hit 2.3b1 the better. .. _Python 2.3a2: http://www.python.org/2.3/ =================================== `new format codes for getargs.c`__ =================================== __ http://mail.python.org/pipermail/python-dev/2003-February/033579.html Thomas Heller implemented a new 'k' format code for `getargs.c`_ that ccepts integers or longs, does no range checking, and returns the lower bits in an unsigned long". After Tim Peters said that tests should be added to `_testcapimodule.c`_ the conversation was moved over to http://www.python.org/sf/595026 . .. _getargs.c: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Pytho… .. __testcapimodule.c: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Modul… ===================================== `assymetry in descriptor behavior`__ ===================================== __ http://mail.python.org/pipermail/python-dev/2003-February/033583.html This summary is going to assume you understand descriptor's. If you don't read `What's New in 2.2`_ for a nice, simple overview or `PEP 252`_ for the technical explanation (the initial email for this thread has simple code showing how descriptor's are used). If you have ever been interested how property(), classmethod(), and staticmethod() work this will tell you. David Abrahams wondered why it was possible to invoke a descriptor's __get__() from either the class it is defined in or an instance of that class while __set__() for the same descriptor cannot be called from the class directly without having defined the descriptor a second time in the metaclass; David thought this was a little difficult. He also asked about the arguments to the descriptor API methods. Guido responded by saying that it wasn't difficult considering you could do it and that Python was pulling something off with a single notation (by using '.' for class and instance accesses) that C++ uses two notations for ('.' and '::'). As for the arguments to the various methods, they are as follows: __get__(self, obj, type) 'self' gets bound to the descriptor instance. When called for an class, obj = None while for an instance it is bound to the instance containing the descriptor. 'type' is set to the class that has the descriptor regardless of what context the descriptor is being called. The duality is so that descriptors can be happy being called either just on an instance or just a class (such as classmethod()). __set__(self, obj, value) 'self' is the descriptor, obj is the instance, and 'value' is what what the assignment is being passed. As mentioned above, this only works with classes if you create the descriptor *twice*; once in the class and once in the class's metaclass. __delete__(self, obj) Guess what gets bound to these parameters? =) A historical note: Guido said "In an early alpha release it was actually __del__, but that didn't work very well. :-)" for obvious reasons. David also submitted a doc patch for this so we are now one step closer to having new-style classes documented. Still, there is work to be done and if you care to help please do so. .. _What's New in 2.2: http://www.python.org/doc/2.2.1/whatsnew/sect-rellinks.html#SECTION00032000… .. _PEP 252: http://www.python.org/peps/pep-0252.html ====================== `Bytecode analysis`__ ====================== __ http://mail.python.org/pipermail/python-dev/2003-February/033663.html Splinter threads: - `Bytecode idea <http://mail.python.org/pipermail/python-dev/2003-February/033693.html>`__ - `Code Generation Idea <http://mail.python.org/pipermail/python-dev/2003-February/033692.html>`__ - `Dynamic bytecode analysis <http://mail.python.org/pipermail/python-dev/2003-February/033752.html>`__ - `new bytecode results <http://mail.python.org/pipermail/python-dev/2003-February/033775.html>`__ Damien Morton posted some opcode statistics and tried to get better performance out of `ceval.c`_ by coming up with a way to do a LOAD_FAST_n call (LOAD_FAST pushes a variable on to the stack) and to cut back on the size of .pyc files. Nothing panned out very much, though (all the benchmarking was done using Pystone_). Guido said that Christian Tismer's idea of changing some of the rarely-used opcodes to function calls and moving them out of the 'switch' statement might get some performance. Christian also thought that some work could be done to speed up calls that involve a ``goto fast_next_opcode`` call. Changing ceval.c to using a jump table instead of a switch also did not pan out. Jeremy Hylton spoke to let people know that sometimes having an opcode call out to a function is not necessarily slower then having the code in the switch statement. He said it depended on how much work the opcode had to do and "lots of other hard-to-predict effects" in terms of memory and generated machine code. Jeremey also reminded people that there is patch out there to use the Pentium's cycle counter to find out how many cycles is spent on each pass through the mainloop. Guido also said that "If you really want fame and fortune, try designing a more representative benchmark". AM Kuchling requested to be notified when someone decided to take on this project. Skip Montanaro pointed out that he has "an XML-RPC server available to which applications can connect and upload their dynamic opcode frequencies" at http://manatee.mojam.com:7304 . Compile with "DYNAMIC_EXCUTION_PROFILE and DXPAIRS defined" and fetch the info from the sys_ module (it's undocumented, but it looks like you can get execution info from sys.getdxp()). If you are interested in how to use Skip's server, see http://mail.python.org/pipermail/python-dev/2003-February/033767.html . Damien Morton made his modified source code available at http://www.bitfurnace.com/python/modified-source.zip and asked people give it a try and report back to him their results. Dan Sugalski suggested putting opcode that tends to execute in pairs closer together so that they would have a better chance of being in the cache. It seemed that doing any mass opcode adding made things slower since the switch got larger and thus made cache hits harder to come by. Various ideas of how to rearrange things so that the switch was not as large were suggested and are most likely still being tested. .. _ceval.c: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Pytho… .. _Pystone: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Lib/t… .. _sys: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Pytho… ========= Quickies ========= `CALL_ATTR, A Method Proposal <http://mail.python.org/pipermail/python-dev/2003-February/033410.html>`__ Finn Bock added one last comment to this thread from the `last summary`_ about how the proposed implementation of a CALL_ATTR bytecode was how Jython_ handled attribute calls. `[Python-checkins] python/dist/src/Misc NEWS,1.660,1.661 <http://mail.python.org/pipermail/python-dev/2003-February/033466.html>`__: `Package Install Manager for Python <http://mail.python.org/pipermail/python-dev/2003-February/033467.html>`__ We learn some people take offense to the word pimp (to the point of considering them rapists), while others think it is fine ("a pretty respectable profession [in Amsterdam]. Definitely higher standing than a cab driver, somewhat on par with a coffeeshop owner"). `incorrect regression tests <http://mail.python.org/pipermail/python-dev/2003-February/033469.html>`__ Neal Norwitz discovered some regresssion tests that weren't being executed. We also learn that it is best for regression test modules to define a test_main() function that executes all the tests then having the tests run as a side-effect of importation (prevents the import lock from being held). `non-binary operators <http://mail.python.org/pipermail/python-dev/2003-February/033470.html>`__ Hold-over from the `last summary`_ when discussing whether the ternary operator could be just chained binary operators. `Import lock knowledge required! <http://mail.python.org/pipermail/python-dev/2003-February/033436.html>`__ Another hold-over from the `last summary`_; Eric Jones says he wouldn't mind more fine-grained import locking. `various unix platform build/test issues <http://mail.python.org/pipermail/python-dev/2003-February/033482.html>`__ Neal Norwitz brought to the attention of python-dev some issues that were preventing Python from compiling on some platforms. `308: the debate is petering out <http://mail.python.org/pipermail/python-dev/2003-February/033484.html>`__ Samuele Pedroni posted some new stats on the `PEP 308`_ debate going on at `comp.lang.python`_. `[rfc] map enhancement <http://mail.python.org/pipermail/python-dev/2003-February/033486.html>`__ Ludovic Aubry proposed a change to map(), but his use-case was eliminated quickly when it was pointed out he could just rewrite his map() or use list comprehensions. `Python 2.3a2 release today? <http://mail.python.org/pipermail/python-dev/2003-February/033489.html>`__ Guido asked if anyone objected to releasing Python 2.3a2 on Feb. 18. Jack Jansen asked if Guido could wait a day and he said yes. `test_timeout fails on Win98SE <http://mail.python.org/pipermail/python-dev/2003-February/033515.html>`__ The title of the thread states what the issue was and it got resolved. `privacy in log files? <http://mail.python.org/pipermail/python-dev/2003-February/033530.html>`__ Guido discovered a comment about not using `PyErr_WarnExplicit()`_ because there was a worry of having code put into a log file. Discussion seemed to end on the idea that it wasn't so much security but throwing a text editor for a loop because of possible non-ASCII getting put into a log file. `What happened to fixed point? <http://mail.python.org/pipermail/python-dev/2003-February/033539.html>`__ David LeBlanc asked about the status of FixedPoint_ getting into the stdlib. Raymond Hettinger said he would be getting to it soon. `test_posix, test_random failing <http://mail.python.org/pipermail/python-dev/2003-February/033541.html>`__ I bet you can figure out what this thread is about. SF tracker items have now been created. `pickling of large arrays <http://mail.python.org/pipermail/python-dev/2003-February/033543.html>`__ Ralf Grosse-Kunstle asked if there was a way to minimize the amount of buffering needed to buffer an array object. It was pointed out that writing a __reduce__() method that used an iterator would prevent the need to do any major buffering. The idea of having a custom append() method for objects to return was also suggested, but didn't get resolved. `Cygwin build failing <http://mail.python.org/pipermail/python-dev/2003-February/033555.html>`__ A problem with builing under Cygwin was fixed by rebasing the system. `2.3a2 problem: iconv module raising RuntimeError <http://mail.python.org/pipermail/python-dev/2003-February/033570.html>`__ `_iconv_codec.c`_ was raising RuntimeError when it was more proper to raise ImportError. It's been fixed. `SCO Open Server 5.0.x thread support <http://mail.python.org/pipermail/python-dev/2003-February/033575.html>`__ Someone asked for help compiling on SCO with thread support. He was redirected to `comp.lang.python`_ to get help. `call for Windows developers <http://mail.python.org/pipermail/python-dev/2003-February/033582.html>`__ Thomas Heller asked for help from some Windows experts with the goal of getting ctypes_ so that one can write ActiveX controls in Python. `tuning up... <http://mail.python.org/pipermail/python-dev/2003-February/033585.html>`__ Andrew MacIntyre sent some performance numbers for OS/2 EMX; about 10% performance improvement from Python 2.2 with -O compared to stock Python 2.3 (-O in 2.3 does not do much since the SET_LINENO opcode was removed entirely from Python). `Weekly Python Bug/Patch Summary <http://mail.python.org/pipermail/python-dev/2003-February/033586.html>`__ Skip Montanaro's weekly reminder that Python is not perfect yet. =) `Needed: regexp maintainer <http://mail.python.org/pipermail/python-dev/2003-February/033590.html>`__ Guido asked for someone to step forward to take over for the re_ module. `_iconv_codec <http://mail.python.org/pipermail/python-dev/2003-February/033602.html>`__ Guido asking what that `_iconv_codec.c`_ module was for (answer: it's a wrapper for the iconv(3) POSIX module). `python/dist/src configure,1.279.6.17... <http://mail.python.org/pipermail/python-dev/2003-February/033596.html>`__ Neil Schemenauer asked what the whitespace rules were for pre-processor directives (e.g., #include, #define, etc.). Tim Peters (the residential C standards know-it-all) said that "Spaces and horizontal tabs are fine before '#', and between '#' and the directive name". `rename bsddbmodule.c to bsddb185.c <http://mail.python.org/pipermail/python-dev/2003-February/033645.html>`__ `bsddbmodule.c`_ is now going to compile to the module bsddb185. `Scheduled downtime for mail.python.org <http://mail.python.org/pipermail/python-dev/2003-February/033651.html>`__ mail.python.org was scheduled to go down on 2003-02-26 at 10:00 EST. `Traceback problem <http://mail.python.org/pipermail/python-dev/2003-February/033607.html>`__ Christian Tismer wanted a way to clear the traceback information stored by `sys.exc_info()`_ to be cleared on-demand since it is kept around as long as the frame is alive. Kevin Jacobs wrote a patch to implement this feature and named is sys.exc_clear(). And a word of warning to anyone who stores the info returned by sys.exc_info(); it creates a cycle with the frame and thus can create a huge chunk of memory to be held so make sure to delete the info when you are done with it. `module extension search order - can it be changed? <http://mail.python.org/pipermail/python-dev/2003-February/033626.html>`__ Skip Montanaro realized that most failed stat() calls occur because the extension search order goes C extension and then Python module; most modules are written in Python and thus the stat() call for a C extension of a module name tends to fail. Guido said it is this way so that if the build of a C extension fails a same-named Python module can be installed instead. This also lead to Skip possibly coming up with a build option of creating a zip archive of the stdlib at install time to minimize failed stat() calls. `Writing a mutable object problem with __setattr__ <http://mail.python.org/pipermail/python-dev/2003-February/033627.html>`__ Aleksandor Totic asked about classes and an object-persistence setup he was designing. You can learn about __setattr__() and that do find out whether an instance is new-style or classic based on whether it has a __class__ attribute (new-style has this). `Re: some preliminary timings <http://mail.python.org/pipermail/python-dev/2003-February/033634.html>`__ Skip Montanaro discovering that importing email_ takes a while. `GIL Pep commentary <http://mail.python.org/pipermail/python-dev/2003-February/033657.html>`__ David Abrahams basically saying he likes `PEP 311`_. `test_re failing again on Mac OS X <http://mail.python.org/pipermail/python-dev/2003-February/033668.html>`__ Someone thought `test_re`_ was failing again on OS X when it turns out it was an isolated incident. `Slowdown in Python CVS <http://mail.python.org/pipermail/python-dev/2003-February/033756.html>`__ Someone thought that Python had slowed down for some reason; turned out to be isolated. If you ever need to check out a CVS copy from a past date, execute ``cvs update -D '24 Feb 2003'`` (with the proper date, of course). `Some questions about maintenance of the regular expression code. <http://mail.python.org/pipermail/python-dev/2003-February/033699.html>`__: `New regex syntax? <http://mail.python.org/pipermail/python-dev/2003-February/033735.html>`__ Gary Herron stepped up to say he was interested in taking over maintenance of the re_ module. He asked, though, how to handle bug reports about ``(.*)?`` and hitting the recursion limit (a patch materialized that solved the recursion issue for non-greedy quantifiers for the common case). The suggestion of coming up with a new syntax for regexes came up but was stopped from forming on the list since that would take "over all available bandwidth in python-dev" as Guido pointed out. Can still be discussed in other forums, though... `bug? classes whose metclass has __del__ are not collectible <http://mail.python.org/pipermail/python-dev/2003-February/033764.html>`__ Answer: no. Reason: "The GC implementation has a good reason for this; someone else may be able to explain it". `Introducing Python <http://mail.python.org/pipermail/python-dev/2003-February/033783.html>`__ Gustavo Niemeyer sent a link to an mpeg promoting Python at http://www.ibiblio.org/obp/pyBiblio/pythonvideo.php . If you ever had any desire to see what some of the guys from PythonLabs look and sound like and you are not going to PyCon_ you can now quench your curiosity. `syntax for funcion attributes <http://mail.python.org/pipermail/python-dev/2003-February/033800.html>`__ Someone suggested a new syntax for being to access function attributes but was told that it didn't look like it would fly. .. _Jython: http://www.jython.org/ .. _PEP 308: http://www.python.org/peps/pep-0308.html .. _PyErr_WarnExplicit(): http://www.python.org/dev/doc/devel/api/exceptionHandling.html#l2h-92 .. _FixedPoint: http://fixedpoint.sf.net/ .. __iconv_codec.c: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Modul… .. _ctypes: http://starship.python.net/crew/theller/ctypes.html .. _re: http://www.python.org/dev/doc/devel/lib/module-re.html .. _bsddbmodule.c: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Modul… .. _sys.exc_info(): http://www.python.org/dev/doc/devel/lib/module-sys.html .. _email: http://www.python.org/dev/doc/devel/lib/module-email.html .. _PEP 311: http://www.python.org/peps/pep-0311.html .. _test_re: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/python/dist/src/Lib/t…

1 0

syntax for funcion attributes
by Mark Nottingham 01 Mar '03

01 Mar '03

Hello, I'm not a python-dev regular, so sorry if this is a FAQ. What's the status of defining a syntax for function attributes (PEP 232)? I'm using __doc__ to carry metadata about methods right now, but would very much like to use function attributes. However, without a specialized syntax, I'm stuck doing things like VeryLongMethodName.MetadataName = "foo" which is fine if it's a one-off, but I'd like others to use the code, and this isn't exactly a friendly mechanism. The proposals in the PEP would be fine; I was thinking something like def foo(a): """this is the docstring""" .this_is_a_function_attribute = 1 but that's just off the top of my head. I'm happy to do some work writing a PEP if there's some consensus about what syntax would be preferable. Cheers, -- Mark Nottingham

2 1

[663074] Codec registry
by Gustavo Niemeyer 01 Mar '03

01 Mar '03

Can someone please review the proposed solution to bug #663074? If accepted, should it be backported to 2.2.3 as well? -- Gustavo Niemeyer [ 2AAC 7928 0FBF 0299 5EB5 60E2 2253 B29A 6664 3A0C ]

1 0