On Sun, 27 Apr 2008 18:07:07 +0200, Bill Janssen <[EMAIL PROTECTED]> wrote:
It appends the value found in the registry (if any) to the end of the
PATH, so any value previously put on the PATH by sitecustomize.py (or
by Andi's hypothetical __init__.py code that runs before the "lucene"
module is
> We are distributing Java as a subcomponent (a subfolder next to the
> embedded Python) under Windows, and we modify the PATH variable with
> sitecustomize.py to point to this jvm.dll. So this would collide with our
> setup.
I believe that it would actually not collide with your solution, D
On Sat, 26 Apr 2008 02:27:51 +0200, Andi Vajda <[EMAIL PROTECTED]>
wrote:
Are there any actual Windows users (I'm not) on this list (besides Bill)
who have an opinion about this ?
Andi..
We are distributing Java as a subcomponent (a subfolder next to the
embedded Python) under Windows,
Well, everytime I used PyLucene on Windows I came up with that exact same
error and had to "hack" my path. For begginers it's not that easy so, I
believe that if appropriately publicized, ie. "We are going to add this to
your path everytime you run pylucene", I think it is ok :)
___
On Fri, 25 Apr 2008, Bill Janssen wrote:
I'd like to reopen an issue we talked about earlier.
I'm having difficulties running PyLucene 2.4.0 (JCC 1.9, shared) on
Windows XP. I've put the "jcc.dll" file into the
PYTHON/Lib/site-packages/lucene/ directory, which seems to work, but
it's complain
