Mailman 3 February 2009 - pypy-dev

pypy translation error :\
by Jurgis Pralgauskis March 1, 2009

March 1, 2009

Hello, maybe smb could give a hint, why: http://files.akl.lt/users/jurgis/etc/pypy_translation_error.txt ps.: I acted according to instructions on http://blog.sandbox.lt/en/WSGI%20and%20PyPy%20sandbox my env: python 2.5.2, Ubuntu 8.04 Thanks in advance -- Jurgis Pralgauskis Don't worry, be happy and make things better ;) http://sagemath.visiems.lt

2 1

holydays
by Antonio Cuni Feb. 28, 2009

Feb. 28, 2009

Hi all, I'm going on holydays next week (skiing :-)), so I won't be online until the 9th. ciao, Anto

2 1

Parsing in PyPy (and runicode)
by Leonardo Santagada Feb. 27, 2009

Feb. 27, 2009

I remember some time ago people on #pypy were talking about redoing the parser for python because it was not good enough or something. Also the parser generator that cfbolz wrote doesn't support unicode and was not suited for automatic-semicolon-insertion. I think it would be good for a javascript parser that supports unicode because the specs call for it and maybe it would be good to python too (don't know about prolog/smalltalk though). What would be better, to have a parser generator that supports unicode or just everyone write their own recursive descendant parser by hand? -- Leonardo Santagada santagada at gmail.com

7 14

pypy/doc changes / py.test plugins
by holger krekel Feb. 27, 2009

Feb. 27, 2009

