Hi Armin
Thanks that worked well with gcc 4.1.2. We are working to get our build system
to a newer version of oel and gcc
Thanks
Roshan
> On Apr 6, 2015, at 12:38 AM, Armin Rigo wrote:
>
> Hi Roshan,
>
>> On 6 April 2015 at 05:44, Roshan Cherian wrote:
>> Could I know the
>> recommended gc
My question stands - should we add this short explanation (maybe with
a link to the blog post) to FAQ as to why you should not use locks in
dels? Or maybe why you should not have advanced logic in dels to start
with.
On Mon, Apr 6, 2015 at 9:05 PM, Armin Rigo wrote:
> Hi Yuriy,
>
> (2) cannot be
Hi Yuriy,
(2) cannot be done in Python without major changes in semantics. User
code that makes no use of threads, for example, certainly doesn't
expect to be careful about multithreading in the __del__ methods.
(1) is hard too. What is hard is to decide when acquiring a lock in a
__del__ is sa
On Mon, Apr 6, 2015 at 4:44 PM Maciej Fijalkowski wrote:
> On Mon, Apr 6, 2015 at 3:28 PM, Yuriy Taraday wrote:
> > On Mon, Apr 6, 2015 at 3:48 PM Maciej Fijalkowski
> wrote:
> >>
> >> maybe we should add something along those lines to FAQ
> >>
> >> http://emptysqua.re/blog/pypy-garbage-collect
On Mon, Apr 6, 2015 at 3:28 PM, Yuriy Taraday wrote:
> On Mon, Apr 6, 2015 at 3:48 PM Maciej Fijalkowski wrote:
>>
>> maybe we should add something along those lines to FAQ
>>
>> http://emptysqua.re/blog/pypy-garbage-collection-and-a-deadlock/
>
>
> Can't it be fixed? I see 2 possible solutions h
On Mon, Apr 6, 2015 at 3:48 PM Maciej Fijalkowski wrote:
> maybe we should add something along those lines to FAQ
>
> http://emptysqua.re/blog/pypy-garbage-collection-and-a-deadlock/
Can't it be fixed? I see 2 possible solutions here:
1. We can detect deadlock (any lock contention during GC rou
maybe we should add something along those lines to FAQ
http://emptysqua.re/blog/pypy-garbage-collection-and-a-deadlock/
___
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
Hi Roshan,
On 6 April 2015 at 05:44, Roshan Cherian wrote:
> Could I know the
> recommended gcc version for building pypy 2.5.0.
Any version that is not seriously outdated would do. I guess 4.1 is
too old. We don't specifically try out every single old version of
gcc so I can't be more precise
