Python-Dev February 2001

python-dev@python.org

63 participants
171 discussions

Perverse nesting bug
by Tim Peters 03 Feb '01

03 Feb '01

SF bug reporting is still impossible. Little program: def f(): print "outer f.a is", f.a def f(): print "inner f.a is", f.a f.a = 666 f() f.a = 42 f() I'm not sure what I expected it to do, but most likely an UnboundLocalError (the local f hasn't been bound to yet at the time "print outer" executes). In reality it prints: outer f.a is and then blows up with a null-pointer dereference, here: case LOAD_DEREF: x = freevars[oparg]; w = PyCell_Get(x); Py_INCREF(w); /***** THIS IS THE GUY *****/ PUSH(w); break; Simpler program with same symptom: def f(): print "outer f.a is", f.a def f(): print "inner f.a is", f.a f() I *do* get an UnboundLocalError if the body of the inner "f" is changed to "pass": def f(): # this one works fine! i.e., UnboundLocalError print "outer f.a is", f.a def f(): pass f() You'll also be happy to know that this one prints 666 twice (as it should): def f(): def f(): print "inner f.a is", f.a f.a = 666 f() print "outer f.a is", f.a f.a = 42 f() python-gets-simpler-each-release<wink>-ly y'rs - tim

1 0

Generalized "from M. import X" was RE: Python 2.1 alpha 2 released)
by Tim Peters 03 Feb '01

03 Feb '01

