Re: [Modeling-users] Models and import order

[Sebastien B. <sbi...@us...>]

Mario Ruggier <ma...@ru...> wrote:
> Hello Seb,
> > Can you confirm that you used the '-B'/--base generation scheme? The
> > -C/compact scheme does not suffer from this as far as I can see.
>=20
> Yes, i use the --base scheme. Sorry I forgot to mention it before, as for
> me this is hidden inside a little custom script that i use to generate
> the package.

Ok.

> OK. I have filed this as bug 839231.

  Thanks. I've just attached a patch to this bug report; you'll need to
patch your local copy and reinstall the framework (templates need to be
recompiled w/ cheetah-compile). Hopefully this solves the problem --at
least that's what I see. I still need to redesign some tests so that
this can be detected in the future, then I'll probably add it to the cvs
trunk if you confirm that this solves the problem on your side as well,
whatever order you use in the import-sequence.

  Thanks for reporting. FYI this was due to circular imports induced by
  useless imports in generated MDL/__init__.py. These imports are now
  done, when necessary, in the dedicated .py modules.

-- S=E9bastien.