PyCintex no longer exists in ROOT6, so there must be a mix-up of environments there. (Cintex, i.e. Reflex to CINT mapping is itself gone, as both CINT and Reflex are gone.) Since about ROOT5.34/11 there is a module ‘cppyy.py’, which also exists in compatible form in ROOT6 (same api, but of course no longer on Cintex).
@wiso: sorry, not following … the import hook is called b/c of the ‘import’ statement. Nothing to do with anything else. Beyond that:[quote=“wiso”]is line 532 correct? Or do you mean >= ?[/quote]which line exactly? My guess is that ‘352’ was meant? If that’s the case, then yes, that code is correct.
(Just to be sure, that ‘5’ in there has nothing to do with ROOT5. Is to do with the ‘5’ in python2.5.)
[quote=“wlav”]@wiso: sorry, not following … the import hook is called b/c of the ‘import’ statement. Nothing to do with anything else. Beyond that:[quote=“wiso”]is line 532 correct? Or do you mean >= ?[/quote]which line exactly? My guess is that ‘352’ was meant? If that’s the case, then yes, that code is correct.
[/quote]
Sorry, a typo.
[quote]
(Just to be sure, that ‘5’ in there has nothing to do with ROOT5. Is to do with the ‘5’ in python2.5.)
Cheers,
Wim[/quote]
ok.
The point is: why if I setup ROOT6, it tried to import PyCintex from my installation of ROOT 5?
[quote=“wiso”]The point is: why if I setup ROOT6, it tried to import PyCintex from my installation of ROOT 5?[/quote]There is no PyCintex python module in ROOT6, so python will follow the usual places beyond that to find it, and since you have one in a standard system location, that is found.
Compare this to ROOT.py, which is picked up from ROOT6, b/c there is one, and so that one masks the one in the system location, which is never seen.