Mailman 3 January 2012 - pypy-dev

What Causes An Ambiguous low-level helper specialization Error?
by Andrew Francis Jan. 25, 2012

Jan. 25, 2012

Hi Folks: I am trying to write a simple RPython programme that uses the STM module. I am modelling my example after targetdemo.py. this is a code fragment def T1(): global fromAccount, toAccount, counter transactionA(fromAccount, toAccount, counter) def T2(): global fromAccount, toAccount, counter transactionB(fromAccount, toAccount, counter) # __________ Entry point __________ def entry_point(argv): &… [View More]

4 9

why PyPy build takes so much resources?
by Dmitrey Jan. 24, 2012

Jan. 24, 2012

Required 4 GB for 64bit machine and lots of time for build to be elapsed each day is very inconvenient. Well, I can download and install compiled version, but then I have to set all paths to the files I'm working with. Maybe somewhere there are lots of C files with -O3 or like that? Can you provide a build option e.g. --without-optimization to remove those -O3, -O2 or somehow else reduce build time and memory consumption (well I see the opts PYPY_GC_MAX_DELTA=200MB pypy --jit … [View More]

2 1

bitbucket slowness
by Maciej Fijalkowski Jan. 23, 2012

Jan. 23, 2012

Hi >From things I just learned: if you use ssh instead of https it's much faster, like: ssh://hg@bitbucket.org/pypy/pypy in .hg/hgrc in your pypy checkout cheers, fijal

1 0

Re: [pypy-dev] [pypy-commit] pypy merge-2.7.2: Implement CPython issue5057: do not const-fold a unicode.__getitem__
by Maciej Fijalkowski Jan. 23, 2012

Jan. 23, 2012

Why not? We have only wide build, don't we? On Sun, Jan 22, 2012 at 9:57 PM, amauryfa <noreply(a)buildbot.pypy.org> wrote: > Author: Amaury Forgeot d'Arc <amauryfa(a)gmail.com> > Branch: merge-2.7.2 > Changeset: r51662:693b08144e00 > Date: 2012-01-22 20:24 +0100 > http://bitbucket.org/pypy/pypy/changeset/693b08144e00/ > > Log: Implement CPython issue5057: do not const-fold a unicode.__getitem__ > operation which … [View More]returns a non-BMP character, this produces .pyc > files which depends on the unicode width > > diff --git a/pypy/interpreter/astcompiler/optimize.py b/pypy/interpreter/astcompiler/optimize.py > --- a/pypy/interpreter/astcompiler/optimize.py > +++ b/pypy/interpreter/astcompiler/optimize.py > @@ -5,6 +5,7 @@ > from pypy.tool import stdlib_opcode as ops > from pypy.interpreter.error import OperationError > from pypy.rlib.unroll import unrolling_iterable > +from pypy.rlib.runicode import MAXUNICODE > > > def optimize_ast(space, tree, compile_info): > @@ -289,8 +290,30 @@ > w_idx = subs.slice.as_constant() > if w_idx is not None: > try: > - return ast.Const(self.space.getitem(w_obj, w_idx), subs.lineno, subs.col_offset) > + w_const = self.space.getitem(w_obj, w_idx) > except OperationError: > - # Let exceptions propgate at runtime. > - pass > + # Let exceptions propagate at runtime. > + return subs > + > + # CPython issue5057: if v is unicode, there might > + # be differences between wide and narrow builds in > + # cases like u'\U00012345'[0]. > + # Wide builds will return a non-BMP char, whereas > + # narrow builds will return a surrogate. In both > + # the cases skip the optimization in order to > + # produce compatible pycs. > + if (self.space.isinstance_w(w_obj, self.space.w_unicode) > + and > + self.space.isinstance_w(w_const, self.space.w_unicode)): > + unistr = self.space.unicode_w(w_const) > + if len(unistr) == 1: > + ch = ord(unistr[0]) > + else: > + ch = 0 > + if (ch > 0xFFFF or > + (MAXUNICODE == 0xFFFF and 0xD800 <= ch <= OxDFFFF)): > + return subs > + > + return ast.Const(w_const, subs.lineno, subs.col_offset) > + > return subs > diff --git a/pypy/interpreter/astcompiler/test/test_compiler.py b/pypy/interpreter/astcompiler/test/test_compiler.py > --- a/pypy/interpreter/astcompiler/test/test_compiler.py > +++ b/pypy/interpreter/astcompiler/test/test_compiler.py > @@ -838,6 +838,30 @@ > # Just checking this doesn't crash out > self.count_instructions(source) > > + def test_const_fold_unicode_subscr(self): > + source = """def f(): > + return u"abc"[0] > + """ > + counts = self.count_instructions(source) > + assert counts == {ops.LOAD_CONST: 1, ops.RETURN_VALUE: 1} > + > + # getitem outside of the BMP should not be optimized > + source = """def f(): > + return u"\U00012345"[0] > + """ > + counts = self.count_instructions(source) > + assert counts == {ops.LOAD_CONST: 2, ops.BINARY_SUBSCR: 1, > + ops.RETURN_VALUE: 1} > + > + # getslice is not yet optimized. > + # Still, check a case which yields the empty string. > + source = """def f(): > + return u"abc"[:0] > + """ > + counts = self.count_instructions(source) > + assert counts == {ops.LOAD_CONST: 2, ops.SLICE+2: 1, > + ops.RETURN_VALUE: 1} > + > def test_remove_dead_code(self): > source = """def f(x): > return 5 > _______________________________________________ > pypy-commit mailing list > pypy-commit(a)python.org > http://mail.python.org/mailman/listinfo/pypy-commit [View Less]

