On Mar 20, 2008, at 13:31, Bill Janssen <[EMAIL PROTECTED]> wrote:
The downside is that you have to add this kind of little startup blit
to each JCC-wrapped module. So, this either needs to be turned into
a JCC utility function which gets called once per Python
instantiation,
or generated by the wrapper generation process for each module.
Actually, if you were to enable the "shared" version of JCC on
Windows, I think the single instance of the blit in jcc/__init__.py
would do the trick. Let me work on that.
When using --shared, the jcc extension is not used (at runtime) only
libjcc.dylib is.
Even if you're not shipping python with your product, you can add that
code to it to run before importing the module(s) that require the new
Path.
Andi..
Bill
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
