You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pylucene-dev@lucene.apache.org by Andi Vajda <va...@apache.org> on 2012/12/26 03:56:39 UTC

[VOTE] Release PyLucene 3.6.2

The PyLucene 3.6.2-1 release tracking the recent release of Apache 
Lucene 3.6.2 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/pylucene_3_6/CHANGES

PyLucene 3.6.2 is built with JCC 2.15 included in these release artifacts:
http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES

A list of Lucene Java changes can be seen at:
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_6_2/lucene/CHANGES.txt

Please vote to release these artifacts as PyLucene 3.6.2-1.

Thanks !

Andi..

ps: the KEYS file for PyLucene release signing is at:
http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
http://people.apache.org/~vajda/staging_area/KEYS

pps: here is my +1

Re: [VOTE] Release PyLucene 3.6.2

Posted by Robert Muir <rc...@gmail.com>.
+1

checks out for me on OS X (make, then make test as documented
http://lucene.apache.org/pylucene/install.html).

I hit a snag trying to do 'make test' directly, but I dont think this
should block the release since the instructions say to do them
separately.

On Tue, Dec 25, 2012 at 9:56 PM, Andi Vajda <va...@apache.org> wrote:
>
> The PyLucene 3.6.2-1 release tracking the recent release of Apache Lucene
> 3.6.2 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/pylucene_3_6/CHANGES
>
> PyLucene 3.6.2 is built with JCC 2.15 included in these release artifacts:
> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_6_2/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.6.2-1.
>
> Thanks !
>
> Andi..
>
> ps: the KEYS file for PyLucene release signing is at:
> http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
> http://people.apache.org/~vajda/staging_area/KEYS
>
> pps: here is my +1

Re: [VOTE] Release PyLucene 3.6.2

Posted by Andi Vajda <va...@apache.org>.
On Tue, 25 Dec 2012, Andi Vajda wrote:

>
> The PyLucene 3.6.2-1 release tracking the recent release of Apache Lucene 
> 3.6.2 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/pylucene_3_6/CHANGES
>
> PyLucene 3.6.2 is built with JCC 2.15 included in these release artifacts:
> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_6_2/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.6.2-1.
>
> Thanks !

This vote has passed. Thank you all who voted.
Expect a release announcement shortly.

Andi..

Re: [VOTE] Release PyLucene 3.6.2

Posted by Andi Vajda <va...@apache.org>.
On Tue, 25 Dec 2012, Andi Vajda wrote:

>
> The PyLucene 3.6.2-1 release tracking the recent release of Apache Lucene 
> 3.6.2 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/pylucene_3_6/CHANGES
>
> PyLucene 3.6.2 is built with JCC 2.15 included in these release artifacts:
> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_6_2/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.6.2-1.
>
> Thanks !

This vote has passed. Thank you all who voted.
Expect a release announcement shortly.

Andi..

Re: AW: [VOTE] Release PyLucene 3.6.2

Posted by Andi Vajda <va...@apache.org>.
On Jan 3, 2013, at 2:18, "Thomas Koch" <ko...@orbiteam.de> wrote:

> Maybe I should add that both java and python are universal binary files for
> 32/64 bit : 
> 
> ios:~ koch$ file /usr/bin/java
> /usr/bin/java: Mach-O universal binary with 2 architectures
> /usr/bin/java (for architecture x86_64):    Mach-O 64-bit executable
> x86_64
> /usr/bin/java (for architecture i386):    Mach-O executable i386
> 
> ios:~ koch$ file /usr/bin/python
> /usr/bin/python: Mach-O universal binary with 2 architectures
> /usr/bin/python (for architecture i386):    Mach-O executable i386
> /usr/bin/python (for architecture x86_64):    Mach-O 64-bit executable
> x86_64
> 
> It seems to me that JCC is also build for both architecture because of the
> flags -arch i386 AND -arch x86_64.
> Maybe the warning relates to the 32bit binaries? Just guessing  - don't
> really know how this universal binary compile magic really works ,-(

When building PyLucene on my mac, I only build the 64-bit version by specifying -arch x86_64, skipping the 32-bit version. It cuts build time (and size) in half.

Andi..

> 
> However Apple Docs say one should take care of theses warnings:
> 
> --%<--
> -Wshorten-64-to-32
> 
>    This flag is like -Wconversion, but is specific to 64-bit data types.
> This flag causes GCC to issue a warning whenever a value is implicitly
> converted (truncated) from a 64-bit type to a 32-bit type. You should fix
> any warnings generated by this flag, as they are likely to be bugs.
> --%<--
> Found here:
> https://developer.apple.com/library/mac/#documentation/Darwin/Conceptual/64b
> itPorting/building/building.html
> 
> 
> regards
> Thomas
> 
>> -----Ursprüngliche Nachricht-----
>> Von: Thomas Koch [mailto:koch@orbiteam.de]
>> Gesendet: Donnerstag, 3. Januar 2013 09:54
>> An: pylucene developers
>> Betreff: Re: [VOTE] Release PyLucene 3.6.2
>> ...
>> I'm on 10.8.2 too with builtin python 2.7.2. I used the makefile snippet
> for
>> Mac OS X 10.6 (for 64-bit and 32-bit Python):
>> 
>> PREFIX_PYTHON=/usr
>> ANT=ant
>> PYTHON=$(PREFIX_PYTHON)/bin/python
>> JCC=$(PYTHON) -m jcc.__main__ --shared --arch x86_64 --arch i386
>> NUM_FILES=4
>> 
>> As said: jcc and pylucene both build and run fine…
>> 
>> 
>> regards,
>> Thomas
> 
> 
> 

AW: [VOTE] Release PyLucene 3.6.2

Posted by Thomas Koch <ko...@orbiteam.de>.
Maybe I should add that both java and python are universal binary files for
32/64 bit : 

ios:~ koch$ file /usr/bin/java
/usr/bin/java: Mach-O universal binary with 2 architectures
/usr/bin/java (for architecture x86_64):	Mach-O 64-bit executable
x86_64
/usr/bin/java (for architecture i386):	Mach-O executable i386

ios:~ koch$ file /usr/bin/python
/usr/bin/python: Mach-O universal binary with 2 architectures
/usr/bin/python (for architecture i386):	Mach-O executable i386
/usr/bin/python (for architecture x86_64):	Mach-O 64-bit executable
x86_64

It seems to me that JCC is also build for both architecture because of the
flags -arch i386 AND -arch x86_64.
Maybe the warning relates to the 32bit binaries? Just guessing  - don't
really know how this universal binary compile magic really works ,-(

However Apple Docs say one should take care of theses warnings:

--%<--
-Wshorten-64-to-32

    This flag is like -Wconversion, but is specific to 64-bit data types.
This flag causes GCC to issue a warning whenever a value is implicitly
converted (truncated) from a 64-bit type to a 32-bit type. You should fix
any warnings generated by this flag, as they are likely to be bugs.
--%<--
Found here:
https://developer.apple.com/library/mac/#documentation/Darwin/Conceptual/64b
itPorting/building/building.html


regards
Thomas

> -----Ursprüngliche Nachricht-----
> Von: Thomas Koch [mailto:koch@orbiteam.de]
> Gesendet: Donnerstag, 3. Januar 2013 09:54
> An: pylucene developers
> Betreff: Re: [VOTE] Release PyLucene 3.6.2
> ...
> I'm on 10.8.2 too with builtin python 2.7.2. I used the makefile snippet
for
> Mac OS X 10.6 (for 64-bit and 32-bit Python):
> 
> PREFIX_PYTHON=/usr
> ANT=ant
> PYTHON=$(PREFIX_PYTHON)/bin/python
> JCC=$(PYTHON) -m jcc.__main__ --shared --arch x86_64 --arch i386
> NUM_FILES=4
> 
> As said: jcc and pylucene both build and run fine…
> 
> 
> regards,
> Thomas




Re: [VOTE] Release PyLucene 3.6.2

Posted by Thomas Koch <ko...@orbiteam.de>.
Hi,
I usually get a bunch of compiler warnings during the build (mostly related to implicit type conversion) so I don't pay much attention on it - unless build or test fails…

Just checked the output of my last Mac build and could in deed find similar issues as reported by Mike. See log here: https://dl.dropbox.com/u/4384120/macosbuildjcc215pylucene362log.txt

I'm on 10.8.2 too with builtin python 2.7.2. I used the makefile snippet for Mac OS X 10.6 (for 64-bit and 32-bit Python):

PREFIX_PYTHON=/usr
ANT=ant
PYTHON=$(PREFIX_PYTHON)/bin/python
JCC=$(PYTHON) -m jcc.__main__ --shared --arch x86_64 --arch i386
NUM_FILES=4

As said: jcc and pylucene both build and run fine…


regards,
Thomas
--
Am 03.01.2013 um 01:58 schrieb Andi Vajda <va...@apache.org>:

> 
> On Wed, 2 Jan 2013, Michael McCandless wrote:
> 
>> Sorry for the delay here ... was out on vacation.  Happy new year!
> 
> Happy new year to you too !
> 
>> I tested on OS X 10.8.2, and was able to install & run my usual smoke
>> test (index & search first 100K Wikipedia docs).
>> 
>> But I hit a few strange things ... first, lots of compilation warnings
>> when compiling jcc and pylucene, eg:
>> 
>> In file included from build/_lucene/JArray.cpp:21:
>> /Library/Python/2.7/site-packages/JCC-2.15-py2.7-macosx-10.8-intel.egg/jcc/sources/JArray.h:104:102:
>> warning: implicit conversion loses integer precision: 'Py_ssize_t'
>> (aka 'long') to 'jsize'
>>     (aka 'int') [-Wshorten-64-to-32]
>>   JArray<jobject>(jclass cls, Py_ssize_t n) :
>> java::lang::Object(env->get_vm_env()->NewObjectArray(n, cls, NULL)) {
>>                                                                  ~~~
>>                             ^
> 
> This could be a mismatch between 32-bit Python and 64-bit Java ?
> I don't know for sure, I've not seen this error but it's clearly complaining about losing 32 out of 64 bits somewhere.
> 
>> and:
>> 
>> #define PySequence_Length PySequence_Size
>>                         ^
>> build/_lucene/__wrap05__.cpp:294:16: warning: implicit conversion
>> loses integer precision: 'Py_ssize_t' (aka 'long') to 'unsigned int'
>> [-Wshorten-64-to-32]
>>         if (!parseArgs(args, "s", &a0))
>>              ^~~~~~~~~~~~~~~~~~~~~~~~~
>> /Library/Python/2.7/site-packages/JCC-2.15-py2.7-macosx-10.8-intel.egg/jcc/sources/functions.h:63:43:
>> note: expanded from macro 'parseArgs'
>> 
>> They are all warnings and the compilation succeeded ...
>> 
>> This could easily be user error ... I didn't change anything in jcc's
>> setup.py ... just ran it as was.  And I just uncommented the top "Mac
>> OS X 10.6" section in the Makefile ... Python is 2.7.2, java is
>> 1.6.0_35.
>> 
>> The second strange problem I hit was during "make install" in
>> pylucene: it installed lots of stuff but then hit this odd error:
> 
> Did you run 'make' first, then 'make install' or just 'make install' straight from scratch ?
> 
> Both of these issues could be because you're using the stock Python 2.7 on Mac OS X 10.8.2 ? I've got a custom install for each and every PyLucene branch I maintain and these seem new enough to be correlated to 10.8.2 ? (I just upgraded to that myself two weeks ago).
> 
> Thanks for checking !
> 
> Andi..
> 
>> 
>> Adding lucene 3.6.2 to easy-install.pth file
>> 
>> Installed /Library/Python/2.7/site-packages/lucene-3.6.2-py2.7-macosx-10.8-x86_64.egg
>> Processing dependencies for lucene==3.6.2
>> Searching for lucene==3.6.2
>> Reading http://pypi.python.org/simple/lucene/
>> Couldn't find index page for 'lucene' (maybe misspelled?)
>> Scanning index of all packages (this may take a while)
>> Reading http://pypi.python.org/simple/
>> No local packages or download links found for lucene==3.6.2
>> error: Could not find suitable distribution for
>> Requirement.parse('lucene==3.6.2')
>> make: *** [install] Error 1
>> 
>> Looks like this is the same thing Rob hit during "make test" ... but
>> my "make test" succeeded (after I hit the issue during "make
>> install").
>> 
>> I was then able to run my smoke test and confirmed it was Lucene 3.6.2
>> under the hood ...
>> 
>> But net/net +1 to release: I didn't hit any showstoppers...
>> 
>> Mike McCandless
>> 
>> http://blog.mikemccandless.com
>> 
>> On Wed, Jan 2, 2013 at 5:21 AM, Thomas Koch <ko...@orbiteam.de> wrote:
>>> Update: I was also able to build JCC2.15/PyLucene3.6.2 on Win7(32 bit) with
>>> Python 2.7.2, Java 1.6 and MSVC9.0
>>> 
>>> 
>>> Regards,
>>> Thomas
>>> 
>>> -----Ursprüngliche Nachricht-----
>>> Von: Thomas Koch [mailto:koch@orbiteam.de]
>>> Gesendet: Sonntag, 30. Dezember 2012 15:22
>>> An: pylucene developers
>>> Betreff: Re: [VOTE] Release PyLucene 3.6.2
>>> 
>>> Hi,
>>> build succeeded on MacOS 10.8.2 with Python 2.7.2 and java 1.6.0_37. (=> +1)
>>> 
>>> I'm currently at home (xmas break) and don't have access to my
>>> Windows-build-environment, but can test on Win7 next week too.
>>> 
>>> regards
>>> Thomas
>>> --
>>> Am 26.12.2012 um 03:56 schrieb Andi Vajda <va...@apache.org>:
>>> 
>>>> 
>>>> The PyLucene 3.6.2-1 release tracking the recent release of Apache Lucene
>>> 3.6.2 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/pylucene_3_6/CHANGE
>>> S
>>>> 
>>>> PyLucene 3.6.2 is built with JCC 2.15 included in these release artifacts:
>>>> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>>>> 
>>>> A list of Lucene Java changes can be seen at:
>>>> 
>>> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_6_2/lucene/CHA
>>> NGES.txt
>>>> 
>>>> Please vote to release these artifacts as PyLucene 3.6.2-1.
>>>> 
>>>> Thanks !
>>>> 
>>>> Andi..
>>>> 
>>>> ps: the KEYS file for PyLucene release signing is at:
>>>> http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
>>>> http://people.apache.org/~vajda/staging_area/KEYS
>>>> 
>>>> pps: here is my +1
>>> 
>>> 


Re: [VOTE] Release PyLucene 3.6.2

Posted by Michael McCandless <lu...@mikemccandless.com>.
On Wed, Jan 2, 2013 at 7:58 PM, Andi Vajda <va...@apache.org> wrote:

>> I tested on OS X 10.8.2, and was able to install & run my usual smoke
>> test (index & search first 100K Wikipedia docs).
>>
>> But I hit a few strange things ... first, lots of compilation warnings
>> when compiling jcc and pylucene, eg:
>>
>> In file included from build/_lucene/JArray.cpp:21:
>>
>> /Library/Python/2.7/site-packages/JCC-2.15-py2.7-macosx-10.8-intel.egg/jcc/sources/JArray.h:104:102:
>> warning: implicit conversion loses integer precision: 'Py_ssize_t'
>> (aka 'long') to 'jsize'
>>      (aka 'int') [-Wshorten-64-to-32]
>>    JArray<jobject>(jclass cls, Py_ssize_t n) :
>> java::lang::Object(env->get_vm_env()->NewObjectArray(n, cls, NULL)) {
>>                                                                   ~~~
>>                              ^
>
>
> This could be a mismatch between 32-bit Python and 64-bit Java ?
> I don't know for sure, I've not seen this error but it's clearly complaining
> about losing 32 out of 64 bits somewhere.

Hmm my Python seems to be 64 bit (at least sys.maxint is 64 bits).

>> and:
>>
>> #define PySequence_Length PySequence_Size
>>                          ^
>> build/_lucene/__wrap05__.cpp:294:16: warning: implicit conversion
>> loses integer precision: 'Py_ssize_t' (aka 'long') to 'unsigned int'
>> [-Wshorten-64-to-32]
>>          if (!parseArgs(args, "s", &a0))
>>               ^~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> /Library/Python/2.7/site-packages/JCC-2.15-py2.7-macosx-10.8-intel.egg/jcc/sources/functions.h:63:43:
>> note: expanded from macro 'parseArgs'
>>
>> They are all warnings and the compilation succeeded ...
>>
>> This could easily be user error ... I didn't change anything in jcc's
>> setup.py ... just ran it as was.  And I just uncommented the top "Mac
>> OS X 10.6" section in the Makefile ... Python is 2.7.2, java is
>> 1.6.0_35.
>>
>> The second strange problem I hit was during "make install" in
>> pylucene: it installed lots of stuff but then hit this odd error:
>
>
> Did you run 'make' first, then 'make install' or just 'make install'
> straight from scratch ?

I just ran 'make' alone, first.

> Both of these issues could be because you're using the stock Python 2.7 on
> Mac OS X 10.8.2 ? I've got a custom install for each and every PyLucene
> branch I maintain and these seem new enough to be correlated to 10.8.2 ? (I
> just upgraded to that myself two weeks ago).

I'm pretty sure this is stock Python but not certain ... when I launch
"python" I get:

Python 2.7.2 (default, Jun 20 2012, 16:23:33)
[GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>>

And "file /usr/bin/python":

/usr/bin/python: Mach-O universal binary with 2 architectures
/usr/bin/python (for architecture i386):	Mach-O executable i386
/usr/bin/python (for architecture x86_64):	Mach-O 64-bit executable x86_64

> Thanks for checking !

Thank you!

Mike McCandless

http://blog.mikemccandless.com

Re: [VOTE] Release PyLucene 3.6.2

Posted by Andi Vajda <va...@apache.org>.
On Wed, 2 Jan 2013, Michael McCandless wrote:

> Sorry for the delay here ... was out on vacation.  Happy new year!

Happy new year to you too !

> I tested on OS X 10.8.2, and was able to install & run my usual smoke
> test (index & search first 100K Wikipedia docs).
>
> But I hit a few strange things ... first, lots of compilation warnings
> when compiling jcc and pylucene, eg:
>
> In file included from build/_lucene/JArray.cpp:21:
> /Library/Python/2.7/site-packages/JCC-2.15-py2.7-macosx-10.8-intel.egg/jcc/sources/JArray.h:104:102:
> warning: implicit conversion loses integer precision: 'Py_ssize_t'
> (aka 'long') to 'jsize'
>      (aka 'int') [-Wshorten-64-to-32]
>    JArray<jobject>(jclass cls, Py_ssize_t n) :
> java::lang::Object(env->get_vm_env()->NewObjectArray(n, cls, NULL)) {
>                                                                   ~~~
>                              ^

This could be a mismatch between 32-bit Python and 64-bit Java ?
I don't know for sure, I've not seen this error but it's clearly complaining 
about losing 32 out of 64 bits somewhere.

> and:
>
> #define PySequence_Length PySequence_Size
>                          ^
> build/_lucene/__wrap05__.cpp:294:16: warning: implicit conversion
> loses integer precision: 'Py_ssize_t' (aka 'long') to 'unsigned int'
> [-Wshorten-64-to-32]
>          if (!parseArgs(args, "s", &a0))
>               ^~~~~~~~~~~~~~~~~~~~~~~~~
> /Library/Python/2.7/site-packages/JCC-2.15-py2.7-macosx-10.8-intel.egg/jcc/sources/functions.h:63:43:
> note: expanded from macro 'parseArgs'
>
> They are all warnings and the compilation succeeded ...
>
> This could easily be user error ... I didn't change anything in jcc's
> setup.py ... just ran it as was.  And I just uncommented the top "Mac
> OS X 10.6" section in the Makefile ... Python is 2.7.2, java is
> 1.6.0_35.
>
> The second strange problem I hit was during "make install" in
> pylucene: it installed lots of stuff but then hit this odd error:

Did you run 'make' first, then 'make install' or just 'make install' 
straight from scratch ?

Both of these issues could be because you're using the stock Python 2.7 on 
Mac OS X 10.8.2 ? I've got a custom install for each and every 
PyLucene branch I maintain and these seem new enough to be correlated to 
10.8.2 ? (I just upgraded to that myself two weeks ago).

Thanks for checking !

Andi..

>
> Adding lucene 3.6.2 to easy-install.pth file
>
> Installed /Library/Python/2.7/site-packages/lucene-3.6.2-py2.7-macosx-10.8-x86_64.egg
> Processing dependencies for lucene==3.6.2
> Searching for lucene==3.6.2
> Reading http://pypi.python.org/simple/lucene/
> Couldn't find index page for 'lucene' (maybe misspelled?)
> Scanning index of all packages (this may take a while)
> Reading http://pypi.python.org/simple/
> No local packages or download links found for lucene==3.6.2
> error: Could not find suitable distribution for
> Requirement.parse('lucene==3.6.2')
> make: *** [install] Error 1
>
> Looks like this is the same thing Rob hit during "make test" ... but
> my "make test" succeeded (after I hit the issue during "make
> install").
>
> I was then able to run my smoke test and confirmed it was Lucene 3.6.2
> under the hood ...
>
> But net/net +1 to release: I didn't hit any showstoppers...
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Wed, Jan 2, 2013 at 5:21 AM, Thomas Koch <ko...@orbiteam.de> wrote:
>> Update: I was also able to build JCC2.15/PyLucene3.6.2 on Win7(32 bit) with
>> Python 2.7.2, Java 1.6 and MSVC9.0
>>
>>
>> Regards,
>> Thomas
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Thomas Koch [mailto:koch@orbiteam.de]
>> Gesendet: Sonntag, 30. Dezember 2012 15:22
>> An: pylucene developers
>> Betreff: Re: [VOTE] Release PyLucene 3.6.2
>>
>> Hi,
>> build succeeded on MacOS 10.8.2 with Python 2.7.2 and java 1.6.0_37. (=> +1)
>>
>> I'm currently at home (xmas break) and don't have access to my
>> Windows-build-environment, but can test on Win7 next week too.
>>
>> regards
>> Thomas
>> --
>> Am 26.12.2012 um 03:56 schrieb Andi Vajda <va...@apache.org>:
>>
>>>
>>> The PyLucene 3.6.2-1 release tracking the recent release of Apache Lucene
>> 3.6.2 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/pylucene_3_6/CHANGE
>> S
>>>
>>> PyLucene 3.6.2 is built with JCC 2.15 included in these release artifacts:
>>> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>>>
>>> A list of Lucene Java changes can be seen at:
>>>
>> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_6_2/lucene/CHA
>> NGES.txt
>>>
>>> Please vote to release these artifacts as PyLucene 3.6.2-1.
>>>
>>> Thanks !
>>>
>>> Andi..
>>>
>>> ps: the KEYS file for PyLucene release signing is at:
>>> http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
>>> http://people.apache.org/~vajda/staging_area/KEYS
>>>
>>> pps: here is my +1
>>
>>
>

Re: [VOTE] Release PyLucene 3.6.2

Posted by Michael McCandless <lu...@mikemccandless.com>.
Sorry for the delay here ... was out on vacation.  Happy new year!

I tested on OS X 10.8.2, and was able to install & run my usual smoke
test (index & search first 100K Wikipedia docs).

But I hit a few strange things ... first, lots of compilation warnings
when compiling jcc and pylucene, eg:

In file included from build/_lucene/JArray.cpp:21:
/Library/Python/2.7/site-packages/JCC-2.15-py2.7-macosx-10.8-intel.egg/jcc/sources/JArray.h:104:102:
warning: implicit conversion loses integer precision: 'Py_ssize_t'
(aka 'long') to 'jsize'
      (aka 'int') [-Wshorten-64-to-32]
    JArray<jobject>(jclass cls, Py_ssize_t n) :
java::lang::Object(env->get_vm_env()->NewObjectArray(n, cls, NULL)) {
                                                                   ~~~
                              ^
and:

#define PySequence_Length PySequence_Size
                          ^
build/_lucene/__wrap05__.cpp:294:16: warning: implicit conversion
loses integer precision: 'Py_ssize_t' (aka 'long') to 'unsigned int'
[-Wshorten-64-to-32]
          if (!parseArgs(args, "s", &a0))
               ^~~~~~~~~~~~~~~~~~~~~~~~~
/Library/Python/2.7/site-packages/JCC-2.15-py2.7-macosx-10.8-intel.egg/jcc/sources/functions.h:63:43:
note: expanded from macro 'parseArgs'

They are all warnings and the compilation succeeded ...

This could easily be user error ... I didn't change anything in jcc's
setup.py ... just ran it as was.  And I just uncommented the top "Mac
OS X 10.6" section in the Makefile ... Python is 2.7.2, java is
1.6.0_35.

The second strange problem I hit was during "make install" in
pylucene: it installed lots of stuff but then hit this odd error:

Adding lucene 3.6.2 to easy-install.pth file

Installed /Library/Python/2.7/site-packages/lucene-3.6.2-py2.7-macosx-10.8-x86_64.egg
Processing dependencies for lucene==3.6.2
Searching for lucene==3.6.2
Reading http://pypi.python.org/simple/lucene/
Couldn't find index page for 'lucene' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading http://pypi.python.org/simple/
No local packages or download links found for lucene==3.6.2
error: Could not find suitable distribution for
Requirement.parse('lucene==3.6.2')
make: *** [install] Error 1

Looks like this is the same thing Rob hit during "make test" ... but
my "make test" succeeded (after I hit the issue during "make
install").

I was then able to run my smoke test and confirmed it was Lucene 3.6.2
under the hood ...

But net/net +1 to release: I didn't hit any showstoppers...

Mike McCandless

http://blog.mikemccandless.com

On Wed, Jan 2, 2013 at 5:21 AM, Thomas Koch <ko...@orbiteam.de> wrote:
> Update: I was also able to build JCC2.15/PyLucene3.6.2 on Win7(32 bit) with
> Python 2.7.2, Java 1.6 and MSVC9.0
>
>
> Regards,
> Thomas
>
> -----Ursprüngliche Nachricht-----
> Von: Thomas Koch [mailto:koch@orbiteam.de]
> Gesendet: Sonntag, 30. Dezember 2012 15:22
> An: pylucene developers
> Betreff: Re: [VOTE] Release PyLucene 3.6.2
>
> Hi,
> build succeeded on MacOS 10.8.2 with Python 2.7.2 and java 1.6.0_37. (=> +1)
>
> I'm currently at home (xmas break) and don't have access to my
> Windows-build-environment, but can test on Win7 next week too.
>
> regards
> Thomas
> --
> Am 26.12.2012 um 03:56 schrieb Andi Vajda <va...@apache.org>:
>
>>
>> The PyLucene 3.6.2-1 release tracking the recent release of Apache Lucene
> 3.6.2 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/pylucene_3_6/CHANGE
> S
>>
>> PyLucene 3.6.2 is built with JCC 2.15 included in these release artifacts:
>> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>>
>> A list of Lucene Java changes can be seen at:
>>
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_6_2/lucene/CHA
> NGES.txt
>>
>> Please vote to release these artifacts as PyLucene 3.6.2-1.
>>
>> Thanks !
>>
>> Andi..
>>
>> ps: the KEYS file for PyLucene release signing is at:
>> http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
>> http://people.apache.org/~vajda/staging_area/KEYS
>>
>> pps: here is my +1
>
>

AW: [VOTE] Release PyLucene 3.6.2

Posted by Thomas Koch <ko...@orbiteam.de>.
Update: I was also able to build JCC2.15/PyLucene3.6.2 on Win7(32 bit) with
Python 2.7.2, Java 1.6 and MSVC9.0


Regards,
Thomas

-----Ursprüngliche Nachricht-----
Von: Thomas Koch [mailto:koch@orbiteam.de] 
Gesendet: Sonntag, 30. Dezember 2012 15:22
An: pylucene developers
Betreff: Re: [VOTE] Release PyLucene 3.6.2

Hi,
build succeeded on MacOS 10.8.2 with Python 2.7.2 and java 1.6.0_37. (=> +1)

I'm currently at home (xmas break) and don't have access to my
Windows-build-environment, but can test on Win7 next week too.

regards
Thomas
--
Am 26.12.2012 um 03:56 schrieb Andi Vajda <va...@apache.org>:

> 
> The PyLucene 3.6.2-1 release tracking the recent release of Apache Lucene
3.6.2 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/pylucene_3_6/CHANGE
S
> 
> PyLucene 3.6.2 is built with JCC 2.15 included in these release artifacts:
> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
> 
> A list of Lucene Java changes can be seen at:
>
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_6_2/lucene/CHA
NGES.txt
> 
> Please vote to release these artifacts as PyLucene 3.6.2-1.
> 
> Thanks !
> 
> Andi..
> 
> ps: the KEYS file for PyLucene release signing is at:
> http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
> http://people.apache.org/~vajda/staging_area/KEYS
> 
> pps: here is my +1



Re: [VOTE] Release PyLucene 3.6.2

Posted by Thomas Koch <ko...@orbiteam.de>.
Hi,
build succeeded on MacOS 10.8.2 with Python 2.7.2 and java 1.6.0_37. (=> +1)

I'm currently at home (xmas break) and don't have access to my Windows-build-environment, but can test on Win7 next week too.

regards
Thomas
--
Am 26.12.2012 um 03:56 schrieb Andi Vajda <va...@apache.org>:

> 
> The PyLucene 3.6.2-1 release tracking the recent release of Apache Lucene 3.6.2 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/pylucene_3_6/CHANGES
> 
> PyLucene 3.6.2 is built with JCC 2.15 included in these release artifacts:
> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
> 
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_6_2/lucene/CHANGES.txt
> 
> Please vote to release these artifacts as PyLucene 3.6.2-1.
> 
> Thanks !
> 
> Andi..
> 
> ps: the KEYS file for PyLucene release signing is at:
> http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
> http://people.apache.org/~vajda/staging_area/KEYS
> 
> pps: here is my +1


Re: [VOTE] Release PyLucene 3.6.2

Posted by Andi Vajda <va...@apache.org>.
On Wed, 26 Dec 2012, Andi Vajda wrote:

>
> On Dec 26, 2012, at 11:58, Robert Muir <rc...@gmail.com> wrote:
>
>> On Wed, Dec 26, 2012 at 11:14 AM, Andi Vajda <va...@apache.org> wrote:
>>>
>>> Very strange. Why would it go out to pypi to install unrelated packages ?
>>> Odd. Did you run just 'make' first before running 'make test' ? (my workflow).
>>>
>>
>> I just tried make, followed by make test, and it worked fine. So I
>> think i must have just tried 'make test' in one shot... must be a
>> little build thing.
>>
>> doesn't seem like a blocker to me, just seemed a bit odd.
>
> I'll see if I can reproduce this. Thank you for the clarification.

I did reproduce something similar running 'make test' after 'make clean'. 
Adding a dependency on 'all' fixed it.

Andi..

>
> Andi..
>
>

Re: [VOTE] Release PyLucene 3.6.2

Posted by Andi Vajda <va...@apache.org>.
On Dec 26, 2012, at 11:58, Robert Muir <rc...@gmail.com> wrote:

> On Wed, Dec 26, 2012 at 11:14 AM, Andi Vajda <va...@apache.org> wrote:
>> 
>> Very strange. Why would it go out to pypi to install unrelated packages ?
>> Odd. Did you run just 'make' first before running 'make test' ? (my workflow).
>> 
> 
> I just tried make, followed by make test, and it worked fine. So I
> think i must have just tried 'make test' in one shot... must be a
> little build thing.
> 
> doesn't seem like a blocker to me, just seemed a bit odd.

I'll see if I can reproduce this. Thank you for the clarification.

Andi..


Re: [VOTE] Release PyLucene 3.6.2

Posted by Robert Muir <rc...@gmail.com>.
On Wed, Dec 26, 2012 at 11:14 AM, Andi Vajda <va...@apache.org> wrote:
>
> Very strange. Why would it go out to pypi to install unrelated packages ?
> Odd. Did you run just 'make' first before running 'make test' ? (my workflow).
>

I just tried make, followed by make test, and it worked fine. So I
think i must have just tried 'make test' in one shot... must be a
little build thing.

doesn't seem like a blocker to me, just seemed a bit odd.

Re: [VOTE] Release PyLucene 3.6.2

Posted by Andi Vajda <va...@apache.org>.
On Dec 26, 2012, at 10:50, Robert Muir <rc...@gmail.com> wrote:

> On OS X, i had to run 'make test' twice. The first time, i got a strange error:
> 
> Installed /Users/rmuir/pylucene/pylucene-3.6.2-1/build/test/lucene-3.6.2-py2.7-macosx-10.7-x86_64.egg
> Processing dependencies for lucene==3.6.2
> Searching for lucene==3.6.2
> Reading http://pypi.python.org/simple/lucene/
> Couldn't find index page for 'lucene' (maybe misspelled?)
> Scanning index of all packages (this may take a while)
> Reading http://pypi.python.org/simple/
> No local packages or download links found for lucene==3.6.2
> error: Could not find suitable distribution for
> Requirement.parse('lucene==3.6.2')
> make: *** [install-test] Error 1
> 
> I just ran it again and it worked...

Very strange. Why would it go out to pypi to install unrelated packages ?
Odd. Did you run just 'make' first before running 'make test' ? (my workflow).

Andi..

> 
> On Tue, Dec 25, 2012 at 6:56 PM, Andi Vajda <va...@apache.org> wrote:
>> 
>> The PyLucene 3.6.2-1 release tracking the recent release of Apache Lucene
>> 3.6.2 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/pylucene_3_6/CHANGES
>> 
>> PyLucene 3.6.2 is built with JCC 2.15 included in these release artifacts:
>> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>> 
>> A list of Lucene Java changes can be seen at:
>> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_6_2/lucene/CHANGES.txt
>> 
>> Please vote to release these artifacts as PyLucene 3.6.2-1.
>> 
>> Thanks !
>> 
>> Andi..
>> 
>> ps: the KEYS file for PyLucene release signing is at:
>> http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
>> http://people.apache.org/~vajda/staging_area/KEYS
>> 
>> pps: here is my +1

Re: [VOTE] Release PyLucene 3.6.2

Posted by Robert Muir <rc...@gmail.com>.
On OS X, i had to run 'make test' twice. The first time, i got a strange error:

Installed /Users/rmuir/pylucene/pylucene-3.6.2-1/build/test/lucene-3.6.2-py2.7-macosx-10.7-x86_64.egg
Processing dependencies for lucene==3.6.2
Searching for lucene==3.6.2
Reading http://pypi.python.org/simple/lucene/
Couldn't find index page for 'lucene' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading http://pypi.python.org/simple/
No local packages or download links found for lucene==3.6.2
error: Could not find suitable distribution for
Requirement.parse('lucene==3.6.2')
make: *** [install-test] Error 1

I just ran it again and it worked...

On Tue, Dec 25, 2012 at 6:56 PM, Andi Vajda <va...@apache.org> wrote:
>
> The PyLucene 3.6.2-1 release tracking the recent release of Apache Lucene
> 3.6.2 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/pylucene_3_6/CHANGES
>
> PyLucene 3.6.2 is built with JCC 2.15 included in these release artifacts:
> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_6_2/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.6.2-1.
>
> Thanks !
>
> Andi..
>
> ps: the KEYS file for PyLucene release signing is at:
> http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
> http://people.apache.org/~vajda/staging_area/KEYS
>
> pps: here is my +1

Re: [VOTE] Release PyLucene 3.6.2

Posted by Robert Muir <rc...@gmail.com>.
+1

checks out for me on OS X (make, then make test as documented
http://lucene.apache.org/pylucene/install.html).

I hit a snag trying to do 'make test' directly, but I dont think this
should block the release since the instructions say to do them
separately.

On Tue, Dec 25, 2012 at 9:56 PM, Andi Vajda <va...@apache.org> wrote:
>
> The PyLucene 3.6.2-1 release tracking the recent release of Apache Lucene
> 3.6.2 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/pylucene_3_6/CHANGES
>
> PyLucene 3.6.2 is built with JCC 2.15 included in these release artifacts:
> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_6_2/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.6.2-1.
>
> Thanks !
>
> Andi..
>
> ps: the KEYS file for PyLucene release signing is at:
> http://svn.apache.org/repos/asf/lucene/pylucene/dist/KEYS
> http://people.apache.org/~vajda/staging_area/KEYS
>
> pps: here is my +1