March 7, 2006
10 p.m.
At 04:37 PM 3/7/2006 -0500, Kevin Dangoor wrote:
On 3/7/06, Ben Bangert <ben@groovie.org> wrote:
Indeed, I just noticed that setup.py was importing version from the package, and the location it was importing, then imported other stuff that had the dependencies. Thanks for the pointer on what was going wrong.
This appears to be the general solution to that particular problem. In setup.py:
execfile(os.path.join("turbogears", "release.py"))
or something along those lines.
That only works if 'release.py' doesn't import any dependencies. :) That is, the issue doesn't have anything to do with imports per se, only imports that cause dependencies to come into play.