[pypy-dev] Re: GC problems with PyObject

Christian Tismer [EMAIL PROTECTED] writes: Hi PyPy-dev! I spent the last two days hunting refcounting problems with pypy generated extension modules. After infinitely long staring at the final flow graphs, I found out that our transition to the gctransform is not as complete as I assumed.

Re: [pypy-dev] GC problems with PyObject

Hi Christian! Christian Tismer wrote: I spent the last two days hunting refcounting problems with pypy generated extension modules. After infinitely long staring at the final flow graphs, I found out that our transition to the gctransform is not as complete as I assumed. Impossible too find by

Re: [pypy-dev] First version of the CLI backend checked in

Hi Antonio! Antonio Cuni wrote: I've just checked in the first version of the CLI backend; for now I've checked it in a branch located at http://codespeak.net/svn/user/antocuni/pypy-antocuni/ At the moment I've tested it only with mono under linux; for running the tests you need to have

Re: [pypy-dev] First version of the CLI backend checked in

Carl Friedrich Bolz wrote: Hi Carl, I just took a cursory glance at the code, but the tests passed for me out of the box :-). Great! :-) I would say you could check it in the main repository (maybe after adding appropriate skips to the tests, if mono is not installed). The test already

Re: [pypy-dev] First version of the CLI backend checked in

Hi Antonio! Antonio Cuni wrote: Carl Friedrich Bolz wrote: I just took a cursory glance at the code, but the tests passed for me out of the box :-). Great! :-) I would say you could check it in the main repository (maybe after adding appropriate skips to the tests, if mono is not

Re: [pypy-dev] First version of the CLI backend checked in

Hi Carl Carl Friedrich Bolz wrote: I guess you have not changed anything outside of the cli directory in your branch. If this is the case it is easy: Just do an svn cp pypy-antocuni/pypy/translator/cli pypy-dist/pypy/translator/ done! Now the code should be in the main repository. Thanks

[pypy-dev] US-friendly timed pypy-sync # 2

what: weekly pypy-sync meeting where: #pypy-sync on freenode when: 2006-03-22, 5pm Central European Time for 30 minutes who: all active PyPy developers topics: - activity reports - status of tokyo sprint - goals of the 0.9 release - status and work planning for the next few weeks - targetting

[pypy-dev] Re: US-friendly timed pypy-sync # 2

Michael Hudson [EMAIL PROTECTED] writes: what: weekly pypy-sync meeting where: #pypy-sync on freenode when: 2006-03-22, 5pm Central European Time for 30 minutes Of course, I meant tomorrow, the 23rd, here. Cheers, mwh -- Need to Know is usually an interesting UK digest of things that