2011/5/19 Gabriel Jacobo :
> Hi All! I have a quick question for the RPython gurus, are properties
> supported?
No.
> I thought from reading pypy tests and some mentions in IRC logs that they
Tests are not RPython.
--
Regards,
Benjamin
___
pypy-dev
Hi All! I have a quick question for the RPython gurus, are properties
supported?
I thought from reading pypy tests and some mentions in IRC logs that they
should work (plus I haven't found any of the RPython rules explicitly
forbidding them), but I'm hitting a dead end trying to use them.
If someon
On Thu, 2011-05-19 at 18:34 +0200, Armin Rigo wrote:
> Hi,
>
> On Thu, May 19, 2011 at 6:00 PM, Maciej Fijalkowski wrote:
> > If the only goal is to avoid doing those 2 at the same time, do
> > translate.py --source and then go to the /tmp/usession-*/testing_1
> > directory and type make
>
> We
Hi,
On Thu, May 19, 2011 at 6:00 PM, Maciej Fijalkowski wrote:
> If the only goal is to avoid doing those 2 at the same time, do
> translate.py --source and then go to the /tmp/usession-*/testing_1
> directory and type make
We should decide if it would make sense or not to just do
os.execv("make
On Thu, May 19, 2011 at 5:55 PM, David Naylor wrote:
> Hi,
>
> I'm sure you all know that translating pypy requires a large amount of RAM.
>
> It has been my experience that GCC also uses a large amount of RAM when
> compiling, about 4G. Is it possible to get python/pypy to stop once
> it has wri
Hi,
I'm sure you all know that translating pypy requires a large amount of RAM.
It has been my experience that GCC also uses a large amount of RAM when
compiling, about 4G. Is it possible to get python/pypy to stop once
it has written
the source files and then to run that build process separatel
