On Thu, Aug 23, 2012 at 11:11 AM, Stefan Behnel stefan...@behnel.de wrote:
Maciej Fijalkowski, 05.07.2012 14:50:
On Thu, Jul 5, 2012 at 2:35 PM, Stefan Behnel wrote:
Maciej Fijalkowski, 05.07.2012 11:01:
On Thu, Jul 5, 2012 at 10:26 AM, Amaury Forgeot d'Arc wrote:
2012/7/5 Stefan Behnel
Back
Stefan Behnel, 03.07.2012 19:56:
Amaury Forgeot d'Arc, 03.07.2012 18:26:
Maybe we should use a weak dictionary to cache the PyObject structure.
This already exists for objects defined and created from C...
That would be really helpful. In particular, it would solve one of the most
annoying
Maciej Fijalkowski, 23.08.2012 11:17:
On Thu, Aug 23, 2012 at 11:11 AM, Stefan Behnel stefan...@behnel.de wrote:
Maciej Fijalkowski, 05.07.2012 14:50:
On Thu, Jul 5, 2012 at 2:35 PM, Stefan Behnel wrote:
Maciej Fijalkowski, 05.07.2012 11:01:
On Thu, Jul 5, 2012 at 10:26 AM, Amaury Forgeot
Hi,
On Fri, Aug 17, 2012 at 3:04 PM, Welch, Matt matt.we...@compuware.com wrote:
Any help would be appreciated. Do I need a different environment? Is it not
MinGW/Msys friendly?
Sorry, at least I don't know MinGW/Msys at all. The PyPy translation
toolchain is tested on Linux, OS/X, and
Armin, et al,
compile_framework_7_interior in test_zrpy_gc fails for the PPC64
backend in a strange way. Identical problems happen on the public
system and my private system, but GDB on the public system is not
permitting hardware watchpoints, so it is more difficult to catch the
cause of the
