You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@lucene.apache.org by Andi Vajda <va...@apache.org> on 2009/11/26 23:05:07 UTC

[VOTE] Release PyLucene 3.0.0-1

With the recent release of Java Lucene 3.0.0, a PyLucene 3.0.0-1 release 
closely tracking it is ready.

ATTENTION: Lucene Java 3.0.0 has seen many changes to its API. While Java
            users can methodically port their code from Lucene 2.9.1 to
            Lucene 3.0.0 by watching for and eliminating deprecation warnings
            while compiling their code against the Lucene 2.9.1 release, no
            such luxury is afforded to Python users. APIs that were
            deprecated in Lucene 2.x have been removed from Lucene 3.0.0 and
            will trigger Python runtime errors in applications coded with
            PyLucene 2.x. Please, refer to Lucene's 3.0.0 changelist [2], in
            particular to its API changes section [3], for all the details.

Release candidate 1 of PyLucene 3.0.0-1 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/trunk/CHANGES
http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES

Please vote to release these artifacts as PyLucene 3.0.0-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

[1] http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x88E27CA20ED7633F
[2] http://lucene.apache.org/java/3_0_0/changes/Changes.html
[3] http://lucene.apache.org/java/3_0_0/changes/Changes.html#3.0.0.api_changes

Re: [VOTE] Release PyLucene 3.0.0-1

Posted by Michael McCandless <lu...@mikemccandless.com>.
Thanks for the pointers Andi, I think I must've somehow had an older
JCC installed -- when I repeated the usual steps, with the new RC,
things built fine.  User error :)  Thanks!

Mike