Hi all, i just merged the pytest plugin branch to py/trunk which is used by pypy/trunk and branches. I needed to fix pypy/trunk/doc/* to work with the new pytest_restdoc plugin, otherwise i hope that everythings just continues to work. But to avoid deprecation warnings you might want to apply revision 62212 and 62219 to the branches. If you are interested, you might read up on pytest plugins here: http://tetamap.wordpress.com/2009/02/27/new-plugin-architecture-and-plugins… cheers, holger -- Metaprogramming, Python, Testing: http://tetamap.wordpress.com Python, PyPy, pytest contracting: http://merlinux.eu

1 0

pypy sandbox
by Dalius Dobravolskas Feb. 26, 2009

Feb. 26, 2009

Hello, All, I'm trying to translate sandboxed pypy but I get following error: [sandbox:WARNING] Not Implemented: sandboxing for external function 'inet_ntop' * [rtyper] -=- specialized 3 more blocks -=- [Timer] Timings: [Timer] annotate --- 1380.9 s [Timer] rtype_lltype --- 1414.1 s [Timer] backendopt_lltype --- 647.0 s [Timer] stackcheckinsertion_lltype --- 218.3 s [Timer] database_c --- 1395.4 s [Timer] =========================================== [Timer] Total: --- 5055.7 s [translation:ERROR] Error: [translation:ERROR] Traceback (most recent call last): [translation:ERROR] File "./translate.py", line 278, in main [translation:ERROR] drv.proceed(goals) [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/translator/driver.py", line 802, in proceed [translation:ERROR] return self._execute(goals, task_skip = self._maybe_skip()) [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/translator/tool/taskengine.py", line 116, in _execute [translation:ERROR] res = self._do(goal, taskcallable, *args, **kwds) [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/translator/driver.py", line 270, in _do [translation:ERROR] res = func() [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/translator/driver.py", line 480, in task_database_c [translation:ERROR] database = cbuilder.build_database() [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/translator/c/genc.py", line 73, in build_database [translation:ERROR] db.complete() [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/translator/c/database.py", line 310, in complete [translation:ERROR] add_dependencies(node.enum_dependencies()) [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/translator/c/database.py", line 298, in add_dependencies [translation:ERROR] self.get(value) [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/translator/c/database.py", line 218, in get [translation:ERROR] node = self.getcontainernode(container) [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/translator/c/database.py", line 156, in getcontainernode [translation:ERROR] node = nodefactory(self, T, container, **buildkwds) [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/translator/c/node.py", line 699, in __init__ [translation:ERROR] self.make_funcgens() [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/translator/c/node.py", line 705, in make_funcgens [translation:ERROR] self.funcgens = select_function_code_generators(self.obj, self.db, self.name) [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/translator/c/node.py", line 825, in select_function_code_generators [translation:ERROR] return sandbox_stub(fnobj, db) [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/translator/c/node.py", line 787, in sandbox_stub [translation:ERROR] force_stub=True) [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/translator/sandbox/rsandbox.py", line 143, in get_external_function_sandbox_graph [translation:ERROR] args_s = [annmodel.lltype_to_annotation(ARG) for ARG in FUNCTYPE.ARGS] [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/annotation/model.py", line 639, in lltype_to_annotation [translation:ERROR] return SomePtr(T) [translation:ERROR] File "/home/dalius/projects/pypy-dist/pypy/annotation/model.py", line 537, in __init__ [translation:ERROR] assert isinstance(ll_ptrtype, lltype.Ptr) [translation:ERROR] AssertionError [translation] start debugger... > /home/dalius/projects/pypy-dist/pypy/annotation/model.py(537)__init__() -> assert isinstance(ll_ptrtype, lltype.Ptr) (Pdb+) q I was running command: /pypy-dist/pypy/translator/goal$ ./translate.py --sandbox --opt=1 --gc=hybrid targetpypystandalone.py I have just quited this time but it failed with same error as I run ./translate.py --sandbox targetpypystandalone.py (without options). ll_ptrtype is sock_addr if I remember correctly (when I will run it next time I will check). My system: $ uname -a Linux dalius 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux $ python -V Python 2.5.2 -- Dalius http://blog.sandbox.lt

6 16

JavaScript parser in Python
by Carl Friedrich Bolz Feb. 23, 2009

Feb. 23, 2009

Hi all, in case we ever get more serious about our JS interpreter, there seems to be a pure-Python port of the JavaScript parser of the Narcissus-project here: http://code.google.com/p/pynarcissus/ Automatic semicolon insertion included. Cheers, Carl Friedrich

2 1

new way to organise test state / new blog
by holger krekel Feb. 22, 2009

Feb. 22, 2009

Hi py-dev, testing-in-python and pypy-dev, i just created a blog where i intend to write about news regarding testing and python and metaprogramming. http://tetamap.blogspot.com/ and did a first posting about a new way of doing test state setup with py.test. Um, does anybody know how to do code coloring with blogspot? cheers, holger -- collaborative expert contracting: http://merlinux.eu PyPy Python/Compiler tool chain: http://codespeak.net/pypy pylib py.test/greenlets/svn APIs: http://pylib.org

3 3

pytest news: plugins, pycon, release-separation
by holger krekel Feb. 21, 2009

Feb. 21, 2009

Hi all, as only some of you are also following pytest developments, find below some news relevant to PyPy as well i think - i plan to merge the new pytest into py/trunk next week which is an svn-external for PyPy. If you have any feedback, i think it's ok if you send it here to pypy-dev, particularly if it is about pypy-related concerns. cheers, holger Hi folks, some good news. as those glimpsing at pytest svn-commits know i am heavily working on a new plugin architecture. I am really happy about it as those also following me on my brand-new twitter account (hpk42) might guess. Around Pycon i am giving a tutorial about advanced testing topics including cross-platform distributed testing and writing plugins and i plan to talk in detail about the new and much improved ways of doing things. Here is the status: * Terminal reporting is now a nice self-contained plugin * there is a new "xfail" plugin, inspired by SimPy to mark test functions as "expected to fail" and report specially * a "poccoo" plugin for sending test failures to http://paste.pocoo.org * new plugins for managing setup/teardown of application state, using a turns-out-to-work-great new mechanism which i guess nosetests might imitate at some point :) Regarding the next release i consider doing the following: * open two google-code projects "pytest" and "pylib" with their svn repos remaining at codespeak (where many projects share one respository - i prefer that) * move current py/test/ to its own "pytest/" root project and depend on the py lib for install. * aim to do two alpha releases, pytest-1.0 alpha and py lib 1.0 alpha (containing the rest) What do you think? I am unfamiliar with commoditized code hosting and consider using google code. I'd probably like to also have an issue tracker for pytest. Any comments/recommendations? Would someone be up for co-admining such a project? Meanwhile i am finishing up the pytestplugins branch for merge to trunk, stay tuned :) cheers & have fun, hope to meet some of you at Pycon, holger -- collaborative expert contracting: http://merlinux.eu PyPy Python/Compiler tool chain: http://codespeak.net/pypy pylib py.test/greenlets/svn APIs: http://pylib.org _______________________________________________ py-dev mailing list py-dev(a)codespeak.net http://codespeak.net/mailman/listinfo/py-dev ----- End forwarded message ----- -- collaborative expert contracting: http://merlinux.eu PyPy Python/Compiler tool chain: http://codespeak.net/pypy pylib py.test/greenlets/svn APIs: http://pylib.org

1 0

pypy and the comtypes module
by Amaury Forgeot d'Arc Feb. 19, 2009

Feb. 19, 2009

Hello Thomas, hello to all pypy-ers, I'm sure you will be interested to know that the ctypes implementation of pypy has matured enough to be able to run the comtypes module, at least some of the examples I found on the web site: http://starship.python.net/crew/theller/comtypes/ See the copy of a pypy session below. Not everything works, though. For example, the COMError exception does not give any message, some errors are caused by the alternate garbage collector of pypy (opposed to the determinism of reference counting), and I'm sure that I missed many important details... At least it is now possible to run the comtypes test suite: some tests even pass ;-) Hey, I did not know that ctypes and comtypes where so intricate: ctypes obviously has features designed for comtypes only (OUT parameters...) and ctypes/__init__.py even tries to import comtypes.server.inprocserver! But this was all fun, and I learned a lot about ffi and COM from reading the code. Thanks for these wonderful modules! Python 2.5.2 (61966, Feb 17 2009, 13:39:17) [PyPy 1.0.0] on win32 Type "help", "copyright", "credits" or "license" for more information. And now for something completely different: ``who am I and if yes, how many?'' >>>> from comtypes.client import CreateObject >>>> xl = CreateObject("Excel.Application") # Generating comtypes.gen._00020813_0000_0000_C000_000000000046_0_1_3 # Generating comtypes.gen._00020430_0000_0000_C000_000000000046_0_2_0 # Generating comtypes.gen.stdole # Generating comtypes.gen._2DF8D04C_5BFA_101B_BDE5_00AA0044DE52_0_2_1 # Generating comtypes.gen.Office # Generating comtypes.gen._0002E157_0000_0000_C000_000000000046_0_5_3 # Generating comtypes.gen.VBIDE # Generating comtypes.gen.Excel >>>> xl.Workbooks.Add() <POINTER(_Workbook) ptr=0x16af6c at 35> >>>> xl.Range("E1").Formula = "=SUM(A1:D1)" >>>> print xl.Range("E1").Value 0.0 >>>> xl.Range("A1", "D1").Value = ("Data", 10, 20, 30) >>>> print xl.Range("E1").Value 60.0 >>>> xl.Visible = True >>>> Cheers, -- Amaury Forgeot d'Arc

2 1

Re: [pypy-dev] [Stackless] Fwd: Stackless on top of greenlets
by Stephan Diehl Feb. 16, 2009

Feb. 16, 2009

Hi, it would be quite nice, if the different implementations could somehow be united (I've written the pypy one, but never used it, so there are indeed lots of errors lurking). pypy's stackless is actually implemented using pypy's coroutine implementation, which, in case CPython is used, is emulated by greenlets. pypy's stackless http://codespeak.net/svn/pypy/trunk/pypy/lib/stackless.py has a corresponding test file http://codespeak.net/svn/pypy/trunk/pypy/lib/app_test/test_stackless.py which is supposed to be compatible with regular stackless as well. Maybe we could come up with a set of tests that cover all of stackless interface and therefore can be used to test our greenlet based implementations against. Cheers, Stephan Richard Tew wrote: > ---------- Forwarded message ---------- > From: Richard Tew <richard.m.tew(a)gmail.com> > Date: Mon, Feb 16, 2009 at 11:21 AM > Subject: Re: [Stackless] Stackless on top of greenlets > To: Henk Punt <henkpunt(a)gmail.com> > > > On Mon, Feb 16, 2009 at 10:33 AM, Henk Punt <henkpunt(a)gmail.com> wrote: >> Can you give some pointers to those implementations?, >> >> The only one I could find is the one included in PyPy and that one is >> not-working, e.g. it lacks certains methods in the API and also it >> does not behave >> exactly as stackless does, especially w.r.t. the order of task-scheduling. >> Also it contains quite a lot of bugs, for instance raising an >> exception in a task that is >> blocked on a channel does not restore the correct balance and similar issues... >> > > None of the implementations I have seen have been perfect, including my own. > > http://www.stackless.com/pipermail/stackless/2005-May/002416.html > > Cheers, > Richard. > > _______________________________________________ > Stackless mailing list > Stackless(a)stackless.com > http://www.stackless.com/mailman/listinfo/stackless

1 0