Re: [VOTE] Release PyLucene 3.5.0 rc3

2011-12-12 Thread Andi Vajda
On Thu, 8 Dec 2011, Andi Vajda wrote: There were some issues again with rc2. Thank you all for having reported them ! Please vote on rc3: This vote has passed. Thank you all who voted. A release announcement should follow shortly. Andi.. The PyLucene 3.5.0-3 release closely tracking the

Re: [VOTE] Release PyLucene 3.5.0 rc3

2011-12-10 Thread Bill Janssen
Just built on XP with MinGW, Python 2.6, and "make test" seems to work fine. Bill

Re: [VOTE] Release PyLucene 3.5.0 rc3

2011-12-10 Thread Robert Muir
On Fri, Dec 9, 2011 at 12:26 AM, Andi Vajda wrote: > > There were some issues again with rc2. > Thank you all for having reported them ! > > Please vote on rc3: > +1. RC3 Built fine and tests pass on my mac (10.6.8) -- lucidimagination.com

Re: [VOTE] Release PyLucene 3.5.0 rc3

2011-12-09 Thread Christian Heimes
Am 09.12.2011 06:26, schrieb Andi Vajda: > > There were some issues again with rc2. > Thank you all for having reported them ! > > Please vote on rc3: > > The PyLucene 3.5.0-3 release closely tracking the recent release of > Apache Lucene 3.5.0 is ready. > > A release candidate is available fro

AW: [VOTE] Release PyLucene 3.5.0 rc3

2011-12-09 Thread Thomas Koch
Cc: gene...@lucene.apache.org Betreff: [VOTE] Release PyLucene 3.5.0 rc3 There were some issues again with rc2. Thank you all for having reported them ! Please vote on rc3: The PyLucene 3.5.0-3 release closely tracking the recent release of Apache Lucene 3.5.0 is ready. A release candidate is availa

Re: [VOTE] Release PyLucene 3.5.0 rc3

2011-12-08 Thread Bill Janssen
> A release candidate is available from: > http://people.apache.org/~vajda/staging_area/ Works on my OS X 10.5 machine. Bill

[VOTE] Release PyLucene 3.5.0 rc3

2011-12-08 Thread Andi Vajda
There were some issues again with rc2. Thank you all for having reported them ! Please vote on rc3: The PyLucene 3.5.0-3 release closely tracking the recent release of Apache Lucene 3.5.0 is ready. A release candidate is available from: http://people.apache.org/~vajda/staging_area/ A list of

Re: [VOTE] Release PyLucene 3.5.0 rc2

2011-12-08 Thread Bill Janssen
Andi Vajda wrote: > On Thu, 8 Dec 2011, Bill Janssen wrote: > > > Andi Vajda wrote: > > > >> from _jcc import initVM > > > > I believe that in the statement "from X import Y", X and Y are > > essentially strings, not runtime-evaluated values. So what would > > work would be > > > > from jcc.

Re: [VOTE] Release PyLucene 3.5.0 rc2

2011-12-08 Thread Andi Vajda
On Thu, 8 Dec 2011, Bill Janssen wrote: Andi Vajda wrote: from _jcc import initVM I believe that in the statement "from X import Y", X and Y are essentially strings, not runtime-evaluated values. So what would work would be from jcc._jcc import initVM or initVM = _jcc.initVM Than

Re: [VOTE] Release PyLucene 3.5.0 rc2

2011-12-08 Thread Andi Vajda
On Thu, 8 Dec 2011, Bill Janssen wrote: Andi Vajda wrote: It seems that adding, before if __name__ == '__main__': from jcc import _jcc works just fine on 2.7 and 2.6 as well. Yes, this works on 2.5, as well. Speaking of which, I don't see when __name__ would be == '__main__'. I tried

Re: [VOTE] Release PyLucene 3.5.0 rc2

2011-12-08 Thread Andi Vajda
On Thu, 8 Dec 2011, Bill Janssen wrote: Andi Vajda wrote: Yes, I could see that. setuptools plays all kinds of games to achieve its ends, some of them broken. Thank heaven for distutils2/packaging. What ? another 'dist' thing ? So that leaves us with distutils 1, 2, setuptools and distri

Re: [VOTE] Release PyLucene 3.5.0 rc2

2011-12-08 Thread Andi Vajda
On Thu, 8 Dec 2011, Andi Vajda wrote: It doesn't look like this statement is needed either. Can you remember why it was there ? (not saying you put it there, just asking, I'm blanking) Maybe just replacing the whole 'if __name__ ...' block with just: from jcc import _jcc is enough for all

Re: [VOTE] Release PyLucene 3.5.0 rc2

2011-12-08 Thread Andi Vajda
On Thu, 8 Dec 2011, Andi Vajda wrote: It seems that adding, before if __name__ == '__main__': from jcc import _jcc works just fine on 2.7 and 2.6 as well. Speaking of which, I don't see when __name__ would be == '__main__'. I tried various combinations with pdb and __name__ is always == 'jc

Re: [VOTE] Release PyLucene 3.5.0 rc2

2011-12-08 Thread Andi Vajda
On Thu, 8 Dec 2011, Andi Vajda wrote: On Dec 8, 2011, at 9:11, Bill Janssen wrote: Andi Vajda wrote: On Wed, 7 Dec 2011, Bill Janssen wrote: This part of the PyLucene Makefile is still screwed up: # Mac OS X 10.5 (32-bit Python 2.5, Java 1.5) #PREFIX_PYTHON=/usr #ANT=ant #PYTHON=$(PR

Re: [VOTE] Release PyLucene 3.5.0 rc2

