Mailman 3 November 2004 - Python-Dev

enhanced gdbinit file - looking for Python+Emacs+gdb users
by Skip Montanaro Nov. 21, 2004

Nov. 21, 2004

I got a little carried away with the gdbinit file that lives in the Python distribution at Misc/gdbinit today. I decided there's no particular reason that gdb shouldn't display the current Python file when moving up and down the C stack any time it encounters PyEval_EvalFrame. After a little digging I realized this would be pretty easy. I made two changes to the gdbinit file: 1. I wrote a lineno command for gdb that calculates and prints the current Python line number. (It's … [View More]

2 1

Re: [Python-Dev] Re: syntactic shortcut - unpack to variably sizedlist
by Nick Coghlan Nov. 20, 2004

Nov. 20, 2004

Raymond Hettinger wrote: >>I have no great problem with leaving the a, b, *c = L idea unPEPed if >>there is >>interest in leaving the idea 'open', though. > > > Yes. I would like to have it left open. OK, here's what I'll do in the next draft of the proposed PEP (PEPP?): 1. Add a discussion of the advantages of iunpack over islice: - guaranteed minimum length (handy for use with tuple unpacking) - return the iterator as the final object (this is nicer when … [View More]

1 0

Re: [Python-Dev] Re: syntactic shortcut - unpack to variably sizedlist
by Nick Coghlan Nov. 20, 2004

Nov. 20, 2004

Raymond Hettinger wrote: >>Officially killing that syntax was actually one of the stated goals of > > the > >>PEP. > > I don't think that is a worthy goal. The is some merit to the a,b,*c > syntax. When the time is ripe, it should have its day in court. There's currently 3 things in the PEP draft: 1. Allow slice objects as arguments list.pop and array.pop 2. Add itertools.iunpack 3. Record the rejection of a, b, *c = L in a PEP (since it's been rejected three … [View More]

1 0

Re: [Python-Dev] Re: syntactic shortcut - unpack to variably sizedlist
by Nick Coghlan Nov. 20, 2004

Nov. 20, 2004

Raymond Hettinger wrote: > Also, the pep would likely kill the remote, but non-zero chance of ever > getting the a,b,*c syntax. IOW, the pep may be a step backwards. Officially killing that syntax was actually one of the stated goals of the PEP. However, the PEP editors would be well within their rights to reject the draft as 'lacking focus'. I wouldn't be offended given the whole 20 minutes it took to write it :) Cheers, Nick. -- Nick Coghlan | Brisbane, … [View More]

2 1

syntactic shortcut - unpack to variably sized list
by Johan Hahn Nov. 20, 2004

Nov. 20, 2004

Hi As far as I can tell from the archive, this has not been discussed before. This is the second time in less than a week that I have stumbled over the rather clumsy syntax of extracting some elements of a sequence and at the same time remove those from the sequence: >>> L = 'a b 1 2 3'.split(' ') >>> a,b,L = L[0], L[1], L[2:] I think it would be nice if the following was legal: >>> a,b,*L = 'a b 1 2 3'.split(' ') >>> a, b, L ('a', 'b', ['1', '2', '3']) … [View More]

9 23

print "%X" % id(object()) not so nice
by James Y Knight Nov. 20, 2004

Nov. 20, 2004

I think id() should never be returning a negative number. Both these behaviors are poor: In 2.3: >>> print "%X" % id(o) __main__:1: FutureWarning: %u/%o/%x/%X of negative int will return a signed string in Python 2.4 and up A5F48198 In 2.4: >>> print "%X" %id(o) -5FC84D08 Pointers are conventionally never treated or printed as signed. In 2.3 and before, it usually ended up okay, besides the warning, because "%X" had broken behavior. In 2.4, now it's ending up doing … [View More]

7 10

Confusion about os.urandom()
by Matthias Andreas Benkard Nov. 19, 2004

Nov. 19, 2004

Hello there. I was just reading through http://www.python.org/2.4/highlights.html and noticed the following: os.urandom() has been added for systems that support a source of random data (entropy) At first, I was a bit stunned about the choice of name here. Why would anyone call this method urandom()? That confused me a bit, for, AFAICS, under Linux at least, /dev/random is the entropy pool and /dev/urandom is a PRNG (or rather, a source of random numbers which falls back to a PRNG … [View More]

2 1

RELEASED Python 2.4, release candidate 1
by Anthony Baxter Nov. 19, 2004

Nov. 19, 2004

On behalf of the Python development team and the Python community, I'm happy to announce the first release candidate of Python 2.4. Python 2.4c1 is a release candidate - we'd greatly appreciate it if you could download it, kick the tires and let us know of any problems you find, but it is probably not suitable for production usage. At this point, we're particularly interested in build bugs. If you could grab the source archive, build it and then run the test suite, we'd appreciate it. … [View More]

2 2

Misinformation in highlights webpage
by Batista, Facundo Nov. 19, 2004

Nov. 19, 2004

In http://www.python.org/2.4/highlights.html it presents decimal between the "New or upgraded built-ins", while it should talk about it in "New or upgraded modules and packages". Should I post a bug or this is enough? (never know what to do regarding webpages). Thanks! Facundo Batista Desarrollo de Red fbatista(a)unifon.com.ar (54 11) 5130-4643 Cel: 15 5097 5024

1 0

python 2.3.5 release?
by Matthias Klose Nov. 18, 2004

Nov. 18, 2004

Python 2.3.4 was released on 2004-05-27. According to the bi-annual release schedule that would assume another release from the 2.3 branch this year. Are people still interested in a formal 2.3.5 release? At least the 2.3 branch does have a couple of patches worth making a release. Is there anything that needs to be added before a 2.3.5 release is scheduled, or should we wait for the 2.4 release to identify patches that need to be backported to a potential 2.3.5 release? Thanks for any comment, Matthias

5 5