Tim,
> I was wondering if it is possible that I screwed something up with
> 32/64bit compilation. I built root and python myself. I think both are
> correctly built as 64bit executables, at least if I do file `which
> python` I get told it is a "Mach-O universal binary with 3
> architectures", one of which is x86_64. I need to read up on universal
> executables a bit to understand more though.
also, I'd figure earlier problems would show up if the problem was at the level of a mismatched build.
> tree in python: <ROOT.TTree object at 0x104c42ef0>
> pytree: <ROOT.TTree object at 0x104c42ef0>
> ttree again: 0
Since ObjectProxy_Check failed, and since TPython::ObjectProxy_AsVoidPtr uses that internally as well, and since the part of ObjectProxy_Check that does the actual work is in python, I can't think of any detail that has this go wrong ... Especially since I'm unable to reproduce. :/
Best regards,
Wim
-- WLavrijsen_at_lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.netReceived on Fri Aug 13 2010 - 20:31:16 CEST
This archive was generated by hypermail 2.2.0 : Wed Aug 25 2010 - 23:50:01 CEST