On Sun, 7 Dec 2008 11:34:01 +0100 (CET) Antoine Jacoutot <[EMAIL PROTECTED]> wrote:
> On Sun, 7 Dec 2008, Eric Faurot wrote: > > > For python modules not using MODPY_SETUPTOOLS, the installed .pyc > > files refer to their source .py files in the fake directory instead of > > LOCALBASE. I am not sure how bad it is in general, but this is at > > least a problem for some py-twisted regress tests which fails because > > of this. > > > > I see no reason why it should not be handled correctly as in the > > "MODPY_SETUPTOOLS=Yes" case. > > > > Comments? > > I completely trust you on this, but I think it would worth a comment in > the python.port.mk file, so that noone wonders why prefix isn't PREFIX. > > On a more important note, does it mean all ports using the python MODULE > without MODPY_SETUPTOOLS need a bump? It looks like so... :-( That is what I thought too at first, but this is very annoying and I don't think it is really worth the hassle: This change would have the same impact on the resulting packages as changing WRKOBJDIR when building them, which is not supposed to matter wrt to packages and updates anyway. So I think we could let the packages get "fixed naturally" as part of the regular updates, and perhaps bump python itself. Eric.