I'm trying to *use* each new feature at least once. It looks like a multiday project <wink/sigh>. I remember reading the discussion about this one: [from (old!) NEWS] > ... > - Two changes to from...import: > > 1) "from M import X" now works even if M is not a real module; it's > basically a getattr() operation with AttributeError exceptions > changed into ImportError. but in practice it turns out I have no idea what it means. For example, >>> alist = [] >>> hasattr(alist, "sort") 1 >>> from alist import sort Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: No module named alist >>> No, I don't want to *do* that, but the description above makes me wonder what I'm missing. Or, something I *might* want to do (maybe, on my worst day, and on any other day I'd agree I should be shot for even considering it): class Random: def random(self): pass def seed(self): pass def betavariate(self): pass # etc etc _inst = Random() from _inst import random, seed, betavariate # etc, etc Again complains that there's no module named "_inst". So if M does not in fact need to be a real module, what *does* it need to be? Ah: sticking in sys.modules["alist"] = alist first does the (disgusting) trick. So, next gripe: I don't see anything about this in the 2.1a2 docs, although the Lang Ref's section on "the import statement" has always been vague enough to allow it. The missing piece: when the Lang Ref says something is "implementation and platform specific", where does one go to find out what the deal is for your particular implementation and platform? guess-not-to-NEWS<wink>-ly y'rs - tim

2 2

2.1a2 released
by Guido van Rossum 03 Feb '01

03 Feb '01

I noticed that the source tarball and Windows installer were in place on SF and ftp.python.org, so I've updated the webpages python.org and python.org/2.1/. Seems email is wedged again so I don't know when people will get this email and if there was something to wait for -- I presume not. I'll mail an official announcement out tomorrow. Going to bed now...! --Guido van Rossum (home page: http://www.python.org/~guido/)

1 0

Setup.local is getting zapped
by Skip Montanaro 03 Feb '01

03 Feb '01

Modules/Setup.local is getting zapped by some aspect of the build process. Not sure by what step, but mine had lines I added to it a few days ago, and nothing now. It should be treated as Modules/Setup used to be: initialize it if it's absent, don't touch it if it's there. The distclean target looks like the culprit: distclean: clobber -rm -f Makefile Makefile.pre buildno config.status config.log \ config.cache config.h setup.cfg Modules/config.c \ Modules/Setup Modules/Setup.local Modules/Setup.config I've been using it a lot lately to build from scratch, what with the new Makefile and setup.py. Since Setup.local is ostensibly something a user would edit manually and would never have useful content in it as distributed, I don't think even distclean should zap it. Skip

1 0

linuxaudiodev crashes
by Skip Montanaro 03 Feb '01

03 Feb '01

I've been getting this for awhile on my laptop (Mandrake 7.1): test test_linuxaudiodev crashed -- linuxaudiodev.error: (11, 'Resource temporarily unavailable') RealPlayer works fine so I suspect the infrastructure is there and functioning. Anyone else seeing this? Skip

1 0

Diamond x Jungle Carpet Python
by Rod 02 Feb '01

02 Feb '01

I have several Diamond x Jungle Capret Pythons for SALE. Make me an offer.... Go to: www.qnet20.com

3 2

Python 2.1 alpha 2 docs released
by Fred L. Drake, Jr. 02 Feb '01

02 Feb '01

The documentation for the Python 2.1 alpha 2 release is now available. View it online at: http://python.sourceforge.net/devel-docs/ (This version will be updated as the documentation evolves, so will be updated beyond what's in the downloadable packages.) Downloadable packages in many formats are also available at: ftp://ftp.python.org/pub/python/doc/2.1a2/ Please avoid printing this documentation -- it's for the alpha, and could waste entire forests! Thanks to everyone who has helped improve the documentation! As always, suggestions and bug reports are welcome. For more instructions on how to file bug reports and where to send suggestions for improvement, see: http://python.sourceforge.net/devel-docs/about.html -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Digital Creations

1 0

Re: [Python-Dev] Benchmarking "fun" (was Re: Python 2.1 slower than 2.0)
by Michael Hudson 02 Feb '01

02 Feb '01

"M.-A. Lemburg" <mal(a)lemburg.com> writes: > > My conclusion? Python 2.1 is slower than Python 2.0, but not by > > enough to care about. > > What compiler did you use and on which platform ? Argh, sorry; I meant to put this in! $ uname -a Linux atrus.jesus.cam.ac.uk 2.2.14-1.1.0 #1 Thu Jan 6 05:12:58 EST 2000 i686 unknown $ gcc --version 2.95.1 It's a Dell Dimension XPS D233 (a 233MHz PII) with a reasonably fast hard drive (two year old 10G IBM 7200rpm thingy) and quite a lot of RAM (192Mb). [snip] > AFAIR, Vladimir's malloc implementation favours small objects. > All number objects (except longs) fall into this category. Well, longs & complex numbers don't do any free list handling (like floats and int do), so I see two conclusions: 1) Don't add obmalloc to the core, but do simple free list stuff for longs (might be tricky) and complex nubmers (this should be a no-brainer). 2) Integrate obmalloc - then maybe we can ditch all of that icky freelist stuff. > Perhaps we should think about adding his lib to the core ?! Strikes me as the better solution. Can anyone try this on Windows? Seeing as windows malloc reputedly sucks, maybe the differences would be bigger. Cheers, M. -- Our lecture theatre has just crashed. It will currently only silently display an unexplained line-drawing of a large dog accompanied by spookily flickering lights. -- Dan Sheppard, ucam.chat (from Owen Dunn's summary of the year)

9 15

Showstopper in import?
by Tim Peters 02 Feb '01

02 Feb '01

Turns out IDLE no longer runs. Starting at line 88 of Tools/idle/EditorWindow.py we have this class defn: class EditorWindow: from Percolator import Percolator from ColorDelegator import ColorDelegator from UndoDelegator import UndoDelegator from IOBinding import IOBinding import Bindings from Tkinter import Toplevel from MultiStatusBar import MultiStatusBar about_title = about_title ... This leads to what looks like a bug (if we're to believe the error msg, which doesn't mean what it says): C:\Pyk>python tools/idle/idle.pyw Traceback (most recent call last): File "tools/idle/idle.pyw", line 2, in ? import idle File "C:\PYK\Tools\idle\idle.py", line 11, in ? import PyShell File "C:\PYK\Tools\idle\PyShell.py", line 15, in ? from EditorWindow import EditorWindow, fixwordbreaks File "C:\PYK\Tools\idle\EditorWindow.py", line 88, in ? class EditorWindow: File "C:\PYK\Tools\idle\EditorWindow.py", line 90, in EditorWindow from Percolator import Percolator SyntaxError: 'from ... import *' may only occur in a module scope Hit return to exit... C:\Pyk> Sorry for the delay in reporting this! I've had other problems with the Windows installer (all fixed now), and IDLE *normally* executes pythonw.exe on Windows, which tosses error msgs into a bit bucket. So all I knew was that IDLE "didn't come up", and took the high-probability guess that it was due to some other problem I was already tracking down. Lost that bet.

5 9

Doc tree frozen for 2.1a2
by Fred L. Drake, Jr. 02 Feb '01

02 Feb '01

The Doc/ tree in the Python CVS is frozen until Python 2.1a2 has been released. No further changes should be made in that part of the tree. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Digital Creations

1 0

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Python-Dev February 2001