#694: Translations scaffolding
------------------------+----------------------
Reporter: olemis | Owner: olemis
Type: task | Status: assigned
Priority: minor | Milestone:
Component: trac core | Version: 0.7.0
Resolution: | Keywords: i18n
------------------------+----------------------
Comment (by olemis):
Replying to [comment:33 olemis]:
> Replying to [comment:32 SaintGermain]:
> > Replying to [comment:31 olemis]:
> > > >
> > > > Indeed bhdashboard/util.py is importing bhdashboard/api.py, so if
you modify bhdashboard/api.py to import bhdashboard/util.py, then you got
circular import.
> > > >
> > > > Maybe you have a clever trick to force them to accept this
circular import ?
> > > > I haven't managed to do it myself.
> > >
> > > These are usually avoided by moving import statements to the end of
the .py file .
> > >
> >
> > I haven't managed to get anywhere by moving the import statements
around.
> > I can think of some dirty tricks, but I'd recommend instead to use a
clean approach: move the widget helpers in a dedicated file (see
additional patch bloodhound_i18n_circular_import.diff, they are all
cumulative).
> >
>
> I'll apply them now and run the test suite(s) to see what I get ...
I have added your changesets in my patch queue . I'd appreciate if you
could create a public fork of the [https://bitbucket.org/olemis
/bloodhound-mq patch queue repos] and upload consecutive versions in there
(which I'll merge into my own). That seems a lot easier than applying by
hand the diff of a diff, but your patch submissions are ok , at least to
me, thanks ;)
To the point ... after all this I ran the multi-product test suite . By
comparing the [http://pastebin.com/99tLkfhj i18n test report] with the
[http://pastebin.com/sswYZ4dd former test report] then total count reveals
that there's something weird happening and some test cases are not
discovered .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/694#comment:34>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
