On Mon, 12 Apr 2010, Bill Janssen wrote:
Andi Vajda <va...@apache.org> wrote:
Well, that's good. What about JCC itself? I'd like something like
import jcc
jcc.VERSION
'2.5.1'
Or
import jcc
jcc.VERSION
(2, 5, 1)
The second form would be more generally useful, I think.
There only is a jcc module at runtime on Windows and then only when
shared mode is used.
Huh? So what's this?
% python
Python 2.5.1 (r251:54863, Feb 6 2009, 19:02:12)
[GCC 4.0.1 (Apple Inc. build 5465)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
import sys
sys.platform
'darwin'
import jcc
Are you saying that jcc need not be installed for PyLucene to be
installed? Sure, that's fine. I'm actually thinking about the case
where jcc is being used to wrap some other library, so in that case
jcc might be there but not lucene.
I'm saying that there are two situations where a jcc module may exist in
your Python VM:
1. at compile time, when you can get VERSION ouf of jcc.config
2. at runtime, where there is no jcc module loaded for you into the
Python VM unless you do it or you're on Windows and are using shared
mode. JCC_VERSION is available from any module that you've built
with JCC regardless of these caveats.
As I'm writing these words, I just realized that's not the case in what I
committed earlier today. It's only in the first module thus imported.
I'm fixing this...
Andi..