2011-12-08 Thread Andi Vajda
On Dec 8, 2011, at 9:11, Bill Janssen wrote: > Andi Vajda wrote: > >> >> On Wed, 7 Dec 2011, Bill Janssen wrote: >> >>> This part of the PyLucene Makefile is still screwed up: >>> >>> # Mac OS X 10.5 (32-bit Python 2.5, Java 1.5) >>> #PREFIX_PYTHON=/usr >>> #ANT=ant >>> #PYTHON=$(PREFIX_PYT

Re: [VOTE] Release PyLucene 3.5.0 rc2

2011-12-08 Thread Bill Janssen
Andi Vajda wrote: > > On Wed, 7 Dec 2011, Bill Janssen wrote: > > > This part of the PyLucene Makefile is still screwed up: > > > > # Mac OS X 10.5 (32-bit Python 2.5, Java 1.5) > > #PREFIX_PYTHON=/usr > > #ANT=ant > > #PYTHON=$(PREFIX_PYTHON)/bin/python > > #JCC=$(PYTHON) -m jcc --shared > > #

Re: [VOTE] Release PyLucene 3.5.0 rc2

2011-12-07 Thread Andi Vajda
On Wed, 7 Dec 2011, Bill Janssen wrote: This part of the PyLucene Makefile is still screwed up: # Mac OS X 10.5 (32-bit Python 2.5, Java 1.5) #PREFIX_PYTHON=/usr #ANT=ant #PYTHON=$(PREFIX_PYTHON)/bin/python #JCC=$(PYTHON) -m jcc --shared #NUM_FILES=4 The way that jcc/__init__.py is now writte

Re: [VOTE] Release PyLucene 3.5.0 rc2

2011-12-07 Thread Bill Janssen
My Leopard machine is happy with this one. "make test" works, and my code seems to work with it, as well. Bill

Re: [VOTE] Release PyLucene 3.5.0 rc2

2011-12-07 Thread Bill Janssen
This part of the PyLucene Makefile is still screwed up: # Mac OS X 10.5 (32-bit Python 2.5, Java 1.5) #PREFIX_PYTHON=/usr #ANT=ant #PYTHON=$(PREFIX_PYTHON)/bin/python #JCC=$(PYTHON) -m jcc --shared #NUM_FILES=4 The way that jcc/__init__.py is now written, there's no way to invoke it with "-m jcc"

Re: [VOTE] Release PyLucene 3.5.0

2011-12-07 Thread Andi Vajda
On Dec 7, 2011, at 17:18, Bill Janssen wrote: > Bill Janssen wrote: > >> Tried this on Windows XP with MinGW, gcc 4.5, Python 2.6, Java 1.6. >> >> Builds and installs OK. >> >> "make test" reveals some failures: >> >> * test_removeDocument fails badly with lots of these: > > Same with 3.5

Re: [VOTE] Release PyLucene 3.5.0 rc2

2011-12-07 Thread Andi Vajda
On Dec 7, 2011, at 17:15, Bill Janssen wrote: > My Windows machine is mentioning "ICU not installed". Not a problem. > Shouldn't the Makefile conditionalize the wrapping of > ICUNormalizer2Filter.py, ICUFoldingFilter.py, and ICUTransformFilter.py > on that? Not sure what you mean here by wrap

Re: [VOTE] Release PyLucene 3.5.0

2011-12-07 Thread Bill Janssen
Bill Janssen wrote: > Tried this on Windows XP with MinGW, gcc 4.5, Python 2.6, Java 1.6. > > Builds and installs OK. > > "make test" reveals some failures: > > * test_removeDocument fails badly with lots of these: Same with 3.5.0-2. ThaiAnalyzerTestCase also fails: ==

Re: [VOTE] Release PyLucene 3.5.0

2011-12-07 Thread Andi Vajda
On Dec 7, 2011, at 17:04, Bill Janssen wrote: > Tried this on Windows XP with MinGW, gcc 4.5, Python 2.6, Java 1.6. > > Builds and installs OK. > > "make test" reveals some failures: > > * test_removeDocument fails badly with lots of these: > > ERROR: test_removeDocument (__main__.PythonDir

Re: [VOTE] Release PyLucene 3.5.0 rc2

2011-12-07 Thread Bill Janssen
My Windows machine is mentioning "ICU not installed". Shouldn't the Makefile conditionalize the wrapping of ICUNormalizer2Filter.py, ICUFoldingFilter.py, and ICUTransformFilter.py on that? Bill

Re: [VOTE] Release PyLucene 3.5.0

2011-12-07 Thread Bill Janssen
Tried this on Windows XP with MinGW, gcc 4.5, Python 2.6, Java 1.6. Builds and installs OK. "make test" reveals some failures: * test_removeDocument fails badly with lots of these: ERROR: test_removeDocument (__main__.PythonDirectoryTests) -

[VOTE] Release PyLucene 3.5.0 rc2

2011-12-07 Thread Andi Vajda
There were some issues with rc1. Thank you all for having reported them ! Please vote on rc2: The PyLucene 3.5.0-2 release closely tracking the recent release of Apache Lucene 3.5.0 is ready. A release candidate is available from: http://people.apache.org/~vajda/staging_area/ A list of changes

[VOTE] Release PyLucene 3.5.0

2011-12-06 Thread Andi Vajda
The PyLucene 3.5.0-1 release closely tracking the recent release of Apache Lucene 3.5.0 is ready. A release candidate is available from: http://people.apache.org/~vajda/staging_area/ A list of changes in this release can be seen at: http://svn.apache.org/repos/asf/lucene/pylucene/branches/pyluc