Mailman 3 February 2005 - pypy-dev

bug in http://codespeak.net/moin/pypy/moin.cgi/FrontPage?action=show
by Laura Creighton 10 Oct '05

10 Oct '05

If you click on the 'documentation' link you get a traceback! ooops. I will look at this later unless somebody beats me to it. Laura

5 4

Re: [pypy-svn] r9372 - pypy/dist/pypy/lib
by Sanghyeon Seo 21 Feb '05

21 Feb '05

I wrote: > Log: > _classobj's geninterplevel_name: Don't reference w_builtin > > --- pypy/dist/pypy/lib/_classobj.py (original) > +++ pypy/dist/pypy/lib/_classobj.py Mon Feb 21 01:46:37 2005 > @@ -101,7 +101,7 @@ > return > i += 1 > # let geninterplevel retrieve the PyPy builtin instead > -_seqiter.geninterplevel_name = lambda gen: "(space.getattr(space.w_builtin, %s))" % gen.nameof('_seqiter') > +_seqiter.geninterplevel_name = lambda gen: "space.builtin.get('_seqiter')" > > OLD_STYLE_CLASSES_IMPL = object() However, this doesn't work... How to get this right? Seo Sanghyeon

1 0

RE: LLVM backend
by Chris Lattner 20 Feb '05

20 Feb '05

