[Jython-dev] work in progress

[Samuele P. <pe...@in...>]

Hi.

I'm working on the precedence issue.
I hope to have finished for ~monday.

Everything we have discussed for it should be implemented, plus some
other bug fixes.

I also have implemented PackageManager through a hier. of abstract classes,
this is an hook for future support for load sets.

The patch/rewriting will be something finished but not definitive,
something we can try and discuss on.

We will have a symm. behaviour for dir/jar pkgs, I have merged
PyJavaDir- and PyJavaPackage.

Some questions:

I would like to distinguish the support for dir() for java packages from
the support for from <pkg> import *. I dislike the fact that dir
force lazy loading, because __dir__ is used by from import * code.
Lazy loading should be limited to the from import * case.
The fact is that I want to minimize the "potential" robustness issues
of the - in any case - necessary cache patch.
Any remark or hint on this is welcome?

I have read the archive of import-sig and looked at the version of imputil
distributed with Python 2.0.

Finn or somebody else knows what is the actual state of the issue?

will imputil substitute ihooks, the distributed version seems not finished
and contains todos and referees and (Finn's) notes about what should be done
to make it possibly work under J(P)ython.

If it will be the future imp hooks framework, not ignoring it for the design
of load sets is maybe a not bad design idea, but clearly imp hooks
and load sets are in some sense orthogonal and the latter very java specific.


[into the future]
My first look impression, is that imputil design and import-sig discussion
have ignored the jython side of the problem.

imputil should support RExec and the import practice of major py pkgs
and extensions plus freeze and try to offer the primitives for mimicking
the java load behaviours (url loading)....

jython imp should support jpythonc, maybe somekind of poor freeze, java 
reloading, mixing of classpath and sys.path ...

My impression is that both world have something to learn from each other,

for example jython is maybe the right ground to decide what could make sense
on sys.path (urls vs. 'importers' ...) and given the constraints for load sets
design, that the concept of virtual pkg can sometimes be useful.

On the other side jython lacks something like RExec, ok we have
java security but it is (very) difficult to use it for python code directly,
maybe we need an extension of RExec concepts that fits with java model:
but that's a real challenge (completely aware of that!) and maybe not that
much useful (very low prio ;)).

regards, Samuele