On Sun, Nov 29, 2009 at 6:53 PM, Andi Vajda <va...@apache.org> wrote:
>
> On Sun, 29 Nov 2009, Michael McCandless wrote:
>
>> I'm trying to build on Mac OS X 10.5.8, Java 1.6.0_15, Python 2.6.4
>> (that I downloaded & installed from http://python.org).
>>
>> I left JCC's setup.py at its defaults for darwin, and am trying this
>> in PyLucene's Makefile:
>>
>> PREFIX_PYTHON=/usr/local
>> ANT=ant
>> PYTHON=$(PREFIX_PYTHON)/bin/python
>> JCC=$(PYTHON) -m jcc.__main__ --arch i386
>> NUM_FILES=2
>>
>> But I'm hitting many occurrences of this compilation error when
>> compiling __wrap01__.cpp:
>>
>> build/_lucene/__wrap01__.cpp: In static member function 'static void
>> org::apache::lucene::search::t_PrefixQuery::initialize(PyObject*)':
>> build/_lucene/__wrap01__.cpp:104: error: no matching function for call
>> to 'make_descriptor(_jclass* (&)(), int)'
>
> You've probably forgotten to install the latest JCC after building it,
> running against an older version ? Or you're picking up a version of the
> header files you're not expecting to ?
>
> For example, if you installed your own version of Python 2.6.4, are you sure
> that you're then running the same python version when building PyLucene ?
>
> Did you really install Python 2.6.4 into /Library ?
>
> Andi..
>
>>
>> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:76:
>> note: candidates are: PyObject* make_descriptor(PyTypeObject*)
>>
>> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:77:
>> note:                 PyObject* make_descriptor(_jclass* (*)())
>>
>> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:78:
>> note:                 PyObject* make_descriptor(PyObject*)
>>
>> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:79:
>> note:                 PyObject* make_descriptor(PyObject*
>> (*)(_jobject* const&))
>>
>> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:80:
>> note:                 PyObject* make_descriptor(jboolean)
>>
>> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:81:
>> note:                 PyObject* make_descriptor(jbyte)
>>
>> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:82:
>> note:                 PyObject* make_descriptor(jchar)
>>
>> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:83:
>> note:                 PyObject* make_descriptor(jdouble)
>>
>> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:84:
>> note:                 PyObject* make_descriptor(jfloat)
>>
>> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:85:
>> note:                 PyObject* make_descriptor(jint)
>>
>> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:86:
>> note:                 PyObject* make_descriptor(jlong)
>>
>> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:87:
>> note:                 PyObject* make_descriptor(jshort)
>>
>>
>> Any ideas?
>>
>> Mike
>>
>> On Thu, Nov 26, 2009 at 5:05 PM, Andi Vajda <va...@apache.org> wrote:
>>>
>>> With the recent release of Java Lucene 3.0.0, a PyLucene 3.0.0-1 release
>>> closely tracking it is ready.
>>>
>>> ATTENTION: Lucene Java 3.0.0 has seen many changes to its API. While Java
>>>           users can methodically port their code from Lucene 2.9.1 to
>>>           Lucene 3.0.0 by watching for and eliminating deprecation
>>> warnings
>>>           while compiling their code against the Lucene 2.9.1 release, no
>>>           such luxury is afforded to Python users. APIs that were
>>>           deprecated in Lucene 2.x have been removed from Lucene 3.0.0
>>> and
>>>           will trigger Python runtime errors in applications coded with
>>>           PyLucene 2.x. Please, refer to Lucene's 3.0.0 changelist [2],
>>> in
>>>           particular to its API changes section [3], for all the details.
>>>
>>> Release candidate 1 of PyLucene 3.0.0-1 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/trunk/CHANGES
>>> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>>>
>>> Please vote to release these artifacts as PyLucene 3.0.0-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
>>>
>>> [1]
>>> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x88E27CA20ED7633F
>>> [2] http://lucene.apache.org/java/3_0_0/changes/Changes.html
>>> [3]
>>>
>>> http://lucene.apache.org/java/3_0_0/changes/Changes.html#3.0.0.api_changes
>>>
>

Re: [VOTE] Release PyLucene 3.0.0-1

Posted by Andi Vajda <va...@apache.org>.
On Sun, 29 Nov 2009, Michael McCandless wrote:

> I'm trying to build on Mac OS X 10.5.8, Java 1.6.0_15, Python 2.6.4
> (that I downloaded & installed from http://python.org).
>
> I left JCC's setup.py at its defaults for darwin, and am trying this
> in PyLucene's Makefile:
>
> PREFIX_PYTHON=/usr/local
> ANT=ant
> PYTHON=$(PREFIX_PYTHON)/bin/python
> JCC=$(PYTHON) -m jcc.__main__ --arch i386
> NUM_FILES=2
>
> But I'm hitting many occurrences of this compilation error when
> compiling __wrap01__.cpp:
>
> build/_lucene/__wrap01__.cpp: In static member function 'static void
> org::apache::lucene::search::t_PrefixQuery::initialize(PyObject*)':
> build/_lucene/__wrap01__.cpp:104: error: no matching function for call
> to 'make_descriptor(_jclass* (&)(), int)'

You've probably forgotten to install the latest JCC after building it, 
running against an older version ? Or you're picking up a version of the 
header files you're not expecting to ?

For example, if you installed your own version of Python 2.6.4, are you sure 
that you're then running the same python version when building PyLucene ?

Did you really install Python 2.6.4 into /Library ?

Andi..

> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:76:
> note: candidates are: PyObject* make_descriptor(PyTypeObject*)
> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:77:
> note:                 PyObject* make_descriptor(_jclass* (*)())
> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:78:
> note:                 PyObject* make_descriptor(PyObject*)
> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:79:
> note:                 PyObject* make_descriptor(PyObject*
> (*)(_jobject* const&))
> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:80:
> note:                 PyObject* make_descriptor(jboolean)
> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:81:
> note:                 PyObject* make_descriptor(jbyte)
> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:82:
> note:                 PyObject* make_descriptor(jchar)
> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:83:
> note:                 PyObject* make_descriptor(jdouble)
> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:84:
> note:                 PyObject* make_descriptor(jfloat)
> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:85:
> note:                 PyObject* make_descriptor(jint)
> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:86:
> note:                 PyObject* make_descriptor(jlong)
> /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:87:
> note:                 PyObject* make_descriptor(jshort)
>
>
> Any ideas?
>
> Mike
>
> On Thu, Nov 26, 2009 at 5:05 PM, Andi Vajda <va...@apache.org> wrote:
>>
>> With the recent release of Java Lucene 3.0.0, a PyLucene 3.0.0-1 release
>> closely tracking it is ready.
>>
>> ATTENTION: Lucene Java 3.0.0 has seen many changes to its API. While Java
>>           users can methodically port their code from Lucene 2.9.1 to
>>           Lucene 3.0.0 by watching for and eliminating deprecation warnings
>>           while compiling their code against the Lucene 2.9.1 release, no
>>           such luxury is afforded to Python users. APIs that were
>>           deprecated in Lucene 2.x have been removed from Lucene 3.0.0 and
>>           will trigger Python runtime errors in applications coded with
>>           PyLucene 2.x. Please, refer to Lucene's 3.0.0 changelist [2], in
>>           particular to its API changes section [3], for all the details.
>>
>> Release candidate 1 of PyLucene 3.0.0-1 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/trunk/CHANGES
>> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>>
>> Please vote to release these artifacts as PyLucene 3.0.0-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
>>
>> [1] http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x88E27CA20ED7633F
>> [2] http://lucene.apache.org/java/3_0_0/changes/Changes.html
>> [3]
>> http://lucene.apache.org/java/3_0_0/changes/Changes.html#3.0.0.api_changes
>>
>

Re: [VOTE] Release PyLucene 3.0.0-1

Posted by Michael McCandless <lu...@mikemccandless.com>.
I'm trying to build on Mac OS X 10.5.8, Java 1.6.0_15, Python 2.6.4
(that I downloaded & installed from http://python.org).

I left JCC's setup.py at its defaults for darwin, and am trying this
in PyLucene's Makefile:

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

But I'm hitting many occurrences of this compilation error when
compiling __wrap01__.cpp:

build/_lucene/__wrap01__.cpp: In static member function 'static void
org::apache::lucene::search::t_PrefixQuery::initialize(PyObject*)':
build/_lucene/__wrap01__.cpp:104: error: no matching function for call
to 'make_descriptor(_jclass* (&)(), int)'
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:76:
note: candidates are: PyObject* make_descriptor(PyTypeObject*)
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:77:
note:                 PyObject* make_descriptor(_jclass* (*)())
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:78:
note:                 PyObject* make_descriptor(PyObject*)
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:79:
note:                 PyObject* make_descriptor(PyObject*
(*)(_jobject* const&))
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:80:
note:                 PyObject* make_descriptor(jboolean)
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:81:
note:                 PyObject* make_descriptor(jbyte)
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:82:
note:                 PyObject* make_descriptor(jchar)
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:83:
note:                 PyObject* make_descriptor(jdouble)
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:84:
note:                 PyObject* make_descriptor(jfloat)
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:85:
note:                 PyObject* make_descriptor(jint)
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:86:
note:                 PyObject* make_descriptor(jlong)
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/jcc/sources/functions.h:87:
note:                 PyObject* make_descriptor(jshort)


Any ideas?

Mike

On Thu, Nov 26, 2009 at 5:05 PM, Andi Vajda <va...@apache.org> wrote:
>
> With the recent release of Java Lucene 3.0.0, a PyLucene 3.0.0-1 release
> closely tracking it is ready.
>
> ATTENTION: Lucene Java 3.0.0 has seen many changes to its API. While Java
>           users can methodically port their code from Lucene 2.9.1 to
>           Lucene 3.0.0 by watching for and eliminating deprecation warnings
>           while compiling their code against the Lucene 2.9.1 release, no
>           such luxury is afforded to Python users. APIs that were
>           deprecated in Lucene 2.x have been removed from Lucene 3.0.0 and
>           will trigger Python runtime errors in applications coded with
>           PyLucene 2.x. Please, refer to Lucene's 3.0.0 changelist [2], in
>           particular to its API changes section [3], for all the details.
>
> Release candidate 1 of PyLucene 3.0.0-1 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/trunk/CHANGES
> http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES
>
> Please vote to release these artifacts as PyLucene 3.0.0-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
>
> [1] http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x88E27CA20ED7633F
> [2] http://lucene.apache.org/java/3_0_0/changes/Changes.html
> [3]
> http://lucene.apache.org/java/3_0_0/changes/Changes.html#3.0.0.api_changes
>

Re: [VOTE] Release PyLucene 3.0.0-1

Posted by Andi Vajda <va...@apache.org>.
On Sun, 29 Nov 2009, Atsuo Ishimoto wrote:

> Sorry, I failed to attach the patch.
>
> On Sun, Nov 29, 2009 at 11:34 PM, Atsuo Ishimoto
> <at...@gmail.com> wrote:
>> Hi Andi,
>>
>> On Fri, Nov 27, 2009 at 7:05 AM, Andi Vajda <va...@apache.org> wrote:
>>>
>>> With the recent release of Java Lucene 3.0.0, a PyLucene 3.0.0-1 release
>>> closely tracking it is ready.
>>>
>>
>> I failed to build jcc with Microsoft VC2008 on Windows Vista. I
>> attached a patch to fix problem.
>> With this patch, all tests are finished successfully.

Indeed, va_arg() needs this on some compilers.
I've built and tested the latest on Win2k, Solaris, Debian and Mac OS X.
All seems good.

Thanks for the patch !

Andi..

Re: [VOTE] Release PyLucene 3.0.0-1

Posted by Atsuo Ishimoto <at...@gmail.com>.
Sorry, I failed to attach the patch.

On Sun, Nov 29, 2009 at 11:34 PM, Atsuo Ishimoto
<at...@gmail.com> wrote:
> Hi Andi,
>
> On Fri, Nov 27, 2009 at 7:05 AM, Andi Vajda <va...@apache.org> wrote:
>>
>> With the recent release of Java Lucene 3.0.0, a PyLucene 3.0.0-1 release
>> closely tracking it is ready.
>>
>
> I failed to build jcc with Microsoft VC2008 on Windows Vista. I
> attached a patch to fix problem.
> With this patch, all tests are finished successfully.
>
-- 
Atsuo Ishimoto
Mail: ishimoto@gembook.org
Blog: http://d.hatena.ne.jp/atsuoishimoto/
Twitter: atsuoishimoto

Re: [VOTE] Release PyLucene 3.0.0-1

Posted by Atsuo Ishimoto <at...@gmail.com>.
Hi Andi,

On Fri, Nov 27, 2009 at 7:05 AM, Andi Vajda <va...@apache.org> wrote:
>
> With the recent release of Java Lucene 3.0.0, a PyLucene 3.0.0-1 release
> closely tracking it is ready.
>

I failed to build jcc with Microsoft VC2008 on Windows Vista. I
attached a patch to fix problem.
With this patch, all tests are finished successfully.

-- 
Atsuo Ishimoto
Mail: ishimoto@gembook.org
Blog: http://d.hatena.ne.jp/atsuoishimoto/
Twitter: atsuoishimoto