Re: [jira] Commented: (PYLUCENE-3) jcc not compiling on Mac Snow Leopard

2010-04-12 Thread Bill Janssen
Andi Vajda (JIRA) wrote: > Why is this a bug ? I asked about this on the Apple java-dev mailing list a few weeks ago, and got back an answer similar to what Jim suggests. This is from Mike Swingler at Apple (swing...@apple.com): > On Mar 19, 2010, at 9:23 PM, Bill Janssen wrote: > > > [I find

Re: [jira] Commented: (PYLUCENE-3) jcc not compiling on Mac Snow Leopard

2010-04-12 Thread Andi Vajda
Why is Apple installing headers there then ?

jcc version string?

2010-04-12 Thread Bill Janssen
It would be helpful to have a variable jcc.VERSION initialized with the jcc version, either as a string or a tuple sequence. Bill

Re: jcc version string?

2010-04-12 Thread Andi Vajda
On Mon, 12 Apr 2010, Bill Janssen wrote: It would be helpful to have a variable jcc.VERSION initialized with the jcc version, either as a string or a tuple sequence. The following is already available. Is it good enough ? >>> from pkg_resources import require >>> require('jcc') [JCC 2.

Re: jcc version string?

2010-04-12 Thread Bill Janssen
Andi Vajda wrote: > > On Mon, 12 Apr 2010, Bill Janssen wrote: > > > It would be helpful to have a variable jcc.VERSION initialized with the > > jcc version, either as a string or a tuple sequence. > > The following is already available. Is it good enough ? > >>>> from pkg_resources impor

Re: [jira] Commented: (PYLUCENE-3) jcc not compiling on Mac Snow Leopard

2010-04-12 Thread Bill Janssen
Andi Vajda wrote: > Why is Apple installing headers there then ? Not sure. My understanding is that it's best regarded as a transient effect that may go away at any point in the future via a software update. Indeed, with the DP of Snow Leopard, those headers weren't there. Bill

Re: jcc version string?

2010-04-12 Thread Andi Vajda
On Mon, 12 Apr 2010, Bill Janssen wrote: Andi Vajda wrote: On Mon, 12 Apr 2010, Bill Janssen wrote: It would be helpful to have a variable jcc.VERSION initialized with the jcc version, either as a string or a tuple sequence. The following is already available. Is it good enough ? >>>

Re: jcc version string?

2010-04-12 Thread Bill Janssen
Andi Vajda wrote: > On Mon, 12 Apr 2010, Bill Janssen wrote: > > > Andi Vajda wrote: > > > >> > >> On Mon, 12 Apr 2010, Bill Janssen wrote: > >> > >>> It would be helpful to have a variable jcc.VERSION initialized with the > >>> jcc version, either as a string or a tuple sequence. > >> > >> The

Re: jcc version string?

2010-04-12 Thread Andi Vajda
On Mon, 12 Apr 2010, Bill Janssen wrote: Andi Vajda wrote: On Mon, 12 Apr 2010, Bill Janssen wrote: Andi Vajda wrote: On Mon, 12 Apr 2010, Bill Janssen wrote: It would be helpful to have a variable jcc.VERSION initialized with the jcc version, either as a string or a tuple sequence.

Re: jcc version string?

2010-04-12 Thread Bill Janssen
Andi Vajda 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

Re: jcc version string?

2010-04-12 Thread Andi Vajda
On Mon, 12 Apr 2010, Bill Janssen wrote: Andi Vajda 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 modul

Re: jcc version string?

2010-04-12 Thread Bill Janssen
By the way, I'm still getting build failures on the PyLucene trunk on OS X 10.5 with the latest Java compiler: [...] common.compile-core: compile-core: compile-test: [mkdir] Created dir: /private