Re: [Jython-dev] *loading

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

[Samuele]
>I clarified to myself that jythonc should build the list, use the new
>order dealing with imports but it is not necessary that it find out
>that a py pkg is also a java pkg :). The modified runtime support
>can deal with this.

[Finn]
>I can make this change. Py.initProxy will then get a new "String[]
>modules" argument. I'll make it a patch,, i.e I will not commit this
>until we have settled the complete semantic change.

[Samuele]
>> During the next weekend I will somehow start experimenting with
>> merging PyJava*Packages and sys.path java load support.
>> So we will have some experience about this.
>
>Given the flat sematic for sys.path java loading (no dynamic __path__'s)
>there is nothing to experiment with, fixing things to the new semantic
>should be simple (and make code cleaner),
>up to jpythonc building the list (but I think it already gathers that 
>information) 

Correct, it does.

>and how radically can we change PackageManager, but I don't
>think its interface was intended to be public up to the sys.add_package
>door that will still be there.

I can't quite parse the paragraph above, but I think sys.add_package is
just about the only intended public interface to the PackageManager.

>It is really just Barry turn to express his opinions and concerns.

Let's not necessarily wait for that. Everybody who have spoken up agrees
that the new precedence is an improvement. With an implementation
available we can get some real world feedback from the users that are
tracking the CVS.

The precedence we are talking about can be described like this:

  Known frozen pys > sys.path (py) > java pkgs > sys.path (java) 

I'll get the necessary changes to jythonc ready by saturday.

regards,
finn