Mailman 3 December 2004 - pypy-dev

Re: [pypy-dev] module writing
by Florian Bauer 15 Dec '04

15 Dec '04

Am 14.12.2004 um 19:13 schrieb Douglas McNeil: > > > Hey, Florian! > > I've just submitted a bug report describing some of the oddities in > binascii.b2a_qp, which is the only routine left which won't pass my > regression tests. I made the mistake of trying to implement the code > straight from rfc 1521 because the C was so ugly, only to discover the > C > does the weirdest things. > > Frustratingly, I had to throw most of my nice refactoring out the > window > and follow your advice to go from the Java. I can easily match the > behaviour for correct inputs with my original code, but (or so I've > discovered) it's almost impossible to match the behaviour for incorrect > inputs without following the original program logic to a T. :( > > When I hear back on whether the behaviour I've been wrestling with > imitating is a bug or not I can send you the finished product. :) > > > Doug (who's glad his supervisor doesn't read sourceforge) > > -- > Queen's University Astronomy Research Group > Planetary Dynamics Division "We create worlds." > Hey Doug, Are you aware that there is a pure python implementation of the quoted-printable stuff in the std lib (I think in quopri.py, but I cant check atm) I hope your supervisor doesn't find out about your sf activities ;-) I have my final presentation for my thesis today. That means, tomorrow I'll have some time for some python hacking. ciao Flo >

1 0

Re: [pypy-dev] module writing
by Florian Bauer 10 Dec '04

10 Dec '04

>Anyway, I'm finishing up the struct module now, though I'll have to see if >the java code has parts I should copy. I still have to convert >test_struct.py in the standard library to the pypy test format. (I admit >this test-driven development stuff takes getting used to.) > > > Congratulations. You seem to work faster than me at the moment. I'm still stuck with finishing my thesis. But I'll submit my binascii code before chrismas, I promise ;-) I wouldn't convert test_struct.py to pypy test format. I would just copy this file over from CPython. For binascii I copied test_binascii.py, and wrote a second test suite with more tests. I guess it will be easier to sync pypy with CPython in the future if pure python files like test_*.py are the same for both implementations. >I can't remember what state I left my binascii code in -- it sounded like >one of the simpler ones to do, I understand ASCII even if psyco makes my >head hurt :) -- and I stopped when I remembered all of a sudden that you >had called it. > >IIRC the uuencoding and hqx routines worked okay but the base64 routines >weren't working and I couldn't quite see why. I'll have a look on the >weekend, and if it's true that four of the six work then I'll send it to >you and maybe you can spot whatever's going on, or tell me that I'm going >in completely the wrong direction. > > Sounds great to me. Send me your stuff, and I'll merge it with mine and then submit it. Have a nice weekend, Florian

1 0

Switzerland sprint around Jan 22-29
by Armin Rigo 10 Dec '04

10 Dec '04

Hi all! The next sprint will take place in Leysin, in the Swiss pre-alps. The precise dates are not fixed yet, but it will almost certainly be during the week of the 22-29th January. Leysin is a village at an altitude of 1200 to 1400m. It is a skiing station, and also the place where I lived for 20 years. There are 2000 people in summer and 10000 in winter :-) but the sprint will be just before the most crowded periods of February. Of course at least one full day will be dedicated to winter sports! Both the sprint venue and the logding will be in a very spacious pair of chalets built specifically for bed&breakfast: http://www.ermina.ch/. Early warning: the internet connexion will be limited to a single 600Kb ADSL. I guess we can set up something to work around this, along the line of moving the whole repository to a local machine for the week. A bientot, Armin

3 2

Re: [pypy-dev] module writing
by Florian Bauer 09 Dec '04

09 Dec '04

