On Fri, Nov 14, 2008 at 9:54 AM, Joachim König <[EMAIL PROTECTED]> wrote: > This is only required at runtime, so this is not a (circular) build or > install dependency, > but as the NetBSD-pkgsrc build infrastructure wants to generate the > .pyc/.pyo files > at installation time, I still have a problem with that.
You should not be importing any of the Python files to generate the .pyc/.pyo files at installation. You should be using compileall.py (from the Python installation) or something similar to create the .pyc/.pyo files. > So my question is: Is this circular dependency really needed or could it > be avoided > somehow? It at least looks a bit strange to me. Two components should > not depend > on each other, or am I missing something? Hopefully it can be avoided, but this isn't a problem for .pyc/.pyo generation. -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "Chaos is the score upon which reality is written." --Henry Miller _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
