Re: [Jython-dev] dependency problem with jythonc

[<bc...@wo...>]

[Juris]

>Hello,
>
>
>I was trying to freeze (actually web/servlet-ize, but that's besides the =
>point) my Jython application, and failed - I must be doing something =
>totally wrong. :-(.
>
>Here's a short failure scenario:

[fine example snipped]

>Now, "jython Main.py" works just fine ("kermits" is printed).
>Here's the output from "jythonc --deep" at compile time:
>
>Next, we go to "./jpywork" and do a "java Main" and get:
>-- start --
>Java Traceback:
>...
>Traceback (innermost last):
>  File "E:\projects\jytest\2\Main.py", line 0, in main
>  File "E:\projects\jytest\2\bpkg\B.py", line 0, in main
>ImportError: no module named apkg
>-- end --
>
>Taking a look at the ./jpywork directory shows that __init__-s (.java, =
>.class and $_PyInner.class) have only been compiled for bpkg, but not =
>for apkg.
>I tried passing it multiple arguments to compile, but it then compiled =
>it to a different "package level".
>=20
>Now, if we uncomment the first line in Main.py to also "from apkg.A =
>import A" it works just fine (but importing all modules from the main =
>application seems an ugly hack).
>
>
>Any comments will be very appreciated.

It's a bug. I have added a bug report so that it wont get lost.

>P.S. I hope this is on-topic for this list, since it _might_ be a =
>jythonc bug. If not - let me know and forgive me this time :-).

Its fine. There is no need to worry to much about the different lists.

regards,
finn