2 1

Re: [pypy-dev] [pypy-commit] pypy py3k: The exception handler target "except ValueError as exc" was always compiled as a global variable. Test and fix.
by Maciej Fijalkowski Jan. 23, 2012

Jan. 23, 2012

Shouldn't that go to trunk as well? On Sun, Jan 22, 2012 at 1:10 PM, amauryfa <noreply(a)buildbot.pypy.org> wrote: > Author: Amaury Forgeot d'Arc <amauryfa(a)gmail.com> > Branch: py3k > Changeset: r51639:e325e4d3227a > Date: 2012-01-22 12:02 +0100 > http://bitbucket.org/pypy/pypy/changeset/e325e4d3227a/ > > Log: The exception handler target "except ValueError as exc" was always > compiled as a global variable. Test and … [View More]

2 1

GC error
by Rich Drewes Jan. 21, 2012

Jan. 21, 2012

Hello all, Great work on pypy! I've had good luck with pypy generally but on a program that loads a very large data set I am getting a GC related exception: ---- loading reads, on record 25000000 RPython traceback: File "translator_goal_targetpypystandalone.c", line 888, in entry_point File "interpreter_function.c", line 876, in funccall__star_1 File "interpreter_function.c", line 905, in funccall__star_1 File "rpython_memory_gc_minimark.c", line 2490, in … [View More]

6 9

numpypy: could NaN be added?
by Dmitrey Jan. 21, 2012

Jan. 21, 2012

hi all, absence of numpypy.nan prevents creating lots of highly important funcs like isnan, nanmin, nanmax, nanargmin, nanargmax, nansum etc. I cannot guarantee I would immediately provide them, especially for multidimensional arrays, but, at least, I (or other programmers) could create temporary replacements for the absent yet funcs in their own code (for example, only for 1-dimensional or at most 2-dimensional arrays), making their code working in PyPy right now. So could you put the … [View More]

2 2

numpypy / scipypy additions
by Joseph Perla Jan. 21, 2012

Jan. 21, 2012

Hello everyone, I want to add functions to numpypy and also start making scipypy useful to scientists. How do I commit my code? First, a little bit about myself: I have been following PyPy's development for 5 years. I met Armin Rigo and other PyPy devs at EuroPython 2011 in Florence this past year. I gave a talk about minimalist Python web templates: weby templates. PyPy always seemed like a hugely complicated project far above my talents. I look forward to finally contributing code … [View More]

3 4

segmentation fault
by Joseph Javier Perla Jan. 20, 2012

Jan. 20, 2012

I wrote several other missing methods (np.log, np.diag, np.concatenate) and now I have the full program working. I would like to add these other features as well. (Also, np.sum() should be able to do element-wise sum of a generator of n-dimensional arrays.) But, now I get a segfault. I was wondering how I could investigate the segfault issue. There is no error message or traceback, and I cannot catch the error with pdb. Thank you. j

2 1

certificate for accepting numpypy new funcs?
by Dmitrey Jan. 20, 2012

Jan. 20, 2012

Hi all, could you provide clarification to numpypy new funcs accepting (not only for me, but for any other possible volunteers)? The doc I've been directed says only "You have to test exhaustively your module", while I would like to know more explicit rules. For example, "at least 3 tests per func" (however, I guess for funcs of different complexity and variability number of tests also should expected to be different). Also, are there any strict rules for the testcases to be submitted, or … [View More]

5 9