Douglas McNeil <mcneil(a)astro.queensu.ca> schrieb am 09.12.04 00:24:36: > Per Laura's suggestion I figured I'd try to look at some of the pending > unpythoned C modules.. though Florian beat me to binascii.py, darn it! > > Should I follow Christian's suggestion and avoid generators in this stuff? > Before I remembered that binascii was already in the works I toyed with > reimplementing it, and half the functions use the same 8-to-6-to-8 bit > transforms with consequent code duplication. Can still be refactored > without generators, but is prettier with.. Hi Doug, I would be interested in seeing your binascii code. Maybe we can merge yours and mine? It seems that you took a different approach than me. I more or less translated the Jython versions of the different functions (Java is in my opinion much closer to python and much easier to read - no pointers ;-). I have not done much refactoring yet, I concentrated on writing test cases. Ciao Florian __________________________________________________________ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201

1 0

[patch] bitwise binary operators
by Olivier Dormond 09 Dec '04

09 Dec '04

Oops! Armin told me that nonneg means that we know for sure that the value is not negative (i.e. postive or null). In that case the xor behave differently. Hopefully this patch will do it right. Cheers, Olivier Index: pypy/annotation/binaryop.py =================================================================== --- pypy/annotation/binaryop.py (revision 7771) +++ pypy/annotation/binaryop.py (working copy) @@ -20,6 +20,7 @@ # XXX unify this with ObjSpace.MethodTable BINARY_OPERATIONS = set(['add', 'sub', 'mul', 'div', 'mod', + 'and_', 'or_', 'xor', 'getitem', 'setitem', 'inplace_add', 'inplace_sub', 'lt', 'le', 'eq', 'ne', 'gt', 'ge', 'is_', @@ -125,16 +126,17 @@ return SomeInteger(nonneg = int1.nonneg and int2.nonneg, unsigned = int1.unsigned or int2.unsigned) - def add((int1, int2)): - return SomeInteger(nonneg = int1.nonneg and int2.nonneg, - unsigned = int1.unsigned or int2.unsigned) + add = mul = div = mod = or_ = union - mul = div = mod = add - def sub((int1, int2)): return SomeInteger(unsigned = int1.unsigned or int2.unsigned) + def and_((int1, int2)): + return SomeInteger(nonneg = int1.nonneg or int1.nonneg, + unsigned = int1.unsigned or int2.unsigned) + xor = and_ + class __extend__(pairtype(SomeBool, SomeBool)): def union((boo1, boo2)):

3 3

[patch] bitwise binary operators
by Olivier Dormond 07 Dec '04

07 Dec '04

Hello, Here is a small patch that add the and_, or_ and xor bitwise operators. It also replaces the add method which is identical to union by a synonym. Cheers, Odie Index: pypy/annotation/binaryop.py =================================================================== --- pypy/annotation/binaryop.py (revision 7771) +++ pypy/annotation/binaryop.py (working copy) @@ -20,6 +20,7 @@ # XXX unify this with ObjSpace.MethodTable BINARY_OPERATIONS = set(['add', 'sub', 'mul', 'div', 'mod', + 'and_', 'or_', 'xor', 'getitem', 'setitem', 'inplace_add', 'inplace_sub', 'lt', 'le', 'eq', 'ne', 'gt', 'ge', 'is_', @@ -125,16 +126,19 @@ return SomeInteger(nonneg = int1.nonneg and int2.nonneg, unsigned = int1.unsigned or int2.unsigned) - def add((int1, int2)): - return SomeInteger(nonneg = int1.nonneg and int2.nonneg, - unsigned = int1.unsigned or int2.unsigned) + add = mul = div = mod = or_ = union - mul = div = mod = add - def sub((int1, int2)): return SomeInteger(unsigned = int1.unsigned or int2.unsigned) + def and_((int1, int2)): + return SomeInteger(nonneg = int1.nonneg or int1.nonneg, + unsigned = int1.unsigned or int2.unsigned) + def xor((int1, int2)): + return SomeInteger(nonneg = int1.nonneg ^ int1.nonneg, + unsigned = int1.unsigned or int2.unsigned) + class __extend__(pairtype(SomeBool, SomeBool)): def union((boo1, boo2)):

1 0

unlurking
by Douglas McNeil 06 Dec '04

06 Dec '04