<sorry I'm joining in late here> Carl Friedrich Bolz wrote: > I just checked my LLVM-backend in (I hope I did nothing wrong). It > resides in pypy/translator/llvm. Wow cool, I had no idea that you guys were this far along! Here are some answers to LLVM related questions: > I just removed the usage of llvmc so if that was really the problem > it could work now. The only llvm tools that genllvm now uses are > llvm-as (which works in your case) and llc (produces native code). Yup, unfortunately, 'llvmc' was not quite stable when the 1.4 release was put out. It's a bit better in LLVM CVS now, but is still a work in progress. Just not using it is a good way to go for now. > - I think there should be some more intelligent way to produce the > necessary LLLVM-implementations for the space operations of more > complex types than just writing them in LLVM-assembler, which can be > quite tedious (it's no fun writing programs in SSA form). Oh yeah, generating SSA is quite a pain. The traditional way that LLVM front-ends deal with this is to use 'alloca's for local variables and use explicit loads/stores to them. This generates really gross looking code, but the LLVM optimizers (specifically mem2reg) rip them up. For example, for something simple like: X = 1; ... = X; ... X = 2; You can generate code that looks like this: %X = alloca int ;; in the entry block for the fn ... store int 1, int* %X ... = load int* %X ... store int 2, int* %X ... If you run this sort of code through the LLVM "-mem2reg" optimization, it will promote all of these to SSA values, so you don't have to do it yourself. If the "..."'s contain control flow, this is a non-trivial task. :) > - List and Strings should be relatively easy to implement with arrays. > I'm not quite shure wether I manage to do it, I'll just ask questions > if I run into problems. If you have any LLVM specific question, please feel free to contact the llvmdev list (http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev), the people on the list are quite helpful and would love to help you in any way they can. > - Are tuples really only used for returning multiple values from a > function? If yes they could be avoided altogether using additional > pointer arguments that point to where the return value should be > stored. On the LLVM side of things, the only way for a function to return multiple values is (as you mention) to pass a pointer that indicates where to store the result. In the future (say 3-4 months out), LLVM will be extended to allow functions to return multiple values in registers. Another thought: I see that you're currently using llc to build your programs, have you considered using the LLVM JIT? Anyway, if you have any questions or run into problems, again, we'd love to help, just let us know. :) -Chris -- http://nondot.org/sabre/ http://llvm.cs.uiuc.edu/

6 10

Type inference documentation
by Valentino Volonghi aka Dialtone 19 Feb '05

19 Feb '05

For poor people like me, pypy wannabe contributor, I think it would be good to have some updated documentation about type-inference/annotation as done in pypy. The only doc I can find is heavily outdated, as stated in the first lines of the file. Is this documentation planned? Sorry for the wrong post in py-dev ML :( cheers -- Valentino Volonghi aka Dialtone Now Running MacOSX 10.3.8 Blog: http://vvolonghi.blogspot.com http://weever.berlios.de

3 4

Ann: PyPy Sprint before PYCON 2005 in Washington
by Christian Tismer 15 Feb '05

15 Feb '05

PyPy Sprint before PYCON 2005 in Washington ------------------------------------------- In the four days from 19th March till 22th March (inclusive) the PyPy team will host a sprint on their new Python-in-Python implementation. The PyPy project was granted funding by the European Union as part of its Sixth Framework Program, and is now on track to produce a stackless Python-in-Python Just-in-Time Compiler by December 2006. Our Python implementation, released under the MIT/BSD license, already provides new levels of flexibility and extensibility at the core interpreter and object implementation level. Armin Rigo and Holger Krekel will also give talks about PyPy and the separate py.test tool (used to perform various kinds of testing in PyPy) during the conference. Naturally, we are eager to see how the other re-implementation of Python, namely IronPython, is doing and to explore collaboration possibilities. Of course, that will depend on the degree of openness that Microsoft wants to employ. The Pycon2005 sprint is going to focus on reaching compatibility with CPython (currently we target version 2.3.4) for our PyPy version running on top of CPython. One goal of the sprint is to pass 60% or more of the unmodified regression tests of mainline CPython. It will thus be a great way to get to know CPython and PyPy better at the same time! Other possible work areas include: - translation to C to get a first working lower-level representation of the interpreter "specified in Python" - integrating and implementing a full parser/compiler chain written in Python maybe already targetting the new AST-branch of mainline CPython - fixing various remaining issues that will come up while trying to reach the compatibility goal - integrate or code pure python implementations of some Python modules currently written in C. - whatever issues you come up with! (please tell us before hand so we can better plan introductions etc.pp.) Besides core developers, Bea Düring will be present to help improving and document our sprint and agile development process. We are going to give tutorials about PyPy's basic concepts and provide help to newcomers usually by pairing them with experienced pypythonistas. However, we kindly ask newcomers to be present on the first day's morning (19th of March) of the sprint to be able to get everyone a smooth start into the sprint. So far most newcomers had few problems in getting a good start into our codebase. However, it is good to have the following preparational points in mind: - some experience with programming in the Python language and interest to dive deeper - subscription to pypy-dev and pypy-sprint at http://codespeak.net/pypy/index.cgi?lists - have a subversion-client, Pygame and graphviz installed on the machine you bring to the sprint. - have a look at our current documentation, especially the architecture and getting-started documents under http://codespeak.net/pypy/index.cgi?doc The pypy-dev and pypy-sprint lists are also the contact points for raising questions and suggesting and discussing sprint topics beforehand. We are on #pypy on irc.freenode.net most of the time. Please don't hesitate to contact us or introduce yourself and your interests! Logistics --------- Organizational details will be posted to pypy-sprint and are or will be available in the Pycon2005-Sprint wiki here: http://www.python.org/moin/PyConDC2005/Sprints Registration ------------ send mail to pypy-sprint(a)codespeak.net, stating the days you can be present and any specific interests if applicable. Registered Participants ----------------------- all days: Jacob Hallén Armin Rigo Holger Krekel Samuele Pedroni Anders Chrigström Bea Düring Christian Tismer Richard Emslie -- Christian Tismer :^) <mailto:tismer@stackless.com> tismerysoft GmbH : 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 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/

1 0

Re: [pypy-svn] r9196 - pypy/dist/lib-python-2.3.4/test
by hpk＠trillke.net 14 Feb '05

14 Feb '05

Hi Anders, On Mon, Feb 14, 2005 at 10:21 +0100, ac(a)codespeak.net wrote: > Author: ac > Date: Mon Feb 14 10:21:01 2005 > New Revision: 9196 > > Modified: > pypy/dist/lib-python-2.3.4/test/pypy_unittest.py > Log: > Work around problem with py.test's raises(). What would that problem be? I tried some cases (wrong or missing exception) which all seemed to work ... cheers, holger

1 0

Re: [pypy-svn] r9152 - pypy/dist/pypy/lib
by hpk＠trillke.net 12 Feb '05

12 Feb '05

Hi Seo, On Sat, Feb 12, 2005 at 09:27 +0100, sanxiyn(a)codespeak.net wrote: > Author: sanxiyn > Date: Sat Feb 12 09:27:20 2005 > New Revision: 9152 > > Added: > pypy/dist/pypy/lib/decimal.py > Log: > decimal module from 2.4. All doctests pass. we wanted to put only modified modules relating to cpython 2.3.4 in our "lib-python-2.3.4" overriding "pypy/lib" directory. Maybe it makes sense to rename pypy/lib to pypy/lib-override-2.3.4 to make this more obvious :-) cheers, holger

1 0

Re: [pypy-svn] r9112 - pypy/dist/pypy/tool
by Laura Creighton 11 Feb '05

11 Feb '05

That was me, mindlessly following a ruleset in my head to convert UnitTestLanguage into code. Some days I am a stupid as a machine. laura In a message of Fri, 11 Feb 2005 14:57:14 +0100, arigo(a)codespeak.net writes: >Author: arigo >Date: Fri Feb 11 14:57:14 2005 >New Revision: 9112 > >Modified: > pypy/dist/pypy/tool/utestconvert.py >Log: >Not sure why failUnlessEqual(x,y) is converted into assert not x!=y. > > >Modified: pypy/dist/pypy/tool/utestconvert.py >========================================================================= >===== >--- pypy/dist/pypy/tool/utestconvert.py (original) >+++ pypy/dist/pypy/tool/utestconvert.py Fri Feb 11 14:57:14 2005 >@@ -18,11 +18,11 @@ > d['assertEqual'] = ('assert', ' ==', [2,3]) > d['failIfEqual'] = ('assert not', ' ==', [2,3]) > d['assertNotEqual'] = ('assert', ' !=', [2,3]) >-d['failUnlessEqual'] = ('assert not', ' !=', [2,3]) >+d['failUnlessEqual'] = ('assert', ' ==', [2,3]) > d['assertAlmostEqual'] = ('assert round', ' ==', [2,3,4]) > d['failIfAlmostEqual'] = ('assert not round', ' ==', [2,3,4]) > d['assertNotAlmostEqual'] = ('assert round', ' !=', [2,3,4]) >-d['failUnlessAlmostEquals'] = ('assert not round', ' !=', [2,3,4]) >+d['failUnlessAlmostEquals'] = ('assert round', ' ==', [2,3,4]) > # PyPy specific > d['assertRaises_w'] = ('self.space.raises_w', '', ['Any'] >) > d['assertEqual_w'] = ('assert self.space.eq_w','',['Any']) >_______________________________________________ >pypy-svn mailing list >pypy-svn(a)codespeak.net >http://codespeak.net/mailman/listinfo/pypy-svn

1 0

Re: [pypy-svn] r9100 - in pypy/dist/pypy/objspace/std: . test
by Michael Hudson 11 Feb '05

11 Feb '05

ac(a)codespeak.net writes: > Author: ac > Date: Fri Feb 11 10:40:47 2005 > New Revision: 9100 > > Added: > pypy/dist/pypy/objspace/std/test/test_fake.py (contents, props changed) > Modified: > pypy/dist/pypy/objspace/std/fake.py > Log: > Make faked types a little more inheritable. Nice one. It might be worth checking if this lets Python 2.3's random module work now. Cheers, mwh -- 34. The string is a stark data structure and everywhere it is passed there is much duplication of process. It is a perfect vehicle for hiding information. -- Alan Perlis, http://www.cs.yale.edu/homes/perlis-alan/quotes.html

2 3

Re: [pypy-svn] r8960 - pypy/dist/pypy/objspace/std
by Armin Rigo 10 Feb '05

10 Feb '05

Hi Anders, On Mon, Feb 07, 2005 at 06:07:19PM +0100, ac(a)codespeak.net wrote: > Log: > Make it possible to run (but with failing tests) cpythons test_builtins Hum, I still cannot run the test in my own machine, but I can run it on codespeak. Moreover I can still run it on codespeak without your patch... So my guess is that something unrelated is going on here. (Your patch itself is fine, though, as a good performance improvement.) Armin

2 2