Mailman 3 January 2009 - pypy-dev

official announcement of snakebite
by Maciej Fijalkowski 28 Jan '09

28 Jan '09

Some very good news for us: http://groups.google.com/group/snakebite-list/browse_thread/thread/6402c238… seems like going towards end of windows problems :) Cheers and thanks to Trent, fijal

1 0

Europython sprint
by Jacob Hallén 28 Jan '09

28 Jan '09

Hi everyone, the Europython organisers would like us to settle on dates for a sprint around Europython as soon as possible. They are very eager to do well in the sprinting department, as sprints are something that hasn't taken off in the UK so far. It is something they very much want to change. PyPy is naturally considered to be the leader in the field of sprints and the organisers would like to accomdate our needs as best they can. This means that they have to book rooms in the next week or so. The outine of the programme is as follows: * Sunday 28th June and Monday 29th June : Tutorial Days * Tuesday 30th June to Thursday 2nd July : Conference * Friday 3rd July, as long as needed : Sprints We could have a sprint(an internal one?) in parallel with the tutorials if we want. How long would we like to sprint after the conference? Friday-Sunday? Birmingham is quite a nice environment and the rate of the British pound is not so outrageous, that we probably can afford a decent length of stay. Jacob

2 1

parser compiler and _ast
by Maciej Fijalkowski 26 Jan '09

26 Jan '09

I did a bit of research on a matter of different python interfaces to parsing. This is a bit of a mess, but it is as follows: a) there is a parser module which gives you very low-level interface (so-called concrete syntax tree), which is essentially a list of tuples with numbers inside. you can compile those tuples to bytecode afterwards. It's slowly being deprecated. b) there is a compiler module, which is a wrapper around parser. it does not let you compile ast, but it gives you ast. It's deprecated since 2.6. c) there is an ast module which lets you have ast *and* compile it. very neat. Now the state of the art is that we have parser, compiler is pure app-level and we don't provide ast. We already discussed a bit whether to have ast module for 1.1 and the answer is "very likely no", raise hands if you want to have it. Now I want to know how much do we care about all of this and how much do we care about any of those? My suggestions are as follows: 1. We keep parser as it is and don't try to fix bugs. Bugs (as reported by CPython's test failures) are that we don't do extra walk around the tree to detect syntax errors. those errors are only detected when we generated the code - or - 1a. We just always generate the code and throw it away. We loose performance, but we don't care (and we pass tests) 2. We slowly deprecate parser & compiler, with some removal in future 3. If we develop a new parser, we drop compatibility with exact concrete syntax trees and we only keep ast around (as ast module) if people want to interact with it (this is one less worry for writing parser). What do you think? Cheers, fijal

2 1

resource module for pypy
by Maciej Fijalkowski 26 Jan '09

26 Jan '09

Hi Victor, hi pypy-dev I think you're the one who implemented the resource module using ctypes. Right now it timouts/fails when running cpython's test suite (1.) - last run. Our policy is to either fix it, or remove it for 1.1 release. Do you eventually would like to take a look? Cheers, fijal 1. http://codespeak.net:8099/summary/longrepr?testname=unmodified&builder=pypy…

1 0

Re: [pypy-dev] [pypy-svn] r61220 - pypy/trunk/lib-python
by Antonio Cuni 22 Jan '09

22 Jan '09

fijal(a)codespeak.net wrote: > we need to have RegrTest for each file starting with test_ anyway... > > > Modified: pypy/trunk/lib-python/conftest.py > ============================================================================== > --- pypy/trunk/lib-python/conftest.py (original) > +++ pypy/trunk/lib-python/conftest.py Thu Jan 22 10:34:15 2009 > @@ -294,6 +294,7 @@ > RegrTest('test_mmap.py'), > RegrTest('test_module.py', core=True), > RegrTest('test_multibytecodec.py', skip="unsupported codecs"), > + RegrTest('test_multibytecodec.py_support', skip="not a test"), uhm... did you want to write test_multibytecodec_support.py, maybe?

2 1

Non-circular path through pypy module imports
by VanL 21 Jan '09

21 Jan '09

Hello, I have been going through the pypy sources recently and I wanted to start from the leaf modules first (in terms of import dependencies)... but there don't appear to be any leaves. For example, starting with baseobjspace in the interpreter, it has 30 or so non-stdlib imports, many of them delayed by placing them in functions. Even something like rarithmetic eventually pulls in most of the lltype hierarchy. The closest I found to a leaf module was extregistry.py. Is there a reason for the circularities that I just don't get? If not, why are there so many? Thanks, Van

2 1

Re: [pypy-dev] Translate failes =(
by Vetoshkin Nikita 21 Jan '09

21 Jan '09

Could you please point me source files where to look/digg: "configure" phase building and pypy-c executable building. As I see now, /MT flag I used applies to all compiled binaries and you suggest using it only during first building process? Any ideas about building manifest file to proper msvcrt.dll linking? >The /MT flag is a nice trick. >But the ctypes module of the generated pypy-c will not work correctly: >get_libc() is supposed to return the MSVCRT.dll linked with the >executable, this function won't work if the c runtime is linked >statically. >The best would be to use /MT (=static C runtime) to build extension >modules (during the "configure" phase) and /MD (=shared C runtime) >when building the pypy-c executable. > >-- Amaury Forgeot d'Arc

2 6

windows buildbot
by Maciej Fijalkowski 20 Jan '09

20 Jan '09

I just triggered translation here: http://codespeak.net:8099/builders/pypy-c-lib-python-win-32/builds/23/steps… and I noticed that there are 48 implement files. Is it because files are split to smaller chunks for some reason, or something went wrong along the lines? Cheers, fijal

3 2

Translate failes =(
by Ветошкин Никита 20 Jan '09

20 Jan '09

Hi, all! I'm trying to translate PyPy on Windows Vista x64 with Python2.4 32 bit and Visual Studio 2008 Express Edition. 32 bit - cause Express Edition isn't shipped with x64 compiler. Translation failes: http://pastebin.com/m70de1376. Fixing Visual Studio version recognition ( warning about KeyError VS71COMNTOOLS) doesn't help, translation failes with the same error. Any suggestions? P.S. In answers, please, put my mail in copy, cause I'm subscribed to digest =)

4 6

forcing builds Re: another issue with buildbot
by Samuele Pedroni 18 Jan '09

18 Jan '09

Maciej Fijalkowski wrote: > I found out that I'm unable to force run by hand. It checks out the > revision from last build. Do you know how to bump it? > you need to use the rebuild from the builder page, the rebuild from the build page will reuse the got_revision

2 2