Re: [Jython-dev] *loading

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

[Samuele]

>Let's do that way. If you mean the gathering of frozen packages info, plus
>the initProxy,initProps,runMain stuff,

I will commit this soon. The list of modules is passed to
Py.initProperties() which right now only prints the list for debugging
purposes. The list looks like this:

   String[] modules = { "p0.__init__", "a", "p0.x" }

Is this what you need? 

>I imagine I can also fix the two last bugs: very likely the first as part of
>the findattr rewriting.

I assume bug #2 must be solved in jythonc. (Pity we can't re-use the
algorithm for searching for modules from jython itself)

>I will disable the unfinished support for poor freezing, we once reffered
>to.

Ok. I have no problem with that.

>And the loading of python modules from mixed java/python pkgs, because with
>the new precedence this is no more necessary and just confusing, there will
>be only python pkgs that eventually shadow java pkgs but leaving access to
>them, or
>not shadowed pure java pkgs.

Exactly. This is one of the reason I believe that we are onto something
good.

>[Finn]
>>>(a little note) Differently from jython, jythonc follows
>>>the proposed precedence py > java. For the rest (java loading)
>>>it uses the org.python.core runtime. Is that true?
>>
>>I don't think so. jythonc creates a list of known java packages and
>>passes this list on to sys.add_package() during initialization. This
>>creates PyJavaPackages which is currently searched before the python
>>modules. I think. But hey, you're the expert <wink>.
>
>I just hope I'm the expert ;). Sorry for the confusion. I was referring to
>the jythonc handling of import stmt
>at compilation time, not to the interaction between compiled code and jython
>runtime. 

Ohh, I see. I'm entirely sure about that either, but it does seem to be
the case. I'll look further into this and maybe fix bug #2.

regards,
finn