Hi, all. Brief intro: Canadian astronomy graduate student, does lots of python programming, thinks pypy is a cool idea and has been lurking for a long time. :) Some of my codes are in C for speed reasons, but they're a lot uglier than the python equivalents would be.. I really wish there were a way to get C speed out of python without going the numarray/pyrex/weave routes, so the translator/annotator stuff interests me for reasons entirely unrelated to pypy itself. Numeric codes tend not to be very dynamic so static analysis should be able to go a long way. The translator code is surprisingly easy to read! It didn't take long before I had fun playing with flowgraph optimization. Just cheap hacks to do loop hoisting and remove more deadops, making dangerous assumptions all over the place, and adding a SomeFloat type to see how that works, but it was nice to see that after a lot of dir(this) and dir(that) to grok the data structure you get the hang of it. The flowgraph viewer helped a lot. I have a thousand questions but I should see what more I can learn from the code itself first before troubling anyone! Congratulations on getting the funding, and here's hoping Guido's wrong about what python 3.0's written in. :) Doug -- Queen's University Astronomy Research Group Planetary Dynamics Division "We create worlds."

1 0

EU funding is official!
by hpk＠trillke.net 06 Dec '04

06 Dec '04

Hi pypythonistas, lucky day! The EU signed the contract and the PyPy/EU projects starts, umm, started on 1st of December 2004! This means we have now two years of funding for PyPy to deliver research and implementation results. The funding will go to a number of people (through their respective organizations) who already are involved in the project for a long time. But this doesn't mean that there is not room for new fellow hackers especially with research interests! After our prototypical work we already completed we can be pretty confident that we can reach the ambitious goals that we promised to the EU. Nevertheless, it will be quite an adventure .. as if it hadn't been one already :-) My special thanks go to Laura who pushed us initially towards going for the funding and also supports the project in magnificient ways! But i think i wasn't wrong either in July 2003, when i was skeptical with respect to all the formal work and communication implications :-) I think that the support from the many pythonistas which e.g. materialized in our EU proposal and in the sprints certainly contributed a lot to winning the contract! Many thanks to Guido and Tim, especially! You are welcome any time to join the sprint marathons towards a new Python implementation :-) thanks & cheers, holger

6 5

Patch for autopath.py on windows
by Florian Schulze 06 Dec '04

06 Dec '04

Hi! I have attached a patch for autopath.py. It fixes the __clone function for windows. I don't know whether it still works on unix, but I think it should. Regards, Florian Schulze

2 2

Re: [pypy-dev] question about read only attributes of my file object
by Laura Creighton 05 Dec '04

05 Dec '04

In a message of Sat, 04 Dec 2004 17:15:24 GMT, Armin Rigo writes: >Hi Laura, > >On Sat, Dec 04, 2004 at 06:07:33PM +0100, Laura Creighton wrote: >> So -- do you really want me to use the properties? I now think they are >> icky. > >Ick! Yes! People who use __getattr__() or __setattr__() should be shot >without even waiting for dawn. Basically, they don't cooperate well with >the whole new-style class mechanisms. > >A bientot, > >Armin. But I am still going to need something for __getattr__(), I think. I mean, in the __init__ I have all of this stuff: self.fd = sio.DiskFile(name, mode) if mode in ['U', 'rU']: # Wants universal newlines self.fd = sio.TextInputFilter(self.fd) if bufsize < 0: bufsize = None if not self.writing and (bufsize is None or bufsize > 0): # Read only buffered stream. self.fd = sio.BufferingInputStream(self.fd, bufsize) if not self.reading: if bufsize is None or bufsize > 1: # Write only buffered stream. self.fd = sio.BufferingOutputStream(self.fd, bufsize) elif bufsize == 1: self.fd = sio.LineBufferingOutputStream(self.fd) if self.reading and self.writing: if bufsize > 2: # Read and write buffered stream. self.fd = sio.BufferingInputOutputStream(self.fd, bufsize) return self.fd --------- which basically exists to get self.fd set to the proper stream. So I need to _file.seek() and _file.write() and friends lead to the appropriate method on whatever we have set fd to be and I don't know how to do this without redefining __getattr__ to be getattr(self.fd, attr) So looks as if I am shot before dawn no matter what :-) Better make my last meal memorable... Laura

2 1