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 2010/12/05 07:50:24 UTC
[VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
With the recent releases of Lucene Java 2.9.4 and 3.0.3, the PyLucene
2.9.4-1 and 3.0.3-1 releases closely tracking them are ready.
Release candidates are 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_2_9/CHANGES
http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_0/CHANGES
All versions of PyLucene are built with the same version of JCC, currently
version 2.7, included in these release artifacts.
A list of Lucene Java changes can be seen at:
http://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/CHANGES.txt
http://svn.apache.org/repos/asf/lucene/java/branches/lucene_3_0/CHANGES.txt
Please vote to release these artifacts as PyLucene 2.9.4-1 and 3.0.3-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.1.0
Posted by Grant Ingersoll <gs...@apache.org>.
+1
On Apr 2, 2011, at 4:28 PM, Andi Vajda wrote:
>
> The PyLucene 3.1.0-1 release closely tracking the recent release of Lucene
> Java 3.1.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/pylucene_3_1/CHANGES
>
> PyLucene 3.1.0 is built with JCC 2.8 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_1/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.1.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
>
> pps: here is my +1
--------------------------
Grant Ingersoll
Lucene Revolution -- Lucene and Solr User Conference
May 25-26 in San Francisco
www.lucenerevolution.org
Re: [VOTE] Release PyLucene 3.1.0
Posted by Grant Ingersoll <gs...@apache.org>.
+1
On Apr 2, 2011, at 4:28 PM, Andi Vajda wrote:
>
> The PyLucene 3.1.0-1 release closely tracking the recent release of Lucene
> Java 3.1.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/pylucene_3_1/CHANGES
>
> PyLucene 3.1.0 is built with JCC 2.8 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_1/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.1.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
>
> pps: here is my +1
--------------------------
Grant Ingersoll
Lucene Revolution -- Lucene and Solr User Conference
May 25-26 in San Francisco
www.lucenerevolution.org
Re: [VOTE] Release PyLucene 3.1.0
Posted by Andi Vajda <va...@apache.org>.
On Wed, 6 Apr 2011, Michael McCandless wrote:
> On Wed, Apr 6, 2011 at 6:38 PM, Andi Vajda <va...@apache.org> wrote:
>>
>> On Wed, 6 Apr 2011, Bill Janssen wrote:
>>
>>> Andi Vajda <va...@apache.org> wrote:
>>>
>>>> Unless I'm missing something here, you've got two options before you
>>>> break your users:
>>>> 1. fix your code before you ship it to them
>>>
>>> Unfortunately, the code is out there for building, and the instructions,
>>> also already out there, say, "PyLucene 2.4 to 3.X". I should be more
>>> careful :-).
>>
>> Given that APIs changed quite a bit between 2.x and 3.0 and that 2.x
>> deprecated APIs are removed from 3.1+ (unless I'm confused about Lucene's
>> deprecation policy (*)), your statement is a bit optimistic.
>>
>> (*) maybe it's not until 4.0 that they're going to be removed ? I can't
>> remember at the moment. Mike, if you read this, can you please correct
>> me if I'm wrong ?
>
> Actually, any API deprecated in any Lucene 2.x release is removed in
> 3.0. (Same for 3.x to 4.0, etc.).
Ah, I thought 3.0 had them both. Ok, duly noted.
Thanks !
Andi..
Re: [VOTE] Release PyLucene 3.1.0
Posted by Michael McCandless <lu...@mikemccandless.com>.
On Wed, Apr 6, 2011 at 6:38 PM, Andi Vajda <va...@apache.org> wrote:
>
> On Wed, 6 Apr 2011, Bill Janssen wrote:
>
>> Andi Vajda <va...@apache.org> wrote:
>>
>>> Unless I'm missing something here, you've got two options before you
>>> break your users:
>>> 1. fix your code before you ship it to them
>>
>> Unfortunately, the code is out there for building, and the instructions,
>> also already out there, say, "PyLucene 2.4 to 3.X". I should be more
>> careful :-).
>
> Given that APIs changed quite a bit between 2.x and 3.0 and that 2.x
> deprecated APIs are removed from 3.1+ (unless I'm confused about Lucene's
> deprecation policy (*)), your statement is a bit optimistic.
>
> (*) maybe it's not until 4.0 that they're going to be removed ? I can't
> remember at the moment. Mike, if you read this, can you please correct
> me if I'm wrong ?
Actually, any API deprecated in any Lucene 2.x release is removed in
3.0. (Same for 3.x to 4.0, etc.).
Mike
http://blog.mikemccandless.com
Re: [VOTE] Release PyLucene 3.1.0
Posted by Andi Vajda <va...@apache.org>.
On Wed, 6 Apr 2011, Bill Janssen wrote:
> Andi Vajda <va...@apache.org> wrote:
>
>> There are two versions available from the lucene module:
>>
>> >>> import lucene
>> >>> [(v, lucene.__dict__[v]) for v in dir(lucene) if 'VERSION' in v]
>> [('JCC_VERSION', '2.8'), ('VERSION', '3.1.0')]
>
> I suppose I could make a list of all the (JCC_VERSION, VERSION) pairs
> that I've personally verified that the code works with, and raise an error
> if a user attempts to install UpLib using a PyLucene that isn't on that
> list... But that seems like a sub-optimal solution :-).
Seems like the best solution to me.
How can you be sure your code works otherwise ?
Andi..
Re: [VOTE] Release PyLucene 3.1.0
Posted by Bill Janssen <ja...@parc.com>.
Andi Vajda <va...@apache.org> wrote:
> There are two versions available from the lucene module:
>
> >>> import lucene
> >>> [(v, lucene.__dict__[v]) for v in dir(lucene) if 'VERSION' in v]
> [('JCC_VERSION', '2.8'), ('VERSION', '3.1.0')]
I suppose I could make a list of all the (JCC_VERSION, VERSION) pairs
that I've personally verified that the code works with, and raise an error
if a user attempts to install UpLib using a PyLucene that isn't on that
list... But that seems like a sub-optimal solution :-).
Bill
Re: [VOTE] Release PyLucene 3.1.0
Posted by Andi Vajda <va...@apache.org>.
On Wed, 6 Apr 2011, Bill Janssen wrote:
> Andi Vajda <va...@apache.org> wrote:
>
>>
>> On Wed, 6 Apr 2011, Bill Janssen wrote:
>>
>>> Andi Vajda <va...@apache.org> wrote:
>>>
>>>> Unless I'm missing something here, you've got two options before you
>>>> break your users:
>>>> 1. fix your code before you ship it to them
>>>
>>> Unfortunately, the code is out there for building, and the instructions,
>>> also already out there, say, "PyLucene 2.4 to 3.X". I should be more
>>> careful :-).
>>
>> Given that APIs changed quite a bit between 2.x and 3.0 and that 2.x
>> deprecated APIs are removed from 3.1+ (unless I'm confused about
>> Lucene's deprecation policy (*)), your statement is a bit optimistic.
>
> My Python code looks for the differences and handles it. Of course, it
> can't do that for the future :-).
>
> Is there some ABI version # that I should be checking, instead?
There are two versions available from the lucene module:
>>> import lucene
>>> [(v, lucene.__dict__[v]) for v in dir(lucene) if 'VERSION' in v]
[('JCC_VERSION', '2.8'), ('VERSION', '3.1.0')]
There is also the lucene.Version object.
Andi..
Re: [VOTE] Release PyLucene 3.1.0
Posted by Bill Janssen <ja...@parc.com>.
Andi Vajda <va...@apache.org> wrote:
>
> On Wed, 6 Apr 2011, Bill Janssen wrote:
>
> > Andi Vajda <va...@apache.org> wrote:
> >
> >> Unless I'm missing something here, you've got two options before you
> >> break your users:
> >> 1. fix your code before you ship it to them
> >
> > Unfortunately, the code is out there for building, and the instructions,
> > also already out there, say, "PyLucene 2.4 to 3.X". I should be more
> > careful :-).
>
> Given that APIs changed quite a bit between 2.x and 3.0 and that 2.x
> deprecated APIs are removed from 3.1+ (unless I'm confused about
> Lucene's deprecation policy (*)), your statement is a bit optimistic.
My Python code looks for the differences and handles it. Of course, it
can't do that for the future :-).
Is there some ABI version # that I should be checking, instead?
Bill
Re: [VOTE] Release PyLucene 3.1.0
Posted by Andi Vajda <va...@apache.org>.
On Wed, 6 Apr 2011, Bill Janssen wrote:
> Andi Vajda <va...@apache.org> wrote:
>
>> Unless I'm missing something here, you've got two options before you
>> break your users:
>> 1. fix your code before you ship it to them
>
> Unfortunately, the code is out there for building, and the instructions,
> also already out there, say, "PyLucene 2.4 to 3.X". I should be more
> careful :-).
Given that APIs changed quite a bit between 2.x and 3.0 and that
2.x deprecated APIs are removed from 3.1+ (unless I'm confused about
Lucene's deprecation policy (*)), your statement is a bit optimistic.
(*) maybe it's not until 4.0 that they're going to be removed ? I can't
remember at the moment. Mike, if you read this, can you please correct
me if I'm wrong ?
Andi..
>
>> 2. don't upgrade
>
> It's the users that upgrade, not me.
>
>> Yes, you could say that the same applies to PyLucene, of course :-)
>
> :-)
>
>> I'm not exactly sure what kind of backwards compat promises Lucene
>> Java made going from 3.0 to 3.1 but the new QueryParser method
>> overloads and the fact that there is no support for method overloads
>> in Python make PythonQueryParser a bit stuck between a rock and a hard
>> place. If you see a better way to fix the mess with the _quoted and
>> _slop variants for getFieldQuery, a patch is welcome.
>
> Sure.
>
> Bill
>
Re: [VOTE] Release PyLucene 3.1.0
Posted by Bill Janssen <ja...@parc.com>.
Andi Vajda <va...@apache.org> wrote:
> Unless I'm missing something here, you've got two options before you
> break your users:
> 1. fix your code before you ship it to them
Unfortunately, the code is out there for building, and the instructions,
also already out there, say, "PyLucene 2.4 to 3.X". I should be more
careful :-).
> 2. don't upgrade
It's the users that upgrade, not me.
> Yes, you could say that the same applies to PyLucene, of course :-)
:-)
> I'm not exactly sure what kind of backwards compat promises Lucene
> Java made going from 3.0 to 3.1 but the new QueryParser method
> overloads and the fact that there is no support for method overloads
> in Python make PythonQueryParser a bit stuck between a rock and a hard
> place. If you see a better way to fix the mess with the _quoted and
> _slop variants for getFieldQuery, a patch is welcome.
Sure.
Bill
Re: [VOTE] Release PyLucene 3.1.0
Posted by Andi Vajda <va...@apache.org>.
On Wed, 6 Apr 2011, Bill Janssen wrote:
> Andi Vajda <va...@apache.org> wrote:
>
>>
>> Hi Bill,
>>
>> The QueryParser class changed a bit. More overloads were introduced on
>> the Lucene side. You probably have a Python 'subclass' of QueryParser
>> that needs a bit of work to adapt to the changes.
>
> Thanks, but... All that adds up to breakage for my users.
Unless I'm missing something here, you've got two options before you break
your users:
1. fix your code before you ship it to them
2. don't upgrade
Yes, you could say that the same applies to PyLucene, of course :-)
I'm not exactly sure what kind of backwards compat promises Lucene Java made
going from 3.0 to 3.1 but the new QueryParser method overloads and the fact
that there is no support for method overloads in Python make
PythonQueryParser a bit stuck between a rock and a hard place. If you see a
better way to fix the mess with the _quoted and _slop variants for
getFieldQuery, a patch is welcome.
Andi..
Re: [VOTE] Release PyLucene 3.1.0
Posted by Bill Janssen <ja...@parc.com>.
Andi Vajda <va...@apache.org> wrote:
>
> Hi Bill,
>
> The QueryParser class changed a bit. More overloads were introduced on
> the Lucene side. You probably have a Python 'subclass' of QueryParser
> that needs a bit of work to adapt to the changes.
Thanks, but... All that adds up to breakage for my users.
Bill
Re: [VOTE] Release PyLucene 3.1.0
Posted by Bill Janssen <ja...@parc.com>.
Andi Vajda <va...@apache.org> wrote:
> Look at the new version in
> apache/pylucene-3.1/java/org/apache/pylucene/queryParser/PythonQueryParser.java
> and see the native methods that you're missing on your Python
Wow, looks like a lot. My implementations just have implementations of
getFieldQuery() and getRangeQuery().
> implementation. Also take a look at test/test_PythonQueryParser.py for
> an example on what the new methods look like (hint:
> getFieldQuery_quoted()).
Looking at that, it seems that one needn't provide implementations for
most of the native methods -- your example classes don't. How should one
know which to implement? The ones that could get called, I suppose.
Bill
>
> With a default QueryParser instance, your query parses just fine:
>
> >>> from lucene import *
> >>> initVM()
> <jcc.JCCEnv object at 0x10029d0f0>
> >>> qp = QueryParser(Version.LUCENE_CURRENT, "foo", StandardAnalyzer(Version.LUCENE_CURRENT))
> >>> qp.parse("categories:RSSReader AND id:[00000-00-0000-000 TO 01299-51-3142-795] AND NOT categories:RSSReader/_noexpire_")
> <Query: +categories:rssreader +id:[00000-00-0000-000 TO 01299-51-3142-795] -(categories:rssreader categories:_noexpire_)>
>
> Andi..
>
> On Wed, 6 Apr 2011, Bill Janssen wrote:
>
> > I'm seeing parse failures on this query string:
> >
> > "categories:RSSReader AND id:[00000-00-0000-000 TO 01299-51-3142-795] AND NOT categories:RSSReader/_noexpire_"
> >
> > thr002: RSSReader: Traceback (most recent call last):
> > thr002: File "/local/lib/UpLib-1.7.11/site-extensions/RSSReader.py", line 271, in _scan_rss_sites
> > thr002: hits = repo.do_query("categories:RSSReader AND id:[00000-00-0000-000 TO %s] AND NOT categories:RSSReader/_noexpire_" % old_id)
> > thr002: File "/local/share/UpLib-1.7.11/code/uplib/repository.py", line 1172, in do_query
> > thr002: results = self.do_full_query(query_string, searchtype)
> > thr002: File "/local/share/UpLib-1.7.11/code/uplib/repository.py", line 1196, in do_full_query
> > thr002: results = self.pylucene_search(searchtype, query_string)
> > thr002: File "/local/share/UpLib-1.7.11/code/uplib/repository.py", line 1081, in pylucene_search
> > thr002: v = self.__search_context.search(query_string)
> > thr002: File "/local/share/UpLib-1.7.11/code/uplib/indexing.py", line 913, in search
> > thr002: parsed_query = query_parser.parseQ(query)
> > thr002: File "/local/share/UpLib-1.7.11/code/uplib/indexing.py", line 550, in parseQ
> > thr002: query = QueryParser.parse(self, querystring)
> > thr002: JavaError: org.apache.jcc.PythonException: getFieldQuery_quoted
> > thr002: AttributeError: getFieldQuery_quoted
> >
> > thr002: Java stacktrace:
> > thr002: org.apache.jcc.PythonException: getFieldQuery_quoted
> > thr002: AttributeError: getFieldQuery_quoted
> >
> > thr002: at org.apache.pylucene.queryParser.PythonMultiFieldQueryParser.getFieldQuery_quoted(Native Method)
> > thr002: at org.apache.pylucene.queryParser.PythonMultiFieldQueryParser.getFieldQuery(Unknown Source)
> > thr002: at org.apache.lucene.queryParser.QueryParser.Term(QueryParser.java:1421)
> > thr002: at org.apache.lucene.queryParser.QueryParser.Clause(QueryParser.java:1309)
> > thr002: at org.apache.lucene.queryParser.QueryParser.Query(QueryParser.java:1237)
> > thr002: at org.apache.lucene.queryParser.QueryParser.TopLevelQuery(QueryParser.java:1226)
> > thr002: at org.apache.lucene.queryParser.QueryParser.parse(QueryParser.java:206)
> >
> >
> > Bill
> >
repl: bad addresses:
pylucene-dev@lucene.apache.org Andi Vajda <va...@apache.org> -- junk after local@domain (Andi)
Re: [VOTE] Release PyLucene 3.1.0
Posted by Andi Vajda <va...@apache.org>.
Hi Bill,
The QueryParser class changed a bit. More overloads were introduced on the
Lucene side. You probably have a Python 'subclass' of QueryParser that needs
a bit of work to adapt to the changes.
Look at the new version in
apache/pylucene-3.1/java/org/apache/pylucene/queryParser/PythonQueryParser.java
and see the native methods that you're missing on your Python
implementation. Also take a look at test/test_PythonQueryParser.py for an
example on what the new methods look like (hint: getFieldQuery_quoted()).
With a default QueryParser instance, your query parses just fine:
>>> from lucene import *
>>> initVM()
<jcc.JCCEnv object at 0x10029d0f0>
>>> qp = QueryParser(Version.LUCENE_CURRENT, "foo", StandardAnalyzer(Version.LUCENE_CURRENT))
>>> qp.parse("categories:RSSReader AND id:[00000-00-0000-000 TO 01299-51-3142-795] AND NOT categories:RSSReader/_noexpire_")
<Query: +categories:rssreader +id:[00000-00-0000-000 TO 01299-51-3142-795] -(categories:rssreader categories:_noexpire_)>
Andi..
On Wed, 6 Apr 2011, Bill Janssen wrote:
> I'm seeing parse failures on this query string:
>
> "categories:RSSReader AND id:[00000-00-0000-000 TO 01299-51-3142-795] AND NOT categories:RSSReader/_noexpire_"
>
> thr002: RSSReader: Traceback (most recent call last):
> thr002: File "/local/lib/UpLib-1.7.11/site-extensions/RSSReader.py", line 271, in _scan_rss_sites
> thr002: hits = repo.do_query("categories:RSSReader AND id:[00000-00-0000-000 TO %s] AND NOT categories:RSSReader/_noexpire_" % old_id)
> thr002: File "/local/share/UpLib-1.7.11/code/uplib/repository.py", line 1172, in do_query
> thr002: results = self.do_full_query(query_string, searchtype)
> thr002: File "/local/share/UpLib-1.7.11/code/uplib/repository.py", line 1196, in do_full_query
> thr002: results = self.pylucene_search(searchtype, query_string)
> thr002: File "/local/share/UpLib-1.7.11/code/uplib/repository.py", line 1081, in pylucene_search
> thr002: v = self.__search_context.search(query_string)
> thr002: File "/local/share/UpLib-1.7.11/code/uplib/indexing.py", line 913, in search
> thr002: parsed_query = query_parser.parseQ(query)
> thr002: File "/local/share/UpLib-1.7.11/code/uplib/indexing.py", line 550, in parseQ
> thr002: query = QueryParser.parse(self, querystring)
> thr002: JavaError: org.apache.jcc.PythonException: getFieldQuery_quoted
> thr002: AttributeError: getFieldQuery_quoted
>
> thr002: Java stacktrace:
> thr002: org.apache.jcc.PythonException: getFieldQuery_quoted
> thr002: AttributeError: getFieldQuery_quoted
>
> thr002: at org.apache.pylucene.queryParser.PythonMultiFieldQueryParser.getFieldQuery_quoted(Native Method)
> thr002: at org.apache.pylucene.queryParser.PythonMultiFieldQueryParser.getFieldQuery(Unknown Source)
> thr002: at org.apache.lucene.queryParser.QueryParser.Term(QueryParser.java:1421)
> thr002: at org.apache.lucene.queryParser.QueryParser.Clause(QueryParser.java:1309)
> thr002: at org.apache.lucene.queryParser.QueryParser.Query(QueryParser.java:1237)
> thr002: at org.apache.lucene.queryParser.QueryParser.TopLevelQuery(QueryParser.java:1226)
> thr002: at org.apache.lucene.queryParser.QueryParser.parse(QueryParser.java:206)
>
>
> Bill
>
Re: [VOTE] Release PyLucene 3.1.0
Posted by Bill Janssen <ja...@parc.com>.
Bill Janssen <ja...@parc.com> wrote:
> I'm seeing parse failures on this query string:
>
> "categories:RSSReader AND id:[00000-00-0000-000 TO 01299-51-3142-795] AND NOT categories:RSSReader/_noexpire_"
3.0.3 works just fine.
Bill
Re: [VOTE] Release PyLucene 3.1.0
Posted by Bill Janssen <ja...@parc.com>.
I'm seeing parse failures on this query string:
"categories:RSSReader AND id:[00000-00-0000-000 TO 01299-51-3142-795] AND NOT categories:RSSReader/_noexpire_"
thr002: RSSReader: Traceback (most recent call last):
thr002: File "/local/lib/UpLib-1.7.11/site-extensions/RSSReader.py", line 271, in _scan_rss_sites
thr002: hits = repo.do_query("categories:RSSReader AND id:[00000-00-0000-000 TO %s] AND NOT categories:RSSReader/_noexpire_" % old_id)
thr002: File "/local/share/UpLib-1.7.11/code/uplib/repository.py", line 1172, in do_query
thr002: results = self.do_full_query(query_string, searchtype)
thr002: File "/local/share/UpLib-1.7.11/code/uplib/repository.py", line 1196, in do_full_query
thr002: results = self.pylucene_search(searchtype, query_string)
thr002: File "/local/share/UpLib-1.7.11/code/uplib/repository.py", line 1081, in pylucene_search
thr002: v = self.__search_context.search(query_string)
thr002: File "/local/share/UpLib-1.7.11/code/uplib/indexing.py", line 913, in search
thr002: parsed_query = query_parser.parseQ(query)
thr002: File "/local/share/UpLib-1.7.11/code/uplib/indexing.py", line 550, in parseQ
thr002: query = QueryParser.parse(self, querystring)
thr002: JavaError: org.apache.jcc.PythonException: getFieldQuery_quoted
thr002: AttributeError: getFieldQuery_quoted
thr002: Java stacktrace:
thr002: org.apache.jcc.PythonException: getFieldQuery_quoted
thr002: AttributeError: getFieldQuery_quoted
thr002: at org.apache.pylucene.queryParser.PythonMultiFieldQueryParser.getFieldQuery_quoted(Native Method)
thr002: at org.apache.pylucene.queryParser.PythonMultiFieldQueryParser.getFieldQuery(Unknown Source)
thr002: at org.apache.lucene.queryParser.QueryParser.Term(QueryParser.java:1421)
thr002: at org.apache.lucene.queryParser.QueryParser.Clause(QueryParser.java:1309)
thr002: at org.apache.lucene.queryParser.QueryParser.Query(QueryParser.java:1237)
thr002: at org.apache.lucene.queryParser.QueryParser.TopLevelQuery(QueryParser.java:1226)
thr002: at org.apache.lucene.queryParser.QueryParser.parse(QueryParser.java:206)
Bill
Re: [VOTE] Release PyLucene 3.1.0
Posted by Michael McCandless <lu...@mikemccandless.com>.
+1 to release
I installed on Mac OS X 10.6.6, and ran my usual smoke test (indexing
first 100K docs from Wikipedia, optimizing, running a few queries).
Looks good!
Mike
http://blog.mikemccandless.com
On Sat, Apr 2, 2011 at 4:28 PM, Andi Vajda <va...@apache.org> wrote:
>
> The PyLucene 3.1.0-1 release closely tracking the recent release of Lucene
> Java 3.1.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/pylucene_3_1/CHANGES
>
> PyLucene 3.1.0 is built with JCC 2.8 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_1/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.1.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
>
> pps: here is my +1
>
Re: [VOTE] Release PyLucene 3.2.0
Posted by Andi Vajda <va...@apache.org>.
This vote has now passed.
It got 3 +1 votes from PMC members and no -1.
Expect a release announcement shortly.
Thank you for voting !
Andi..
On Mon, 6 Jun 2011, Andi Vajda wrote:
> The PyLucene 3.2.0-1 release closely tracking the recent release of Lucene
> Java 3.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_2/CHANGES
>
> PyLucene 3.2.0 is built with JCC 2.9 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_2/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.2.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
>
> pps: here is my +1
>
Re: [VOTE] Release PyLucene 3.3.0
Posted by Andi Vajda <va...@apache.org>.
On Sun, 3 Jul 2011, Christian Heimes wrote:
> Am 03.07.2011 18:17, schrieb Andi Vajda:
>> What kind of errors ?
>>
>> So I added the grouping module to the PyLucene branch_3x build and it "just
>> built" (tm). I even committed the change to the build (rev 1142455) but I
>> didn't check that the grouping module was functional in PyLucene as I didn't
>> port any unit tests or even know much about it.
>
> I'm getting an error on my box, too.
I fixed a bug with what looks like strange behaviour of the
java.lang.reflect.Constructor class: for a non-static inner class, it
appears that Constructor.getGenericParameterTypes() is not returning the
implicit first parameter - the instance of the declaring outer class - that
Constructor.getParameterTypes() is returning.
This difference is not documented (nor is the implicit first parameter
returned by the non-generic version).
Could you please get the latest jcc from trunk/branch_3x (version 2.10) and
verify that my fix really fixes it. I was able to reproduce and explain the
bug but would like to be sure I'm not missing something.
I re-enabled the grouping module on branch_3x.
Once verified, I'll spin a new PyLucene 3.3 release candidate as the
previous didn't garner the 3 required PMC votes anyway.
Thanks !
Andi..
>
> In file included from build/_lucene/__wrap01__.cpp:39469:0:
> build/_lucene/org/apache/lucene/search/grouping/AbstractSecondPassGroupingCollector$SearchGroupDocs.h:55:83:
> error: ?AbstractSecondPassGroupingCollector? in namespace
> ?org::apache::lucene::search::grouping? does not name a type
> build/_lucene/org/apache/lucene/search/grouping/AbstractSecondPassGroupingCollector$SearchGroupDocs.h:55:160:
> error: ISO C++ forbids declaration of ?parameter? with no type
> build/_lucene/__wrap01__.cpp:39503:132: error:
> ?AbstractSecondPassGroupingCollector? in namespace
> ?org::apache::lucene::search::grouping? does not name a type
> build/_lucene/__wrap01__.cpp:39503:211: error: ISO C++ forbids
> declaration of ?a0? with no type
> build/_lucene/__wrap01__.cpp: In constructor
> ?org::apache::lucene::search::grouping::AbstractSecondPassGroupingCollector$SearchGroupDocs::AbstractSecondPassGroupingCollector$SearchGroupDocs(const
> int&, const java::lang::Object&, const
> org::apache::lucene::search::TopDocsCollector&)?:
> build/_lucene/__wrap01__.cpp:39503:394: error: request for member
> ?this$? in ?a0?, which is of non-class type ?const int?
> build/_lucene/__wrap01__.cpp: In function ?int
> org::apache::lucene::search::grouping::t_AbstractSecondPassGroupingCollector$SearchGroupDocs_init_(org::apache::lucene::search::grouping::t_AbstractSecondPassGroupingCollector$SearchGroupDocs*,
> PyObject*, PyObject*)?:
> build/_lucene/__wrap01__.cpp:39608:25: error:
> ?AbstractSecondPassGroupingCollector? is not a member of
> ?org::apache::lucene::search::grouping?
> build/_lucene/__wrap01__.cpp:39608:102: error: expected ?;? before ?a0?
> build/_lucene/__wrap01__.cpp:39615:30: error:
> ?org::apache::lucene::search::grouping::AbstractSecondPassGroupingCollector?
> has not been declared
> build/_lucene/__wrap01__.cpp:39615:30: error: ?a0? was not declared in
> this scope
> build/_lucene/__wrap01__.cpp:39615:30: error:
> ?org::apache::lucene::search::grouping::t_AbstractSecondPassGroupingCollector?
> has not been declared
> error: command 'gcc' failed with exit status 1
>
> Ubuntu 11.04 x86_64
> GCC 4.5.2
> Python 2.7.2
>
> Christian
>
Re: [VOTE] Release PyLucene 3.3.0
Posted by Michael McCandless <lu...@mikemccandless.com>.
I agree this is not a release blocker -- +1 to release PyLucene 3.3.0-1.
Mike McCandless
http://blog.mikemccandless.com
On Sun, Jul 3, 2011 at 1:20 PM, Andi Vajda <va...@apache.org> wrote:
>
> On Sun, 3 Jul 2011, Christian Heimes wrote:
>
>> Am 03.07.2011 18:17, schrieb Andi Vajda:
>>>
>>> What kind of errors ?
>>>
>>> So I added the grouping module to the PyLucene branch_3x build and it
>>> "just
>>> built" (tm). I even committed the change to the build (rev 1142455) but I
>>> didn't check that the grouping module was functional in PyLucene as I
>>> didn't
>>> port any unit tests or even know much about it.
>>
>> I'm getting an error on my box, too.
>
> While I don't see the error, I see that there could be something missing in
> that header file, AbstractSecondPassGroupingCollector$SearchGroupDocs.h.
> For example, TopDocsCollector is forward-declared there but
> AbstractSecondPassGroupingCollector is not, even though it is used. What's
> special about it is that it's the outer class of the class being defined
> here, AbstractSecondPassGroupingCollector$SearchGroupDocs.
>
> The reason I'm not seeing there error could be a difference in file
> inclusion order somewhere getting this missing class definition included
> from somewhere else.
>
> I'm about to go on vacation for two weeks, without a computer (ok, email
> only) and I should investigate this upon my return.
>
> Still, that shouldn't necessarily block the PyLucene 3.3 release.
> I'm fine with either solution, block the release on this or fix that for
> 3.4. Either way, I can't finish the release process until I return as the
> vote has to run for three business days, ie, until Tuesday.
>
> I'll leave it up to the voters to decide :-)
>
> Andi..
>
>>
>> In file included from build/_lucene/__wrap01__.cpp:39469:0:
>>
>> build/_lucene/org/apache/lucene/search/grouping/AbstractSecondPassGroupingCollector$SearchGroupDocs.h:55:83:
>> error: ?AbstractSecondPassGroupingCollector? in namespace
>> ?org::apache::lucene::search::grouping? does not name a type
>>
>> build/_lucene/org/apache/lucene/search/grouping/AbstractSecondPassGroupingCollector$SearchGroupDocs.h:55:160:
>> error: ISO C++ forbids declaration of ?parameter? with no type
>> build/_lucene/__wrap01__.cpp:39503:132: error:
>> ?AbstractSecondPassGroupingCollector? in namespace
>> ?org::apache::lucene::search::grouping? does not name a type
>> build/_lucene/__wrap01__.cpp:39503:211: error: ISO C++ forbids
>> declaration of ?a0? with no type
>> build/_lucene/__wrap01__.cpp: In constructor
>>
>> ?org::apache::lucene::search::grouping::AbstractSecondPassGroupingCollector$SearchGroupDocs::AbstractSecondPassGroupingCollector$SearchGroupDocs(const
>> int&, const java::lang::Object&, const
>> org::apache::lucene::search::TopDocsCollector&)?:
>> build/_lucene/__wrap01__.cpp:39503:394: error: request for member
>> ?this$? in ?a0?, which is of non-class type ?const int?
>> build/_lucene/__wrap01__.cpp: In function ?int
>>
>> org::apache::lucene::search::grouping::t_AbstractSecondPassGroupingCollector$SearchGroupDocs_init_(org::apache::lucene::search::grouping::t_AbstractSecondPassGroupingCollector$SearchGroupDocs*,
>> PyObject*, PyObject*)?:
>> build/_lucene/__wrap01__.cpp:39608:25: error:
>> ?AbstractSecondPassGroupingCollector? is not a member of
>> ?org::apache::lucene::search::grouping?
>> build/_lucene/__wrap01__.cpp:39608:102: error: expected ?;? before ?a0?
>> build/_lucene/__wrap01__.cpp:39615:30: error:
>>
>> ?org::apache::lucene::search::grouping::AbstractSecondPassGroupingCollector?
>> has not been declared
>> build/_lucene/__wrap01__.cpp:39615:30: error: ?a0? was not declared in
>> this scope
>> build/_lucene/__wrap01__.cpp:39615:30: error:
>>
>> ?org::apache::lucene::search::grouping::t_AbstractSecondPassGroupingCollector?
>> has not been declared
>> error: command 'gcc' failed with exit status 1
>>
>> Ubuntu 11.04 x86_64
>> GCC 4.5.2
>> Python 2.7.2
>>
>> Christian
>>
>
Re: [VOTE] Release PyLucene 3.3.0
Posted by Andi Vajda <va...@apache.org>.
On Sun, 3 Jul 2011, Christian Heimes wrote:
> Am 03.07.2011 18:17, schrieb Andi Vajda:
>> What kind of errors ?
>>
>> So I added the grouping module to the PyLucene branch_3x build and it "just
>> built" (tm). I even committed the change to the build (rev 1142455) but I
>> didn't check that the grouping module was functional in PyLucene as I didn't
>> port any unit tests or even know much about it.
>
> I'm getting an error on my box, too.
While I don't see the error, I see that there could be something missing in
that header file, AbstractSecondPassGroupingCollector$SearchGroupDocs.h.
For example, TopDocsCollector is forward-declared there but
AbstractSecondPassGroupingCollector is not, even though it is used. What's
special about it is that it's the outer class of the class being defined
here, AbstractSecondPassGroupingCollector$SearchGroupDocs.
The reason I'm not seeing there error could be a difference in file
inclusion order somewhere getting this missing class definition included
from somewhere else.
I'm about to go on vacation for two weeks, without a computer (ok, email
only) and I should investigate this upon my return.
Still, that shouldn't necessarily block the PyLucene 3.3 release.
I'm fine with either solution, block the release on this or fix that for
3.4. Either way, I can't finish the release process until I return as the
vote has to run for three business days, ie, until Tuesday.
I'll leave it up to the voters to decide :-)
Andi..
>
> In file included from build/_lucene/__wrap01__.cpp:39469:0:
> build/_lucene/org/apache/lucene/search/grouping/AbstractSecondPassGroupingCollector$SearchGroupDocs.h:55:83:
> error: ?AbstractSecondPassGroupingCollector? in namespace
> ?org::apache::lucene::search::grouping? does not name a type
> build/_lucene/org/apache/lucene/search/grouping/AbstractSecondPassGroupingCollector$SearchGroupDocs.h:55:160:
> error: ISO C++ forbids declaration of ?parameter? with no type
> build/_lucene/__wrap01__.cpp:39503:132: error:
> ?AbstractSecondPassGroupingCollector? in namespace
> ?org::apache::lucene::search::grouping? does not name a type
> build/_lucene/__wrap01__.cpp:39503:211: error: ISO C++ forbids
> declaration of ?a0? with no type
> build/_lucene/__wrap01__.cpp: In constructor
> ?org::apache::lucene::search::grouping::AbstractSecondPassGroupingCollector$SearchGroupDocs::AbstractSecondPassGroupingCollector$SearchGroupDocs(const
> int&, const java::lang::Object&, const
> org::apache::lucene::search::TopDocsCollector&)?:
> build/_lucene/__wrap01__.cpp:39503:394: error: request for member
> ?this$? in ?a0?, which is of non-class type ?const int?
> build/_lucene/__wrap01__.cpp: In function ?int
> org::apache::lucene::search::grouping::t_AbstractSecondPassGroupingCollector$SearchGroupDocs_init_(org::apache::lucene::search::grouping::t_AbstractSecondPassGroupingCollector$SearchGroupDocs*,
> PyObject*, PyObject*)?:
> build/_lucene/__wrap01__.cpp:39608:25: error:
> ?AbstractSecondPassGroupingCollector? is not a member of
> ?org::apache::lucene::search::grouping?
> build/_lucene/__wrap01__.cpp:39608:102: error: expected ?;? before ?a0?
> build/_lucene/__wrap01__.cpp:39615:30: error:
> ?org::apache::lucene::search::grouping::AbstractSecondPassGroupingCollector?
> has not been declared
> build/_lucene/__wrap01__.cpp:39615:30: error: ?a0? was not declared in
> this scope
> build/_lucene/__wrap01__.cpp:39615:30: error:
> ?org::apache::lucene::search::grouping::t_AbstractSecondPassGroupingCollector?
> has not been declared
> error: command 'gcc' failed with exit status 1
>
> Ubuntu 11.04 x86_64
> GCC 4.5.2
> Python 2.7.2
>
> Christian
>
Re: [VOTE] Release PyLucene 3.3.0
Posted by Christian Heimes <li...@cheimes.de>.
Am 03.07.2011 18:17, schrieb Andi Vajda:
> What kind of errors ?
>
> So I added the grouping module to the PyLucene branch_3x build and it "just
> built" (tm). I even committed the change to the build (rev 1142455) but I
> didn't check that the grouping module was functional in PyLucene as I didn't
> port any unit tests or even know much about it.
I'm getting an error on my box, too.
In file included from build/_lucene/__wrap01__.cpp:39469:0:
build/_lucene/org/apache/lucene/search/grouping/AbstractSecondPassGroupingCollector$SearchGroupDocs.h:55:83:
error: ‘AbstractSecondPassGroupingCollector’ in namespace
‘org::apache::lucene::search::grouping’ does not name a type
build/_lucene/org/apache/lucene/search/grouping/AbstractSecondPassGroupingCollector$SearchGroupDocs.h:55:160:
error: ISO C++ forbids declaration of ‘parameter’ with no type
build/_lucene/__wrap01__.cpp:39503:132: error:
‘AbstractSecondPassGroupingCollector’ in namespace
‘org::apache::lucene::search::grouping’ does not name a type
build/_lucene/__wrap01__.cpp:39503:211: error: ISO C++ forbids
declaration of ‘a0’ with no type
build/_lucene/__wrap01__.cpp: In constructor
‘org::apache::lucene::search::grouping::AbstractSecondPassGroupingCollector$SearchGroupDocs::AbstractSecondPassGroupingCollector$SearchGroupDocs(const
int&, const java::lang::Object&, const
org::apache::lucene::search::TopDocsCollector&)’:
build/_lucene/__wrap01__.cpp:39503:394: error: request for member
‘this$’ in ‘a0’, which is of non-class type ‘const int’
build/_lucene/__wrap01__.cpp: In function ‘int
org::apache::lucene::search::grouping::t_AbstractSecondPassGroupingCollector$SearchGroupDocs_init_(org::apache::lucene::search::grouping::t_AbstractSecondPassGroupingCollector$SearchGroupDocs*,
PyObject*, PyObject*)’:
build/_lucene/__wrap01__.cpp:39608:25: error:
‘AbstractSecondPassGroupingCollector’ is not a member of
‘org::apache::lucene::search::grouping’
build/_lucene/__wrap01__.cpp:39608:102: error: expected ‘;’ before ‘a0’
build/_lucene/__wrap01__.cpp:39615:30: error:
‘org::apache::lucene::search::grouping::AbstractSecondPassGroupingCollector’
has not been declared
build/_lucene/__wrap01__.cpp:39615:30: error: ‘a0’ was not declared in
this scope
build/_lucene/__wrap01__.cpp:39615:30: error:
‘org::apache::lucene::search::grouping::t_AbstractSecondPassGroupingCollector’
has not been declared
error: command 'gcc' failed with exit status 1
Ubuntu 11.04 x86_64
GCC 4.5.2
Python 2.7.2
Christian
Re: [VOTE] Release PyLucene 3.3.0
Posted by Michael McCandless <lu...@mikemccandless.com>.
Sorry, I should have included my errors 1st time around:
In file included from build/_lucene/__wrap03__.cpp:514:
build/_lucene/org/apache/lucene/search/grouping/AbstractSecondPassGroupingCollector$SearchGroupDocs.h:55:
error: expected unqualified-id before '&' token
build/_lucene/org/apache/lucene/search/grouping/AbstractSecondPassGroupingCollector$SearchGroupDocs.h:55:
error: expected ',' or '...' before '&' token
build/_lucene/__wrap03__.cpp:548: error: expected unqualified-id
before '&' token
build/_lucene/__wrap03__.cpp:548: error: expected ',' or '...' before '&' token
build/_lucene/__wrap03__.cpp: In constructor
'org::apache::lucene::search::grouping::AbstractSecondPassGroupingCollector$SearchGroupDocs::AbstractSecondPassGroupingCollector$SearchGroupDocs()':
build/_lucene/__wrap03__.cpp:548: error: 'a0' was not declared in this scope
build/_lucene/__wrap03__.cpp:548: error: 'a1' was not declared in this scope
build/_lucene/__wrap03__.cpp:548: error: 'a2' was not declared in this scope
build/_lucene/__wrap03__.cpp: In function 'int
org::apache::lucene::search::grouping::t_AbstractSecondPassGroupingCollector$SearchGroupDocs_init_(org::apache::lucene::search::grouping::t_AbstractSecondPassGroupingCollector$SearchGroupDocs*,
PyObject*, PyObject*)':
build/_lucene/__wrap03__.cpp:653: error:
'AbstractSecondPassGroupingCollector' is not a member of
'org::apache::lucene::search::grouping'
build/_lucene/__wrap03__.cpp:653: error: expected `;' before 'a0'
build/_lucene/__wrap03__.cpp:660: error:
'org::apache::lucene::search::grouping::AbstractSecondPassGroupingCollector'
has not been declared
build/_lucene/__wrap03__.cpp:660: error: 'a0' was not declared in this scope
build/_lucene/__wrap03__.cpp:660: error:
'org::apache::lucene::search::grouping::t_AbstractSecondPassGroupingCollector'
has not been declared
error: command 'gcc-4.2' failed with exit status 1
make: *** [compile] Error 1
My env is OS X 10.6.6, Apple's build of Python (2.6.1), Java 1.6.0_22.
Mike McCandless
http://blog.mikemccandless.com
On Sun, Jul 3, 2011 at 12:17 PM, Andi Vajda <va...@apache.org> wrote:
>
> Hi Mike,
>
> On Sun, 3 Jul 2011, Michael McCandless wrote:
>
>> Re-send, this time to pylucene-dev:
>>
>> Everything looks good -- I was able to compile, run all tests
>> successfully, and run my usual smoke test (indexing & optimizing &
>> searching on first 100K wikipedia docs), but...
>>
>> I then tried to enable the grouping module (lucene/contrib/grouping),
>> by adding a GROUPING_JAR matching all the other contrib jars, and
>> running "make". This then hit various compilation errors -- is anyone
>> able to enable the grouping module and compile successfully?
>
> What kind of errors ?
>
> So I added the grouping module to the PyLucene branch_3x build and it "just
> built" (tm). I even committed the change to the build (rev 1142455) but I
> didn't check that the grouping module was functional in PyLucene as I didn't
> port any unit tests or even know much about it.
>
> Andi..
>
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>> On Sun, Jul 3, 2011 at 10:14 AM, Michael McCandless
>> <lu...@mikemccandless.com> wrote:
>>>
>>> Everything looks good -- I was able to compile, run all tests
>>> successfully, and run my usual smoke test (indexing & optimizing &
>>> searching on first 100K wikipedia docs), but...
>>>
>>> I then tried to enable the grouping module (lucene/contrib/grouping),
>>> by adding a GROUPING_JAR matching all the other contrib jars, and
>>> running "make". This then hit various compilation errors -- is anyone
>>> able to enable the grouping module and compile successfully?
>>>
>>> Mike McCandless
>>>
>>> http://blog.mikemccandless.com
>>>
>>> On Fri, Jul 1, 2011 at 8:24 AM, Andi Vajda <va...@apache.org> wrote:
>>>>
>>>> The PyLucene 3.3.0-1 release closely tracking the recent release of
>>>> Lucene
>>>> Java 3.3 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_3/CHANGES
>>>>
>>>> PyLucene 3.3.0 is built with JCC 2.9 included in these release
>>>> artifacts.
>>>>
>>>> A list of Lucene Java changes can be seen at:
>>>>
>>>> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
>>>>
>>>> Please vote to release these artifacts as PyLucene 3.3.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
>>>>
>>>> pps: here is my +1
>>>>
>>>
>
Re: [VOTE] Release PyLucene 3.3.0
Posted by Andi Vajda <va...@apache.org>.
Hi Mike,
On Sun, 3 Jul 2011, Michael McCandless wrote:
> Re-send, this time to pylucene-dev:
>
> Everything looks good -- I was able to compile, run all tests
> successfully, and run my usual smoke test (indexing & optimizing &
> searching on first 100K wikipedia docs), but...
>
> I then tried to enable the grouping module (lucene/contrib/grouping),
> by adding a GROUPING_JAR matching all the other contrib jars, and
> running "make". This then hit various compilation errors -- is anyone
> able to enable the grouping module and compile successfully?
What kind of errors ?
So I added the grouping module to the PyLucene branch_3x build and it "just
built" (tm). I even committed the change to the build (rev 1142455) but I
didn't check that the grouping module was functional in PyLucene as I didn't
port any unit tests or even know much about it.
Andi..
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Sun, Jul 3, 2011 at 10:14 AM, Michael McCandless
> <lu...@mikemccandless.com> wrote:
>> Everything looks good -- I was able to compile, run all tests
>> successfully, and run my usual smoke test (indexing & optimizing &
>> searching on first 100K wikipedia docs), but...
>>
>> I then tried to enable the grouping module (lucene/contrib/grouping),
>> by adding a GROUPING_JAR matching all the other contrib jars, and
>> running "make". This then hit various compilation errors -- is anyone
>> able to enable the grouping module and compile successfully?
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>> On Fri, Jul 1, 2011 at 8:24 AM, Andi Vajda <va...@apache.org> wrote:
>>>
>>> The PyLucene 3.3.0-1 release closely tracking the recent release of Lucene
>>> Java 3.3 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_3/CHANGES
>>>
>>> PyLucene 3.3.0 is built with JCC 2.9 included in these release artifacts.
>>>
>>> A list of Lucene Java changes can be seen at:
>>> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
>>>
>>> Please vote to release these artifacts as PyLucene 3.3.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
>>>
>>> pps: here is my +1
>>>
>>
>
Re: [VOTE] Release PyLucene 3.3.0
Posted by Michael McCandless <lu...@mikemccandless.com>.
Re-send, this time to pylucene-dev:
Everything looks good -- I was able to compile, run all tests
successfully, and run my usual smoke test (indexing & optimizing &
searching on first 100K wikipedia docs), but...
I then tried to enable the grouping module (lucene/contrib/grouping),
by adding a GROUPING_JAR matching all the other contrib jars, and
running "make". This then hit various compilation errors -- is anyone
able to enable the grouping module and compile successfully?
Mike McCandless
http://blog.mikemccandless.com
On Sun, Jul 3, 2011 at 10:14 AM, Michael McCandless
<lu...@mikemccandless.com> wrote:
> Everything looks good -- I was able to compile, run all tests
> successfully, and run my usual smoke test (indexing & optimizing &
> searching on first 100K wikipedia docs), but...
>
> I then tried to enable the grouping module (lucene/contrib/grouping),
> by adding a GROUPING_JAR matching all the other contrib jars, and
> running "make". This then hit various compilation errors -- is anyone
> able to enable the grouping module and compile successfully?
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Fri, Jul 1, 2011 at 8:24 AM, Andi Vajda <va...@apache.org> wrote:
>>
>> The PyLucene 3.3.0-1 release closely tracking the recent release of Lucene
>> Java 3.3 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_3/CHANGES
>>
>> PyLucene 3.3.0 is built with JCC 2.9 included in these release artifacts.
>>
>> A list of Lucene Java changes can be seen at:
>> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
>>
>> Please vote to release these artifacts as PyLucene 3.3.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
>>
>> pps: here is my +1
>>
>
Re: [VOTE] Release PyLucene 3.3.0
Posted by Michael McCandless <lu...@mikemccandless.com>.
Everything looks good -- I was able to compile, run all tests
successfully, and run my usual smoke test (indexing & optimizing &
searching on first 100K wikipedia docs), but...
I then tried to enable the grouping module (lucene/contrib/grouping),
by adding a GROUPING_JAR matching all the other contrib jars, and
running "make". This then hit various compilation errors -- is anyone
able to enable the grouping module and compile successfully?
Mike McCandless
http://blog.mikemccandless.com
On Fri, Jul 1, 2011 at 8:24 AM, Andi Vajda <va...@apache.org> wrote:
>
> The PyLucene 3.3.0-1 release closely tracking the recent release of Lucene
> Java 3.3 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_3/CHANGES
>
> PyLucene 3.3.0 is built with JCC 2.9 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.3.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
>
> pps: here is my +1
>
Re: [VOTE] Release PyLucene 3.3 (rc3)
Posted by Michael McCandless <lu...@mikemccandless.com>.
+1 to release!
Smoke test passed and I see grouping module classes are visible by
default! Thanks Andi :)
Mike McCandless
http://blog.mikemccandless.com
On Thu, Jul 21, 2011 at 12:47 PM, Andi Vajda <va...@apache.org> wrote:
>
> A problem was found with rc2. Please, vote on rc3, thanks :-)
>
> The Apache PyLucene 3.3-3 release closely tracking the recent release of
> Apache Lucene Java 3.3 is ready.
>
> A release candidate is available from:
> http://people.apache.org/~vajda/staging_area/
>
> This new release candidate fixes an issue with wrapping the new grouping
> contrib module which is now part of the PyLucene build.
>
> A list of changes in this release can be seen at:
> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_3/CHANGES
>
> PyLucene 3.3 is built with JCC 2.10 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.3-3.
>
> 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.3 (rc3)
Posted by Christian Heimes <li...@cheimes.de>.
Am 21.07.2011 18:47, schrieb Andi Vajda:
> Please vote to release these artifacts as PyLucene 3.3-3.
+1 from me
I've tested PyLucene on Linux (Ubuntu 10.04 as well as 11.04 on X86_64)
with Python 2.6 and 2.7. My bobobrowse integration and the unit test
suite of our applications are working, too. The grouping module is
available, too. :)
Christian
Re: [VOTE] Release PyLucene 3.3 (rc3)
Posted by Robert Muir <rc...@gmail.com>.
+1, built RC3 and all tests passed here on linux.
On Thu, Jul 21, 2011 at 12:47 PM, Andi Vajda <va...@apache.org> wrote:
>
> A problem was found with rc2. Please, vote on rc3, thanks :-)
>
> The Apache PyLucene 3.3-3 release closely tracking the recent release of
> Apache Lucene Java 3.3 is ready.
>
> A release candidate is available from:
> http://people.apache.org/~vajda/staging_area/
>
> This new release candidate fixes an issue with wrapping the new grouping
> contrib module which is now part of the PyLucene build.
>
> A list of changes in this release can be seen at:
> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_3/CHANGES
>
> PyLucene 3.3 is built with JCC 2.10 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.3-3.
>
> 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
>
--
lucidimagination.com
Re: [VOTE] Release PyLucene 3.3 (rc3)
Posted by Michael McCandless <lu...@mikemccandless.com>.
+1 to release!
Smoke test passed and I see grouping module classes are visible by
default! Thanks Andi :)
Mike McCandless
http://blog.mikemccandless.com
On Thu, Jul 21, 2011 at 12:47 PM, Andi Vajda <va...@apache.org> wrote:
>
> A problem was found with rc2. Please, vote on rc3, thanks :-)
>
> The Apache PyLucene 3.3-3 release closely tracking the recent release of
> Apache Lucene Java 3.3 is ready.
>
> A release candidate is available from:
> http://people.apache.org/~vajda/staging_area/
>
> This new release candidate fixes an issue with wrapping the new grouping
> contrib module which is now part of the PyLucene build.
>
> A list of changes in this release can be seen at:
> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_3/CHANGES
>
> PyLucene 3.3 is built with JCC 2.10 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.3-3.
>
> 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
>
[VOTE] Release PyLucene 3.3 (rc3)
Posted by Andi Vajda <va...@apache.org>.
A problem was found with rc2. Please, vote on rc3, thanks :-)
The Apache PyLucene 3.3-3 release closely tracking the recent release of
Apache Lucene Java 3.3 is ready.
A release candidate is available from:
http://people.apache.org/~vajda/staging_area/
This new release candidate fixes an issue with wrapping the new grouping
contrib module which is now part of the PyLucene build.
A list of changes in this release can be seen at:
http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_3/CHANGES
PyLucene 3.3 is built with JCC 2.10 included in these release artifacts.
A list of Lucene Java changes can be seen at:
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
Please vote to release these artifacts as PyLucene 3.3-3.
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
[VOTE] Release PyLucene 3.3 (rc3)
Posted by Andi Vajda <va...@apache.org>.
A problem was found with rc2. Please, vote on rc3, thanks :-)
The Apache PyLucene 3.3-3 release closely tracking the recent release of
Apache Lucene Java 3.3 is ready.
A release candidate is available from:
http://people.apache.org/~vajda/staging_area/
This new release candidate fixes an issue with wrapping the new grouping
contrib module which is now part of the PyLucene build.
A list of changes in this release can be seen at:
http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_3/CHANGES
PyLucene 3.3 is built with JCC 2.10 included in these release artifacts.
A list of Lucene Java changes can be seen at:
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
Please vote to release these artifacts as PyLucene 3.3-3.
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.3 (rc2)
Posted by Christian Heimes <li...@cheimes.de>.
Am 21.07.2011 12:47, schrieb Andi Vajda:
>
> The Apache PyLucene 3.3-2 release closely tracking the recent release of
> Apache Lucene Java 3.3 is ready.
>
> A release candidate is available from:
> http://people.apache.org/~vajda/staging_area/
>
> This new release candidate fixes an issue with wrapping the new grouping
> contrib module which is now part of the PyLucene build.
>
> A list of changes in this release can be seen at:
> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_3/CHANGES
>
> PyLucene 3.3 is built with JCC 2.10 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.3-2.
The new RC compiles fine with grouping.jar. The tests are passing, too.
(Ubuntu 10.04, X86_64)
+1
Christian
Re: [VOTE] Release PyLucene 3.3 (rc2)
Posted by Andi Vajda <va...@apache.org>.
On Thu, 21 Jul 2011, Michael McCandless wrote:
> +1 to release.
>
> I ran my usual smoke test (index first 100K wikipedia docs and run a
> few searches).
>
> The grouping module isn't actually enabled right? I see this:
>
> JARS+=$(GROUPING_JAR) # grouping module
>
> But then GROUPING_JAR isn't defined anywhere, I think? I went and
> defined it (just copied how SPATIAL_JAR was set up), and was then able
> to compile it just fine this time around.
Ouch, there goes that release candidate. My bad, I had a merging snafu.
Still, I tested the grouping build on the 3.x branch.
Producing rc3 in a bit...
My apologies and thanks for finding this !
Andi..
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Thu, Jul 21, 2011 at 10:50 AM, Thomas Koch <ko...@orbiteam.de> wrote:
>> Hi,
>> I've just tried to build PyLucene 3.3 on win32 and failed.
>> This may be unrelated to V3.3 though as I tried the build process with minGW
>> for the first time (used MSVC before)! Just wondering if I'm doing sth wrong
>> or anyone had this issue and can help:
>>
>> Using
>> - Python 2.6.6 (r266:84297, Aug 24 2010, 18:46:32) [MSC v.1500 32 bit
>> (Intel)] on win32
>> - jdk1.6.0_14
>> - mingw32-gcc (gcc (GCC) 4.5.2)
>> - setuptools.__version__'0.6c11'
>> - msys-make (GNU Make 3.81)
>> - ant 1.7.1
>>
>> I'm able to build (and install) JCC:
>> ./jcc-2.10-py2.6-win32.egg
>>>>> jcc.initVM()
>> <jcc.JCCEnv object at 0x01BAF0B0>
>>
>> Then "make" runs fine until the final "python -m jcc.__main__ xyz.jar ...
>> --build"
>> Here python.exe crashes (windows popup asking to send details to
>> somewhere...)
>> make: *** [compile] Error 5
>>
>> The only warnings I get are
>>
>> which: icupkg: unknown command
>> ICU not installed
>> (is there a minGW package for that?)
>>
>> This is Windows-Vista 32-bit. Attached is my Makefile chunk.
>>
>> Any ideas? Has anyone yet tried to build PyLucene within
>> virtualenv(ironment) and is this suggested?
>>
>> I fear the answer is "you have to build Python with MinGW" ,-(
>>
>> I may get back to MSVC but would also like to get this running with MinGW...
>>
>> Regards
>> Thomas
>> --
>> # Makefile [...]
>> # Windows (Win32, msys/MinGW, Python 2.6.6, Java 1.6, ant 1.7.1
>> PREFIX_PYTHON=C:\\Devel\\Python26
>> ANT=C:\\Devel\\Eclipse\\eclipse36\\plugins\\org.apache.ant_1.7.1.v20100518-1
>> 145\\bin\\ant
>> PYTHON=$(PREFIX_PYTHON)\\python.exe
>> JCC=$(PYTHON) -m jcc.__main__ --shared --compiler mingw32
>> NUM_FILES=3
>>
>>
>> Imports work to some extend ... here's make output with -v -d args for
>> python:
>> ...
>> import jcc # directory
>> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc
>> #
>> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\__init__.py
>> c
>> matches
>> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\__init__.py
>> import jcc # precompiled from
>> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\__init__.py
>> c
>> #
>> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\config.pyc
>> matches
>> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\config.py
>> import jcc.config # precompiled from
>> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\config.pyc
>> import jcc._jcc # dynamically loaded from
>> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\_jcc.pyd
>> # c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\cpp.pyc
>> matches
>> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\cpp.py
>> import jcc.cpp # precompiled from
>> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\cpp.pyc
>> # c:\Devel\Python26\lib\zipfile.pyc matches c:\Devel\Python26\lib\zipfile.py
>> import zipfile # precompiled from c:\Devel\Python26\lib\zipfile.pyc
>> # c:\Devel\Python26\lib\struct.pyc matches c:\Devel\Python26\lib\struct.py
>> import struct # precompiled from c:\Devel\Python26\lib\struct.pyc
>> import _struct # builtin
>> import time # builtin
>> # c:\Devel\Python26\lib\shutil.pyc matches c:\Devel\Python26\lib\shutil.py
>> import shutil # precompiled from c:\Devel\Python26\lib\shutil.pyc
>> # c:\Devel\Python26\lib\fnmatch.pyc matches c:\Devel\Python26\lib\fnmatch.py
>> import fnmatch # precompiled from c:\Devel\Python26\lib\fnmatch.pyc
>> import binascii # builtin
>> import cStringIO # builtin
>> import zlib # builtin
>> #
>> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\python.pyc
>> matches
>> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\python.py
>> import jcc.python # precompiled from
>> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\python.pyc
>> # c:\Devel\Python26\lib\platform.pyc matches
>> c:\Devel\Python26\lib\platform.py
>> import platform # precompiled from c:\Devel\Python26\lib\platform.pyc
>> # c:\Devel\Python26\lib\string.pyc matches c:\Devel\Python26\lib\string.py
>> import string # precompiled from c:\Devel\Python26\lib\string.pyc
>> import strop # builtin
>> import itertools # builtin
>> make: *** [compile] Error 5
>>
>>> -----Original Message-----
>>> From: Andi Vajda [mailto:vajda@apache.org]
>>> Sent: Thursday, July 21, 2011 12:47 PM
>>> To: pylucene-dev@lucene.apache.org
>>> Cc: general@lucene.apache.org
>>> Subject: [VOTE] Release PyLucene 3.3 (rc2)
>>>
>>>
>>> The Apache PyLucene 3.3-2 release closely tracking the recent release of
>>> Apache Lucene Java 3.3 is ready.
>>>
>>> A release candidate is available from:
>>> http://people.apache.org/~vajda/staging_area/
>>>
>>> This new release candidate fixes an issue with wrapping the new grouping
>>> contrib module which is now part of the PyLucene build.
>>>
>>> A list of changes in this release can be seen at:
>>>
>> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_3/CHANGE
>> S
>>>
>>> PyLucene 3.3 is built with JCC 2.10 included in these release artifacts.
>>>
>>> A list of Lucene Java changes can be seen at:
>>>
>> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANG
>> ES
>>> .txt
>>>
>>> Please vote to release these artifacts as PyLucene 3.3-2.
>>>
>>> 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.3 (rc2)
Posted by Michael McCandless <lu...@mikemccandless.com>.
+1 to release.
I ran my usual smoke test (index first 100K wikipedia docs and run a
few searches).
The grouping module isn't actually enabled right? I see this:
JARS+=$(GROUPING_JAR) # grouping module
But then GROUPING_JAR isn't defined anywhere, I think? I went and
defined it (just copied how SPATIAL_JAR was set up), and was then able
to compile it just fine this time around.
Mike McCandless
http://blog.mikemccandless.com
On Thu, Jul 21, 2011 at 10:50 AM, Thomas Koch <ko...@orbiteam.de> wrote:
> Hi,
> I've just tried to build PyLucene 3.3 on win32 and failed.
> This may be unrelated to V3.3 though as I tried the build process with minGW
> for the first time (used MSVC before)! Just wondering if I'm doing sth wrong
> or anyone had this issue and can help:
>
> Using
> - Python 2.6.6 (r266:84297, Aug 24 2010, 18:46:32) [MSC v.1500 32 bit
> (Intel)] on win32
> - jdk1.6.0_14
> - mingw32-gcc (gcc (GCC) 4.5.2)
> - setuptools.__version__'0.6c11'
> - msys-make (GNU Make 3.81)
> - ant 1.7.1
>
> I'm able to build (and install) JCC:
> ./jcc-2.10-py2.6-win32.egg
>>>> jcc.initVM()
> <jcc.JCCEnv object at 0x01BAF0B0>
>
> Then "make" runs fine until the final "python -m jcc.__main__ xyz.jar ...
> --build"
> Here python.exe crashes (windows popup asking to send details to
> somewhere...)
> make: *** [compile] Error 5
>
> The only warnings I get are
>
> which: icupkg: unknown command
> ICU not installed
> (is there a minGW package for that?)
>
> This is Windows-Vista 32-bit. Attached is my Makefile chunk.
>
> Any ideas? Has anyone yet tried to build PyLucene within
> virtualenv(ironment) and is this suggested?
>
> I fear the answer is "you have to build Python with MinGW" ,-(
>
> I may get back to MSVC but would also like to get this running with MinGW...
>
> Regards
> Thomas
> --
> # Makefile [...]
> # Windows (Win32, msys/MinGW, Python 2.6.6, Java 1.6, ant 1.7.1
> PREFIX_PYTHON=C:\\Devel\\Python26
> ANT=C:\\Devel\\Eclipse\\eclipse36\\plugins\\org.apache.ant_1.7.1.v20100518-1
> 145\\bin\\ant
> PYTHON=$(PREFIX_PYTHON)\\python.exe
> JCC=$(PYTHON) -m jcc.__main__ --shared --compiler mingw32
> NUM_FILES=3
>
>
> Imports work to some extend ... here's make output with -v -d args for
> python:
> ...
> import jcc # directory
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc
> #
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\__init__.py
> c
> matches
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\__init__.py
> import jcc # precompiled from
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\__init__.py
> c
> #
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\config.pyc
> matches
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\config.py
> import jcc.config # precompiled from
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\config.pyc
> import jcc._jcc # dynamically loaded from
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\_jcc.pyd
> # c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\cpp.pyc
> matches
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\cpp.py
> import jcc.cpp # precompiled from
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\cpp.pyc
> # c:\Devel\Python26\lib\zipfile.pyc matches c:\Devel\Python26\lib\zipfile.py
> import zipfile # precompiled from c:\Devel\Python26\lib\zipfile.pyc
> # c:\Devel\Python26\lib\struct.pyc matches c:\Devel\Python26\lib\struct.py
> import struct # precompiled from c:\Devel\Python26\lib\struct.pyc
> import _struct # builtin
> import time # builtin
> # c:\Devel\Python26\lib\shutil.pyc matches c:\Devel\Python26\lib\shutil.py
> import shutil # precompiled from c:\Devel\Python26\lib\shutil.pyc
> # c:\Devel\Python26\lib\fnmatch.pyc matches c:\Devel\Python26\lib\fnmatch.py
> import fnmatch # precompiled from c:\Devel\Python26\lib\fnmatch.pyc
> import binascii # builtin
> import cStringIO # builtin
> import zlib # builtin
> #
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\python.pyc
> matches
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\python.py
> import jcc.python # precompiled from
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\python.pyc
> # c:\Devel\Python26\lib\platform.pyc matches
> c:\Devel\Python26\lib\platform.py
> import platform # precompiled from c:\Devel\Python26\lib\platform.pyc
> # c:\Devel\Python26\lib\string.pyc matches c:\Devel\Python26\lib\string.py
> import string # precompiled from c:\Devel\Python26\lib\string.pyc
> import strop # builtin
> import itertools # builtin
> make: *** [compile] Error 5
>
>> -----Original Message-----
>> From: Andi Vajda [mailto:vajda@apache.org]
>> Sent: Thursday, July 21, 2011 12:47 PM
>> To: pylucene-dev@lucene.apache.org
>> Cc: general@lucene.apache.org
>> Subject: [VOTE] Release PyLucene 3.3 (rc2)
>>
>>
>> The Apache PyLucene 3.3-2 release closely tracking the recent release of
>> Apache Lucene Java 3.3 is ready.
>>
>> A release candidate is available from:
>> http://people.apache.org/~vajda/staging_area/
>>
>> This new release candidate fixes an issue with wrapping the new grouping
>> contrib module which is now part of the PyLucene build.
>>
>> A list of changes in this release can be seen at:
>>
> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_3/CHANGE
> S
>>
>> PyLucene 3.3 is built with JCC 2.10 included in these release artifacts.
>>
>> A list of Lucene Java changes can be seen at:
>>
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANG
> ES
>> .txt
>>
>> Please vote to release these artifacts as PyLucene 3.3-2.
>>
>> 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.3 (rc2)
Posted by Thomas Koch <ko...@orbiteam.de>.
Hi Andi,
yes there was a thread on the mailing list about using MinGW on Windows, but
that didn't come to an end.
I've meanwhile managed to build PyLucene-3.3.3 on Win32(vista) with msvc
compiler (Microsoft Visual Studio 9.0 == msvcr90.dll) and Python 2.6.
Did also run "make test" without any errors. So here's my +1 for the RC3
from Windows platform perspective.
Regards,
Thomas
> -----Original Message-----
> From: Andi Vajda [mailto:vajda@apache.org]
> Sent: Thursday, July 21, 2011 5:56 PM
> To: pylucene-dev@lucene.apache.org
> Subject: RE: [VOTE] Release PyLucene 3.3 (rc2)
>
>
> Hi Thomas,
>
> I don't use mingw so I can't tell you much about it but others on this
list
> do use it, they may have more to say...
>
> About the 'icupkg' utility missing, this is ignorable, you just won't get
> the PyLucene/PyICU integration, which is not indispensable.
>
> Andi..
>
> On Thu, 21 Jul 2011, Thomas Koch wrote:
>
> > I've just tried to build PyLucene 3.3 on win32 and failed.
> > This may be unrelated to V3.3 though as I tried the build process with
minGW
> > for the first time (used MSVC before)! Just wondering if I'm doing sth
wrong
> > or anyone had this issue and can help:
> >
> > Using
> > - Python 2.6.6 (r266:84297, Aug 24 2010, 18:46:32) [MSC v.1500 32 bit
> > (Intel)] on win32
> > - jdk1.6.0_14
> > - mingw32-gcc (gcc (GCC) 4.5.2)
> > - setuptools.__version__'0.6c11'
> > - msys-make (GNU Make 3.81)
> > - ant 1.7.1
> >
> > I'm able to build (and install) JCC:
> > ./jcc-2.10-py2.6-win32.egg
> >>>> jcc.initVM()
> > <jcc.JCCEnv object at 0x01BAF0B0>
> >
> > Then "make" runs fine until the final "python -m jcc.__main__ xyz.jar
...
> > --build"
> > Here python.exe crashes (windows popup asking to send details to
> > somewhere...)
> > make: *** [compile] Error 5
> >
> > The only warnings I get are
> >
> > which: icupkg: unknown command
> > ICU not installed
> > (is there a minGW package for that?)
> >
> > This is Windows-Vista 32-bit. Attached is my Makefile chunk.
> >
> > Any ideas? Has anyone yet tried to build PyLucene within
> > virtualenv(ironment) and is this suggested?
> >
> > I fear the answer is "you have to build Python with MinGW" ,-(
> >
> > I may get back to MSVC but would also like to get this running with
MinGW...
> >
> > Regards
> > Thomas
> > --
> > # Makefile [...]
> > # Windows (Win32, msys/MinGW, Python 2.6.6, Java 1.6, ant 1.7.1
> > PREFIX_PYTHON=C:\\Devel\\Python26
> >
ANT=C:\\Devel\\Eclipse\\eclipse36\\plugins\\org.apache.ant_1.7.1.v20100518-1
> > 145\\bin\\ant
> > PYTHON=$(PREFIX_PYTHON)\\python.exe
> > JCC=$(PYTHON) -m jcc.__main__ --shared --compiler mingw32
> > NUM_FILES=3
> >
> >
> > Imports work to some extend ... here's make output with -v -d args for
> > python:
> > ...
> > import jcc # directory
> > c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc
> > #
> >
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\__init__.py
> > c
> > matches
> >
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\__init__.py
> > import jcc # precompiled from
> >
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\__init__.py
> > c
> > #
> >
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\config.pyc
> > matches
> >
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\config.py
> > import jcc.config # precompiled from
> >
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\config.pyc
> > import jcc._jcc # dynamically loaded from
> >
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\_jcc.pyd
> > #
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\cpp.pyc
> > matches
> > c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\cpp.py
> > import jcc.cpp # precompiled from
> > c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\cpp.pyc
> > # c:\Devel\Python26\lib\zipfile.pyc matches
c:\Devel\Python26\lib\zipfile.py
> > import zipfile # precompiled from c:\Devel\Python26\lib\zipfile.pyc
> > # c:\Devel\Python26\lib\struct.pyc matches
c:\Devel\Python26\lib\struct.py
> > import struct # precompiled from c:\Devel\Python26\lib\struct.pyc
> > import _struct # builtin
> > import time # builtin
> > # c:\Devel\Python26\lib\shutil.pyc matches
c:\Devel\Python26\lib\shutil.py
> > import shutil # precompiled from c:\Devel\Python26\lib\shutil.pyc
> > # c:\Devel\Python26\lib\fnmatch.pyc matches
c:\Devel\Python26\lib\fnmatch.py
> > import fnmatch # precompiled from c:\Devel\Python26\lib\fnmatch.pyc
> > import binascii # builtin
> > import cStringIO # builtin
> > import zlib # builtin
> > #
> >
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\python.pyc
> > matches
> >
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\python.py
> > import jcc.python # precompiled from
> >
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\python.pyc
> > # c:\Devel\Python26\lib\platform.pyc matches
> > c:\Devel\Python26\lib\platform.py
> > import platform # precompiled from c:\Devel\Python26\lib\platform.pyc
> > # c:\Devel\Python26\lib\string.pyc matches
c:\Devel\Python26\lib\string.py
> > import string # precompiled from c:\Devel\Python26\lib\string.pyc
> > import strop # builtin
> > import itertools # builtin
> > make: *** [compile] Error 5
> >
> >> -----Original Message-----
> >> From: Andi Vajda [mailto:vajda@apache.org]
> >> Sent: Thursday, July 21, 2011 12:47 PM
> >> To: pylucene-dev@lucene.apache.org
> >> Cc: general@lucene.apache.org
> >> Subject: [VOTE] Release PyLucene 3.3 (rc2)
> >>
> >>
> >> The Apache PyLucene 3.3-2 release closely tracking the recent release
of
> >> Apache Lucene Java 3.3 is ready.
> >>
> >> A release candidate is available from:
> >> http://people.apache.org/~vajda/staging_area/
> >>
> >> This new release candidate fixes an issue with wrapping the new
grouping
> >> contrib module which is now part of the PyLucene build.
> >>
> >> A list of changes in this release can be seen at:
> >>
> >
http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_3/CHANGE
> > S
> >>
> >> PyLucene 3.3 is built with JCC 2.10 included in these release
artifacts.
> >>
> >> A list of Lucene Java changes can be seen at:
> >>
> >
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANG
> > ES
> >> .txt
> >>
> >> Please vote to release these artifacts as PyLucene 3.3-2.
> >>
> >> 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.3 (rc2)
Posted by Andi Vajda <va...@apache.org>.
Hi Thomas,
I don't use mingw so I can't tell you much about it but others on this list
do use it, they may have more to say...
About the 'icupkg' utility missing, this is ignorable, you just won't get
the PyLucene/PyICU integration, which is not indispensable.
Andi..
On Thu, 21 Jul 2011, Thomas Koch wrote:
> I've just tried to build PyLucene 3.3 on win32 and failed.
> This may be unrelated to V3.3 though as I tried the build process with minGW
> for the first time (used MSVC before)! Just wondering if I'm doing sth wrong
> or anyone had this issue and can help:
>
> Using
> - Python 2.6.6 (r266:84297, Aug 24 2010, 18:46:32) [MSC v.1500 32 bit
> (Intel)] on win32
> - jdk1.6.0_14
> - mingw32-gcc (gcc (GCC) 4.5.2)
> - setuptools.__version__'0.6c11'
> - msys-make (GNU Make 3.81)
> - ant 1.7.1
>
> I'm able to build (and install) JCC:
> ./jcc-2.10-py2.6-win32.egg
>>>> jcc.initVM()
> <jcc.JCCEnv object at 0x01BAF0B0>
>
> Then "make" runs fine until the final "python -m jcc.__main__ xyz.jar ...
> --build"
> Here python.exe crashes (windows popup asking to send details to
> somewhere...)
> make: *** [compile] Error 5
>
> The only warnings I get are
>
> which: icupkg: unknown command
> ICU not installed
> (is there a minGW package for that?)
>
> This is Windows-Vista 32-bit. Attached is my Makefile chunk.
>
> Any ideas? Has anyone yet tried to build PyLucene within
> virtualenv(ironment) and is this suggested?
>
> I fear the answer is "you have to build Python with MinGW" ,-(
>
> I may get back to MSVC but would also like to get this running with MinGW...
>
> Regards
> Thomas
> --
> # Makefile [...]
> # Windows (Win32, msys/MinGW, Python 2.6.6, Java 1.6, ant 1.7.1
> PREFIX_PYTHON=C:\\Devel\\Python26
> ANT=C:\\Devel\\Eclipse\\eclipse36\\plugins\\org.apache.ant_1.7.1.v20100518-1
> 145\\bin\\ant
> PYTHON=$(PREFIX_PYTHON)\\python.exe
> JCC=$(PYTHON) -m jcc.__main__ --shared --compiler mingw32
> NUM_FILES=3
>
>
> Imports work to some extend ... here's make output with -v -d args for
> python:
> ...
> import jcc # directory
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc
> #
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\__init__.py
> c
> matches
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\__init__.py
> import jcc # precompiled from
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\__init__.py
> c
> #
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\config.pyc
> matches
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\config.py
> import jcc.config # precompiled from
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\config.pyc
> import jcc._jcc # dynamically loaded from
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\_jcc.pyd
> # c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\cpp.pyc
> matches
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\cpp.py
> import jcc.cpp # precompiled from
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\cpp.pyc
> # c:\Devel\Python26\lib\zipfile.pyc matches c:\Devel\Python26\lib\zipfile.py
> import zipfile # precompiled from c:\Devel\Python26\lib\zipfile.pyc
> # c:\Devel\Python26\lib\struct.pyc matches c:\Devel\Python26\lib\struct.py
> import struct # precompiled from c:\Devel\Python26\lib\struct.pyc
> import _struct # builtin
> import time # builtin
> # c:\Devel\Python26\lib\shutil.pyc matches c:\Devel\Python26\lib\shutil.py
> import shutil # precompiled from c:\Devel\Python26\lib\shutil.pyc
> # c:\Devel\Python26\lib\fnmatch.pyc matches c:\Devel\Python26\lib\fnmatch.py
> import fnmatch # precompiled from c:\Devel\Python26\lib\fnmatch.pyc
> import binascii # builtin
> import cStringIO # builtin
> import zlib # builtin
> #
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\python.pyc
> matches
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\python.py
> import jcc.python # precompiled from
> c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\python.pyc
> # c:\Devel\Python26\lib\platform.pyc matches
> c:\Devel\Python26\lib\platform.py
> import platform # precompiled from c:\Devel\Python26\lib\platform.pyc
> # c:\Devel\Python26\lib\string.pyc matches c:\Devel\Python26\lib\string.py
> import string # precompiled from c:\Devel\Python26\lib\string.pyc
> import strop # builtin
> import itertools # builtin
> make: *** [compile] Error 5
>
>> -----Original Message-----
>> From: Andi Vajda [mailto:vajda@apache.org]
>> Sent: Thursday, July 21, 2011 12:47 PM
>> To: pylucene-dev@lucene.apache.org
>> Cc: general@lucene.apache.org
>> Subject: [VOTE] Release PyLucene 3.3 (rc2)
>>
>>
>> The Apache PyLucene 3.3-2 release closely tracking the recent release of
>> Apache Lucene Java 3.3 is ready.
>>
>> A release candidate is available from:
>> http://people.apache.org/~vajda/staging_area/
>>
>> This new release candidate fixes an issue with wrapping the new grouping
>> contrib module which is now part of the PyLucene build.
>>
>> A list of changes in this release can be seen at:
>>
> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_3/CHANGE
> S
>>
>> PyLucene 3.3 is built with JCC 2.10 included in these release artifacts.
>>
>> A list of Lucene Java changes can be seen at:
>>
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANG
> ES
>> .txt
>>
>> Please vote to release these artifacts as PyLucene 3.3-2.
>>
>> 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.3 (rc2)
Posted by Thomas Koch <ko...@orbiteam.de>.
Hi,
I've just tried to build PyLucene 3.3 on win32 and failed.
This may be unrelated to V3.3 though as I tried the build process with minGW
for the first time (used MSVC before)! Just wondering if I'm doing sth wrong
or anyone had this issue and can help:
Using
- Python 2.6.6 (r266:84297, Aug 24 2010, 18:46:32) [MSC v.1500 32 bit
(Intel)] on win32
- jdk1.6.0_14
- mingw32-gcc (gcc (GCC) 4.5.2)
- setuptools.__version__'0.6c11'
- msys-make (GNU Make 3.81)
- ant 1.7.1
I'm able to build (and install) JCC:
./jcc-2.10-py2.6-win32.egg
>>> jcc.initVM()
<jcc.JCCEnv object at 0x01BAF0B0>
Then "make" runs fine until the final "python -m jcc.__main__ xyz.jar ...
--build"
Here python.exe crashes (windows popup asking to send details to
somewhere...)
make: *** [compile] Error 5
The only warnings I get are
which: icupkg: unknown command
ICU not installed
(is there a minGW package for that?)
This is Windows-Vista 32-bit. Attached is my Makefile chunk.
Any ideas? Has anyone yet tried to build PyLucene within
virtualenv(ironment) and is this suggested?
I fear the answer is "you have to build Python with MinGW" ,-(
I may get back to MSVC but would also like to get this running with MinGW...
Regards
Thomas
--
# Makefile [...]
# Windows (Win32, msys/MinGW, Python 2.6.6, Java 1.6, ant 1.7.1
PREFIX_PYTHON=C:\\Devel\\Python26
ANT=C:\\Devel\\Eclipse\\eclipse36\\plugins\\org.apache.ant_1.7.1.v20100518-1
145\\bin\\ant
PYTHON=$(PREFIX_PYTHON)\\python.exe
JCC=$(PYTHON) -m jcc.__main__ --shared --compiler mingw32
NUM_FILES=3
Imports work to some extend ... here's make output with -v -d args for
python:
...
import jcc # directory
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc
#
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\__init__.py
c
matches
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\__init__.py
import jcc # precompiled from
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\__init__.py
c
#
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\config.pyc
matches
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\config.py
import jcc.config # precompiled from
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\config.pyc
import jcc._jcc # dynamically loaded from
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\_jcc.pyd
# c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\cpp.pyc
matches
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\cpp.py
import jcc.cpp # precompiled from
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\cpp.pyc
# c:\Devel\Python26\lib\zipfile.pyc matches c:\Devel\Python26\lib\zipfile.py
import zipfile # precompiled from c:\Devel\Python26\lib\zipfile.pyc
# c:\Devel\Python26\lib\struct.pyc matches c:\Devel\Python26\lib\struct.py
import struct # precompiled from c:\Devel\Python26\lib\struct.pyc
import _struct # builtin
import time # builtin
# c:\Devel\Python26\lib\shutil.pyc matches c:\Devel\Python26\lib\shutil.py
import shutil # precompiled from c:\Devel\Python26\lib\shutil.pyc
# c:\Devel\Python26\lib\fnmatch.pyc matches c:\Devel\Python26\lib\fnmatch.py
import fnmatch # precompiled from c:\Devel\Python26\lib\fnmatch.pyc
import binascii # builtin
import cStringIO # builtin
import zlib # builtin
#
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\python.pyc
matches
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\python.py
import jcc.python # precompiled from
c:\Devel\Python26\lib\site-packages\jcc-2.10-py2.6-win32.egg\jcc\python.pyc
# c:\Devel\Python26\lib\platform.pyc matches
c:\Devel\Python26\lib\platform.py
import platform # precompiled from c:\Devel\Python26\lib\platform.pyc
# c:\Devel\Python26\lib\string.pyc matches c:\Devel\Python26\lib\string.py
import string # precompiled from c:\Devel\Python26\lib\string.pyc
import strop # builtin
import itertools # builtin
make: *** [compile] Error 5
> -----Original Message-----
> From: Andi Vajda [mailto:vajda@apache.org]
> Sent: Thursday, July 21, 2011 12:47 PM
> To: pylucene-dev@lucene.apache.org
> Cc: general@lucene.apache.org
> Subject: [VOTE] Release PyLucene 3.3 (rc2)
>
>
> The Apache PyLucene 3.3-2 release closely tracking the recent release of
> Apache Lucene Java 3.3 is ready.
>
> A release candidate is available from:
> http://people.apache.org/~vajda/staging_area/
>
> This new release candidate fixes an issue with wrapping the new grouping
> contrib module which is now part of the PyLucene build.
>
> A list of changes in this release can be seen at:
>
http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_3/CHANGE
S
>
> PyLucene 3.3 is built with JCC 2.10 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
>
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANG
ES
> .txt
>
> Please vote to release these artifacts as PyLucene 3.3-2.
>
> 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
[VOTE] Release PyLucene 3.3 (rc2)
Posted by Andi Vajda <va...@apache.org>.
The Apache PyLucene 3.3-2 release closely tracking the recent release of
Apache Lucene Java 3.3 is ready.
A release candidate is available from:
http://people.apache.org/~vajda/staging_area/
This new release candidate fixes an issue with wrapping the new grouping
contrib module which is now part of the PyLucene build.
A list of changes in this release can be seen at:
http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_3/CHANGES
PyLucene 3.3 is built with JCC 2.10 included in these release artifacts.
A list of Lucene Java changes can be seen at:
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
Please vote to release these artifacts as PyLucene 3.3-2.
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.3.0
Posted by Andi Vajda <va...@apache.org>.
On Jul 2, 2011, at 15:20, Darren Govoni <da...@ontrenet.com> wrote:
> Without the third 0, how will you version critical patch releases should they be necessary?
If the patch comes from Lucene, then I'd use their new version number, as usual. If it's a PyLucene fix, its version would go from 3.3-1 to 3.3-2.
Andi..
>
> On 07/02/2011 09:13 AM, Andi Vajda wrote:
>> On Jul 2, 2011, at 13:58, Christian Heimes<li...@cheimes.de> wrote:
>>
>>> Am 01.07.2011 14:24, schrieb Andi Vajda:
>>>> The PyLucene 3.3.0-1 release closely tracking the recent release of Lucene
>>>> Java 3.3 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_3/CHANGES
>>>>
>>>> PyLucene 3.3.0 is built with JCC 2.9 included in these release artifacts.
>>>>
>>>> A list of Lucene Java changes can be seen at:
>>>> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
>>>>
>>>> Please vote to release these artifacts as PyLucene 3.3.0-1.
>>> I've tested PyLucene 3.3 with your application, everything still works.
>>> I can't comment on new features, though.
>>>
>>> +1 from me
>>>
>>> By the way could you please keep a consistent version schema? You are
>>> slowly dropping the zero at the end. ;)
>>>
>>> pylucene-3.1.0-1-src.tar.gz LUCENE_VER=3.1.0
>>> pylucene-3.2.0-1-src.tar.gz LUCENE_VER=3.2
>>> pylucene-3.3-1-src.tar.gz LUCENE_VER=3.3
>> :-)
>> I resisted the Lucene Java 0 droppage but it got the best of me.
>>
>> Andi..
>>
>>> Christian
Re: [VOTE] Release PyLucene 3.3.0
Posted by Darren Govoni <da...@ontrenet.com>.
Without the third 0, how will you version critical patch releases should
they be necessary?
On 07/02/2011 09:13 AM, Andi Vajda wrote:
> On Jul 2, 2011, at 13:58, Christian Heimes<li...@cheimes.de> wrote:
>
>> Am 01.07.2011 14:24, schrieb Andi Vajda:
>>> The PyLucene 3.3.0-1 release closely tracking the recent release of Lucene
>>> Java 3.3 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_3/CHANGES
>>>
>>> PyLucene 3.3.0 is built with JCC 2.9 included in these release artifacts.
>>>
>>> A list of Lucene Java changes can be seen at:
>>> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
>>>
>>> Please vote to release these artifacts as PyLucene 3.3.0-1.
>> I've tested PyLucene 3.3 with your application, everything still works.
>> I can't comment on new features, though.
>>
>> +1 from me
>>
>> By the way could you please keep a consistent version schema? You are
>> slowly dropping the zero at the end. ;)
>>
>> pylucene-3.1.0-1-src.tar.gz LUCENE_VER=3.1.0
>> pylucene-3.2.0-1-src.tar.gz LUCENE_VER=3.2
>> pylucene-3.3-1-src.tar.gz LUCENE_VER=3.3
> :-)
> I resisted the Lucene Java 0 droppage but it got the best of me.
>
> Andi..
>
>> Christian
Re: [VOTE] Release PyLucene 3.3.0
Posted by Andi Vajda <va...@apache.org>.
On Jul 2, 2011, at 13:58, Christian Heimes <li...@cheimes.de> wrote:
> Am 01.07.2011 14:24, schrieb Andi Vajda:
>>
>> The PyLucene 3.3.0-1 release closely tracking the recent release of Lucene
>> Java 3.3 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_3/CHANGES
>>
>> PyLucene 3.3.0 is built with JCC 2.9 included in these release artifacts.
>>
>> A list of Lucene Java changes can be seen at:
>> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
>>
>> Please vote to release these artifacts as PyLucene 3.3.0-1.
>
> I've tested PyLucene 3.3 with your application, everything still works.
> I can't comment on new features, though.
>
> +1 from me
>
> By the way could you please keep a consistent version schema? You are
> slowly dropping the zero at the end. ;)
>
> pylucene-3.1.0-1-src.tar.gz LUCENE_VER=3.1.0
> pylucene-3.2.0-1-src.tar.gz LUCENE_VER=3.2
> pylucene-3.3-1-src.tar.gz LUCENE_VER=3.3
:-)
I resisted the Lucene Java 0 droppage but it got the best of me.
Andi..
>
> Christian
Re: [VOTE] Release PyLucene 3.3.0
Posted by Christian Heimes <li...@cheimes.de>.
Am 01.07.2011 14:24, schrieb Andi Vajda:
>
> The PyLucene 3.3.0-1 release closely tracking the recent release of Lucene
> Java 3.3 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_3/CHANGES
>
> PyLucene 3.3.0 is built with JCC 2.9 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.3.0-1.
I've tested PyLucene 3.3 with your application, everything still works.
I can't comment on new features, though.
+1 from me
By the way could you please keep a consistent version schema? You are
slowly dropping the zero at the end. ;)
pylucene-3.1.0-1-src.tar.gz LUCENE_VER=3.1.0
pylucene-3.2.0-1-src.tar.gz LUCENE_VER=3.2
pylucene-3.3-1-src.tar.gz LUCENE_VER=3.3
Christian
[VOTE] Release PyLucene 3.3 (rc2)
Posted by Andi Vajda <va...@apache.org>.
The Apache PyLucene 3.3-2 release closely tracking the recent release of
Apache Lucene Java 3.3 is ready.
A release candidate is available from:
http://people.apache.org/~vajda/staging_area/
This new release candidate fixes an issue with wrapping the new grouping
contrib module which is now part of the PyLucene build.
A list of changes in this release can be seen at:
http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_3/CHANGES
PyLucene 3.3 is built with JCC 2.10 included in these release artifacts.
A list of Lucene Java changes can be seen at:
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
Please vote to release these artifacts as PyLucene 3.3-2.
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
[VOTE] Release PyLucene 3.3.0
Posted by Andi Vajda <va...@apache.org>.
The PyLucene 3.3.0-1 release closely tracking the recent release of Lucene
Java 3.3 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_3/CHANGES
PyLucene 3.3.0 is built with JCC 2.9 included in these release artifacts.
A list of Lucene Java changes can be seen at:
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
Please vote to release these artifacts as PyLucene 3.3.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
pps: here is my +1
[VOTE] Release PyLucene 3.3.0
Posted by Andi Vajda <va...@apache.org>.
The PyLucene 3.3.0-1 release closely tracking the recent release of Lucene
Java 3.3 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_3/CHANGES
PyLucene 3.3.0 is built with JCC 2.9 included in these release artifacts.
A list of Lucene Java changes can be seen at:
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_3/lucene/CHANGES.txt
Please vote to release these artifacts as PyLucene 3.3.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
pps: here is my +1
Re: [VOTE] Release PyLucene 3.2.0
Posted by Michael McCandless <lu...@mikemccandless.com>.
+1
I built on OS X 10.6.6, passed all tests (I think? No overall summary
in the end, but I didn't see any obvious problem), and ran my usual
smoke test indexing first 100K docs from a line file from Wikipedia,
and running a few searches.
Mike McCandless
http://blog.mikemccandless.com
On Mon, Jun 6, 2011 at 4:58 PM, Andi Vajda <va...@apache.org> wrote:
>
> The PyLucene 3.2.0-1 release closely tracking the recent release of Lucene
> Java 3.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_2/CHANGES
>
> PyLucene 3.2.0 is built with JCC 2.9 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_2/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.2.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
>
> pps: here is my +1
>
>
Re: [VOTE] Release PyLucene 3.2.0
Posted by Michael McCandless <lu...@mikemccandless.com>.
+1
I built on OS X 10.6.6, passed all tests (I think? No overall summary
in the end, but I didn't see any obvious problem), and ran my usual
smoke test indexing first 100K docs from a line file from Wikipedia,
and running a few searches.
Mike McCandless
http://blog.mikemccandless.com
On Mon, Jun 6, 2011 at 4:58 PM, Andi Vajda <va...@apache.org> wrote:
>
> The PyLucene 3.2.0-1 release closely tracking the recent release of Lucene
> Java 3.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_2/CHANGES
>
> PyLucene 3.2.0 is built with JCC 2.9 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_2/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.2.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
>
> pps: here is my +1
>
>
Re: [VOTE] Release PyLucene 3.2.0
Posted by Robert Muir <rc...@gmail.com>.
+1
I built the included jcc and pylucene, ran the test suite
successfully, checked license headers on the pylucene/jcc sources and
tests, and verified sig and hash
On Mon, Jun 6, 2011 at 4:58 PM, Andi Vajda <va...@apache.org> wrote:
>
> The PyLucene 3.2.0-1 release closely tracking the recent release of Lucene
> Java 3.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_2/CHANGES
>
> PyLucene 3.2.0 is built with JCC 2.9 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_2/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.2.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
>
> pps: here is my +1
>
>
Re: [VOTE] Release PyLucene 3.2.0
Posted by Andi Vajda <va...@apache.org>.
This vote has now passed.
It got 3 +1 votes from PMC members and no -1.
Expect a release announcement shortly.
Thank you for voting !
Andi..
On Mon, 6 Jun 2011, Andi Vajda wrote:
> The PyLucene 3.2.0-1 release closely tracking the recent release of Lucene
> Java 3.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_2/CHANGES
>
> PyLucene 3.2.0 is built with JCC 2.9 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_2/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.2.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
>
> pps: here is my +1
>
[VOTE] Release PyLucene 3.2.0
Posted by Andi Vajda <va...@apache.org>.
The PyLucene 3.2.0-1 release closely tracking the recent release of Lucene
Java 3.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_2/CHANGES
PyLucene 3.2.0 is built with JCC 2.9 included in these release artifacts.
A list of Lucene Java changes can be seen at:
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_2/lucene/CHANGES.txt
Please vote to release these artifacts as PyLucene 3.2.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
pps: here is my +1
Re: [VOTE] Release PyLucene 3.1.0
Posted by Bill Janssen <ja...@parc.com>.
I'm seeing parse failures on this query string:
"categories:RSSReader AND id:[00000-00-0000-000 TO 01299-51-3142-795] AND NOT categories:RSSReader/_noexpire_"
thr002: RSSReader: Traceback (most recent call last):
thr002: File "/local/lib/UpLib-1.7.11/site-extensions/RSSReader.py", line 271, in _scan_rss_sites
thr002: hits = repo.do_query("categories:RSSReader AND id:[00000-00-0000-000 TO %s] AND NOT categories:RSSReader/_noexpire_" % old_id)
thr002: File "/local/share/UpLib-1.7.11/code/uplib/repository.py", line 1172, in do_query
thr002: results = self.do_full_query(query_string, searchtype)
thr002: File "/local/share/UpLib-1.7.11/code/uplib/repository.py", line 1196, in do_full_query
thr002: results = self.pylucene_search(searchtype, query_string)
thr002: File "/local/share/UpLib-1.7.11/code/uplib/repository.py", line 1081, in pylucene_search
thr002: v = self.__search_context.search(query_string)
thr002: File "/local/share/UpLib-1.7.11/code/uplib/indexing.py", line 913, in search
thr002: parsed_query = query_parser.parseQ(query)
thr002: File "/local/share/UpLib-1.7.11/code/uplib/indexing.py", line 550, in parseQ
thr002: query = QueryParser.parse(self, querystring)
thr002: JavaError: org.apache.jcc.PythonException: getFieldQuery_quoted
thr002: AttributeError: getFieldQuery_quoted
thr002: Java stacktrace:
thr002: org.apache.jcc.PythonException: getFieldQuery_quoted
thr002: AttributeError: getFieldQuery_quoted
thr002: at org.apache.pylucene.queryParser.PythonMultiFieldQueryParser.getFieldQuery_quoted(Native Method)
thr002: at org.apache.pylucene.queryParser.PythonMultiFieldQueryParser.getFieldQuery(Unknown Source)
thr002: at org.apache.lucene.queryParser.QueryParser.Term(QueryParser.java:1421)
thr002: at org.apache.lucene.queryParser.QueryParser.Clause(QueryParser.java:1309)
thr002: at org.apache.lucene.queryParser.QueryParser.Query(QueryParser.java:1237)
thr002: at org.apache.lucene.queryParser.QueryParser.TopLevelQuery(QueryParser.java:1226)
thr002: at org.apache.lucene.queryParser.QueryParser.parse(QueryParser.java:206)
Bill
Re: [VOTE] Release PyLucene 3.1.0
Posted by Michael McCandless <lu...@mikemccandless.com>.
+1 to release
I installed on Mac OS X 10.6.6, and ran my usual smoke test (indexing
first 100K docs from Wikipedia, optimizing, running a few queries).
Looks good!
Mike
http://blog.mikemccandless.com
On Sat, Apr 2, 2011 at 4:28 PM, Andi Vajda <va...@apache.org> wrote:
>
> The PyLucene 3.1.0-1 release closely tracking the recent release of Lucene
> Java 3.1.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/pylucene_3_1/CHANGES
>
> PyLucene 3.1.0 is built with JCC 2.8 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_1/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.1.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
>
> pps: here is my +1
>
[VOTE] Release PyLucene 3.2.0
Posted by Andi Vajda <va...@apache.org>.
The PyLucene 3.2.0-1 release closely tracking the recent release of Lucene
Java 3.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_2/CHANGES
PyLucene 3.2.0 is built with JCC 2.9 included in these release artifacts.
A list of Lucene Java changes can be seen at:
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_2/lucene/CHANGES.txt
Please vote to release these artifacts as PyLucene 3.2.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
pps: here is my +1
Re: [VOTE] Release PyLucene 3.1.0
Posted by Andi Vajda <va...@apache.org>.
On Sat, 2 Apr 2011, Andi Vajda wrote:
> The PyLucene 3.1.0-1 release closely tracking the recent release of Lucene
> Java 3.1.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/pylucene_3_1/CHANGES
>
> PyLucene 3.1.0 is built with JCC 2.8 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_1/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.1.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
>
> pps: here is my +1
This vote has passed, thank you !
Expect a release announcement shortly.
Andi..
Re: [VOTE] Release PyLucene 3.1.0
Posted by Andi Vajda <va...@apache.org>.
On Sat, 2 Apr 2011, Andi Vajda wrote:
> The PyLucene 3.1.0-1 release closely tracking the recent release of Lucene
> Java 3.1.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/pylucene_3_1/CHANGES
>
> PyLucene 3.1.0 is built with JCC 2.8 included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_1/lucene/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 3.1.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
>
> pps: here is my +1
This vote has passed, thank you !
Expect a release announcement shortly.
Andi..
[VOTE] Release PyLucene 3.1.0
Posted by Andi Vajda <va...@apache.org>.
The PyLucene 3.1.0-1 release closely tracking the recent release of Lucene
Java 3.1.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/pylucene_3_1/CHANGES
PyLucene 3.1.0 is built with JCC 2.8 included in these release artifacts.
A list of Lucene Java changes can be seen at:
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_1/lucene/CHANGES.txt
Please vote to release these artifacts as PyLucene 3.1.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
pps: here is my +1
Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Posted by Michael McCandless <lu...@mikemccandless.com>.
+1 to both.
I installed both on Linux (Fedora 13) and ran my test python script
that indexes first 100K line docs from wikipedia and runs a few
searches. No problems!
Mike
On Sun, Dec 5, 2010 at 1:50 AM, Andi Vajda <va...@apache.org> wrote:
>
> With the recent releases of Lucene Java 2.9.4 and 3.0.3, the PyLucene
> 2.9.4-1 and 3.0.3-1 releases closely tracking them are ready.
>
> Release candidates are 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_2_9/CHANGES
> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_0/CHANGES
>
> All versions of PyLucene are built with the same version of JCC, currently
> version 2.7, included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/CHANGES.txt
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_3_0/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 2.9.4-1 and 3.0.3-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 2.9.4-1 and 3.0.3-1
Posted by Robert Muir <rc...@gmail.com>.
On Sun, Dec 5, 2010 at 1:50 AM, Andi Vajda <va...@apache.org> wrote:
>
> With the recent releases of Lucene Java 2.9.4 and 3.0.3, the PyLucene
> 2.9.4-1 and 3.0.3-1 releases closely tracking them are ready.
>
> Release candidates are 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_2_9/CHANGES
> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_0/CHANGES
>
> All versions of PyLucene are built with the same version of JCC, currently
> version 2.7, included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/CHANGES.txt
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_3_0/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 2.9.4-1 and 3.0.3-1.
>
+1, everything looks in order, building pylucene and running 'make
test' seemed fine on both versions.
Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Posted by Michael McCandless <lu...@mikemccandless.com>.
+1 to both.
I installed both on Linux (Fedora 13) and ran my test python script
that indexes first 100K line docs from wikipedia and runs a few
searches. No problems!
Mike
On Sun, Dec 5, 2010 at 1:50 AM, Andi Vajda <va...@apache.org> wrote:
>
> With the recent releases of Lucene Java 2.9.4 and 3.0.3, the PyLucene
> 2.9.4-1 and 3.0.3-1 releases closely tracking them are ready.
>
> Release candidates are 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_2_9/CHANGES
> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_0/CHANGES
>
> All versions of PyLucene are built with the same version of JCC, currently
> version 2.7, included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/CHANGES.txt
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_3_0/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 2.9.4-1 and 3.0.3-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
>
[VOTE] Release PyLucene 3.1.0
Posted by Andi Vajda <va...@apache.org>.
The PyLucene 3.1.0-1 release closely tracking the recent release of Lucene
Java 3.1.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/pylucene_3_1/CHANGES
PyLucene 3.1.0 is built with JCC 2.8 included in these release artifacts.
A list of Lucene Java changes can be seen at:
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_3_1/lucene/CHANGES.txt
Please vote to release these artifacts as PyLucene 3.1.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
pps: here is my +1
Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Posted by Bill Janssen <ja...@parc.com>.
>>>>> "Adil" == Adil Lotia <ad...@gmail.com> writes:
Adil> Hi Andi I downloaded the release candidate from your staging
Adil> area, and will be running pylucene on OS X. I am not sure if
Adil> this is intentional, but was there a reason for this specific
Adil> change?
Adil> adil:681 lucene $ diff pylucene-3.0.2-1/jcc/setup.py
Adil> pylucene-3.0.3-1/jcc/setup.py ... 47c47 < 'darwin':
Adil> '/System/Library/Frameworks/JavaVM.framework/Versions/Current',
Adil> ---
>> 'darwin':
Adil> '/Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/JavaVM.framework/Versions/Current',
Adil> ...
Adil> I have the standard JDK installation, which is in /System.
As I understand it, Apple is preparing to move to something like the JRE
under /System, and the JDK under /Developer/... (which sort of makes
sense). So development tools like "jar" and "javac" will move to the
/Developer tree.
Adil> Also, this is my system config: adil:689 lucene $
Adil> /usr/bin/sw_vers ProductName: Mac OS X ProductVersion: 10.5.8
Adil> BuildVersion: 9L31a
Adil> adil:690 lucene $ python -V Python 2.6.6
Adil> adil:691 lucene $ java -version java version "1.5.0_26"
Adil> Java(TM) 2 Runtime Environment, Standard Edition (build
Adil> 1.5.0_26-b03-376-9M3263) Java HotSpot(TM) Client VM (build
Adil> 1.5.0_26-156, mixed mode, sharing) adil:692 lucene
This is a pretty non-standard Mac. OS X 10.5.8 uses Python 2.5.1, not
2.6.6. And the "standard" Java is 1.6.0_22, though I also usually
compile with 1.5.
Bill
Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Posted by Adil Lotia <ad...@gmail.com>.
Wonderful!
Thank you for the quick review and fix on that one.
Cheers,
-Adil
On Thu, Dec 9, 2010 at 1:55 PM, Andi Vajda <va...@apache.org> wrote:
>
> On Tue, 7 Dec 2010, Andi Vajda wrote:
>
>
>> Hi Adil,
>>
>> And for both pylucene-3.0.3-1 (rc) and pylucene-3.0.2-1 when I run the
>>> make
>>> tests, most of the tests run fine, but a couple of them crash Python.
>>> ...
>>> /opt/local/bin/python test/test_PhraseQuery.py
>>> ........
>>> ----------------------------------------------------------------------
>>> Ran 8 tests in 0.162s
>>>
>>> OK
>>> /opt/local/bin/python test/test_PositionIncrement.py
>>> Invalid memory access of location 0x0 eip=0x240ba3b
>>> make: *** [test] Error 1
>>>
>>> I have tested this on three of our 10.5 systems, and it is reproduceable
>>> on
>>> all. (The unit tests complete okay on 10.6). I have tried switching to
>>> Java
>>> 6 and/or Python 2.7, and I still get the same behaviour. This crash is
>>> not
>>> a show-stopper for us. Pylucene is working fine for what we need.
>>>
>>
>> Hmm, let me try this on my 10.5 system and report back.
>> If someone else can try this before I get to it, please us know what you
>> see.
>>
>
> There was indeed a bug with using Java 1.5 where the JNI version was still
> 1.4. This caused some cached methods to be NULL instead of correct pointers.
>
> I fixed this on JCC's trunk (also used by the release candidates) and I
> should be preparing new release artifacts shortly.
>
> Andi..
>
Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Posted by Andi Vajda <va...@apache.org>.
On Tue, 7 Dec 2010, Andi Vajda wrote:
>
> Hi Adil,
>
>> And for both pylucene-3.0.3-1 (rc) and pylucene-3.0.2-1 when I run the make
>> tests, most of the tests run fine, but a couple of them crash Python.
>> ...
>> /opt/local/bin/python test/test_PhraseQuery.py
>> ........
>> ----------------------------------------------------------------------
>> Ran 8 tests in 0.162s
>>
>> OK
>> /opt/local/bin/python test/test_PositionIncrement.py
>> Invalid memory access of location 0x0 eip=0x240ba3b
>> make: *** [test] Error 1
>>
>> I have tested this on three of our 10.5 systems, and it is reproduceable on
>> all. (The unit tests complete okay on 10.6). I have tried switching to Java
>> 6 and/or Python 2.7, and I still get the same behaviour. This crash is not
>> a show-stopper for us. Pylucene is working fine for what we need.
>
> Hmm, let me try this on my 10.5 system and report back.
> If someone else can try this before I get to it, please us know what you see.
There was indeed a bug with using Java 1.5 where the JNI version was still
1.4. This caused some cached methods to be NULL instead of correct pointers.
I fixed this on JCC's trunk (also used by the release candidates) and I
should be preparing new release artifacts shortly.
Andi..
Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Posted by Andi Vajda <va...@apache.org>.
Hi Adil,
> And for both pylucene-3.0.3-1 (rc) and pylucene-3.0.2-1 when I run the make
> tests, most of the tests run fine, but a couple of them crash Python.
> ...
> /opt/local/bin/python test/test_PhraseQuery.py
> ........
> ----------------------------------------------------------------------
> Ran 8 tests in 0.162s
>
> OK
> /opt/local/bin/python test/test_PositionIncrement.py
> Invalid memory access of location 0x0 eip=0x240ba3b
> make: *** [test] Error 1
>
> I have tested this on three of our 10.5 systems, and it is reproduceable on
> all. (The unit tests complete okay on 10.6). I have tried switching to Java
> 6 and/or Python 2.7, and I still get the same behaviour. This crash is not
> a show-stopper for us. Pylucene is working fine for what we need.
Hmm, let me try this on my 10.5 system and report back.
If someone else can try this before I get to it, please us know what you
see.
Thanks !
Andi..
>
> Cheers,
> -Adil
>
> On Sat, Dec 4, 2010 at 10:50 PM, Andi Vajda <va...@apache.org> wrote:
>
>>
>> With the recent releases of Lucene Java 2.9.4 and 3.0.3, the PyLucene
>> 2.9.4-1 and 3.0.3-1 releases closely tracking them are ready.
>>
>> Release candidates are 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_2_9/CHANGES
>>
>> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_0/CHANGES
>>
>> All versions of PyLucene are built with the same version of JCC, currently
>> version 2.7, included in these release artifacts.
>>
>> A list of Lucene Java changes can be seen at:
>> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/CHANGES.txt
>> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_3_0/CHANGES.txt
>>
>> Please vote to release these artifacts as PyLucene 2.9.4-1 and 3.0.3-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 2.9.4-1 and 3.0.3-1
Posted by Andi Vajda <va...@apache.org>.
On Wed, 8 Dec 2010, Adil Lotia wrote:
> I think Xcode 3.1.[34] is the last one which supports10.5. Here's a link to
> get 3.1.3 (requires ADC login:)
> https://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/wa/getSoftware?bundleID=20414
>
> I see some mention that Xcode 3.1.4 is the latest one (for 10.5), but I
> couldn't locate it on Apple's site.
I did find it, after looking around for a bit. 993MB download.
Andi..
>
> Hope this helps! But you probably will have to contend with another mongo
> download!
>
> Cheers,
> -Adil
>
> On Wed, Dec 8, 2010 at 10:03 AM, Andi Vajda <va...@apache.org> wrote:
>
>>
>> On Wed, 8 Dec 2010, Bill Janssen wrote:
>>
>> Andi Vajda <va...@apache.org> wrote:
>>>
>>> Yes, two things made me do this:
>>>> 1. Bill Janssen said on this list that an Apple developer he talked to
>>>> said that the /Developer tree is the correct one to use.
>>>>
>>>
>>> I asked again, and got this answer. Looks like I was (wrong? talking
>>> about a pre-release version of Snow Leopard?); Mike says to just use
>>> /System/Library/Frameworks/JavaVM.framework/Headers, and explains why
>>> that doesn't always work, and that they're aware of the problem.
>>>
>>> So let's just hardcode that path into the setup.py file for "darwin".
>>>
>>
>> That would be the safer thing to do at this point, yes.
>>
>> I wasn't able to build on 10.5 yesterday (my old G4 powerbook needs some
>> refreshing first [1]). Once I confirm 10.5 presents no problems, I'm
>> probably going to revert the setup.py change and prepare new release
>> artifacts and call for another vote.
>>
>> Andi..
>>
>> [1] bitrot story:
>> - the svn I have installed there doesn't support the externals format used
>> - updating svn via MacPorts requires a MacPorts update first
>> - updating MacPorts implies a dev tools update (since it complains about
>> Xcode 3.0 causing "problems")
>> - installing the 3.2.2 devtools on my 10.5.8 G4 powerbook crashes the
>> installer.app, consistently, while "looking for installation volumes"
>> - downloading the 3.2.5 devtools took 3 hrs (3.52GB download, I was not
>> able to find a Xcode-only .dmg, only Xcode+iPhone SDK, iPhone part which
>> is not even supported on 10.5), download completed overnight
>> - no time to continue this until tonight again
>>
>>
>>
>>> Bill
>>>
>>> Subject: Re: how to locate an installed JDK?
>>> From: Mike Swingler <sw...@apple.com>
>>> Date: Wed, 8 Dec 2010 07:13:59 PST
>>> Cc: java-dev <ja...@lists.apple.com>
>>>
>>> On Dec 7, 2010, at 7:08 PM, Bill Janssen wrote:
>>>
>>> Now that we have /usr/libexec/java_home, is there a standard way to
>>>> locate a JDK, with tools like "javac" and "jar" and header files like
>>>> "jni.h"?
>>>>
>>>> The PyLucene project installs a tool called "JCC", which wraps a jar
>>>> file as a Python module, but to build JCC, it has to find a Java JDK
>>>> with header files. Is there a standard way of doing that yet?
>>>>
>>>
>>> To find a $JAVA_HOME for the purposes of using the command line tools,
>>> please use /usr/libexec/java_home. The man page for "java_home"
>>> enumerates all of it's options.
>>>
>>> As for headers, always use
>>> /System/Library/Frameworks/JavaVM.framework/Headers.
>>>
>>> It may be necessary to install the "Java for Mac OS X 10.6 Update 3
>>> Developer Package" or "Java for Mac OS X 10.5 Update 8 Developer
>>> Package" from <http://connect.apple.com> under the "Java" section, to
>>> ensure the native headers are present in the JavaVM.framework. We are
>>> aware that this has caused some inconvenience for otherwise native
>>> projects that make use of the JNI API, and we are leaning towards just
>>> shipping the headers in the regular customer software update package.
>>>
>>> Regards,
>>> Mike Swingler
>>> Java Engineering
>>> Apple Inc.
>>>
>>>
>
Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Posted by Adil Lotia <ad...@gmail.com>.
Hi Andi,
I think Xcode 3.1.[34] is the last one which supports10.5. Here's a link to
get 3.1.3 (requires ADC login:)
https://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/wa/getSoftware?bundleID=20414
I see some mention that Xcode 3.1.4 is the latest one (for 10.5), but I
couldn't locate it on Apple's site.
Hope this helps! But you probably will have to contend with another mongo
download!
Cheers,
-Adil
On Wed, Dec 8, 2010 at 10:03 AM, Andi Vajda <va...@apache.org> wrote:
>
> On Wed, 8 Dec 2010, Bill Janssen wrote:
>
> Andi Vajda <va...@apache.org> wrote:
>>
>> Yes, two things made me do this:
>>> 1. Bill Janssen said on this list that an Apple developer he talked to
>>> said that the /Developer tree is the correct one to use.
>>>
>>
>> I asked again, and got this answer. Looks like I was (wrong? talking
>> about a pre-release version of Snow Leopard?); Mike says to just use
>> /System/Library/Frameworks/JavaVM.framework/Headers, and explains why
>> that doesn't always work, and that they're aware of the problem.
>>
>> So let's just hardcode that path into the setup.py file for "darwin".
>>
>
> That would be the safer thing to do at this point, yes.
>
> I wasn't able to build on 10.5 yesterday (my old G4 powerbook needs some
> refreshing first [1]). Once I confirm 10.5 presents no problems, I'm
> probably going to revert the setup.py change and prepare new release
> artifacts and call for another vote.
>
> Andi..
>
> [1] bitrot story:
> - the svn I have installed there doesn't support the externals format used
> - updating svn via MacPorts requires a MacPorts update first
> - updating MacPorts implies a dev tools update (since it complains about
> Xcode 3.0 causing "problems")
> - installing the 3.2.2 devtools on my 10.5.8 G4 powerbook crashes the
> installer.app, consistently, while "looking for installation volumes"
> - downloading the 3.2.5 devtools took 3 hrs (3.52GB download, I was not
> able to find a Xcode-only .dmg, only Xcode+iPhone SDK, iPhone part which
> is not even supported on 10.5), download completed overnight
> - no time to continue this until tonight again
>
>
>
>> Bill
>>
>> Subject: Re: how to locate an installed JDK?
>> From: Mike Swingler <sw...@apple.com>
>> Date: Wed, 8 Dec 2010 07:13:59 PST
>> Cc: java-dev <ja...@lists.apple.com>
>>
>> On Dec 7, 2010, at 7:08 PM, Bill Janssen wrote:
>>
>> Now that we have /usr/libexec/java_home, is there a standard way to
>>> locate a JDK, with tools like "javac" and "jar" and header files like
>>> "jni.h"?
>>>
>>> The PyLucene project installs a tool called "JCC", which wraps a jar
>>> file as a Python module, but to build JCC, it has to find a Java JDK
>>> with header files. Is there a standard way of doing that yet?
>>>
>>
>> To find a $JAVA_HOME for the purposes of using the command line tools,
>> please use /usr/libexec/java_home. The man page for "java_home"
>> enumerates all of it's options.
>>
>> As for headers, always use
>> /System/Library/Frameworks/JavaVM.framework/Headers.
>>
>> It may be necessary to install the "Java for Mac OS X 10.6 Update 3
>> Developer Package" or "Java for Mac OS X 10.5 Update 8 Developer
>> Package" from <http://connect.apple.com> under the "Java" section, to
>> ensure the native headers are present in the JavaVM.framework. We are
>> aware that this has caused some inconvenience for otherwise native
>> projects that make use of the JNI API, and we are leaning towards just
>> shipping the headers in the regular customer software update package.
>>
>> Regards,
>> Mike Swingler
>> Java Engineering
>> Apple Inc.
>>
>>
Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Posted by Andi Vajda <va...@apache.org>.
On Wed, 8 Dec 2010, Andi Vajda wrote:
>
> On Wed, 8 Dec 2010, Bill Janssen wrote:
>
>> Andi Vajda <va...@apache.org> wrote:
>>
>>> Yes, two things made me do this:
>>> 1. Bill Janssen said on this list that an Apple developer he talked to
>>> said that the /Developer tree is the correct one to use.
>>
>> I asked again, and got this answer. Looks like I was (wrong? talking
>> about a pre-release version of Snow Leopard?); Mike says to just use
>> /System/Library/Frameworks/JavaVM.framework/Headers, and explains why
>> that doesn't always work, and that they're aware of the problem.
>>
>> So let's just hardcode that path into the setup.py file for "darwin".
>
> That would be the safer thing to do at this point, yes.
I finally opted to stay with the current setting under /Developer since, if
there is one version that should work out of the box, it should be the
latest OS/Java combination. Once Apple changes it again, if they do, I can
change it back as well so that more setups work again out of the box.
Andi..
>
> I wasn't able to build on 10.5 yesterday (my old G4 powerbook needs some
> refreshing first [1]). Once I confirm 10.5 presents no problems, I'm probably
> going to revert the setup.py change and prepare new release artifacts and
> call for another vote.
>
> Andi..
>
> [1] bitrot story:
> - the svn I have installed there doesn't support the externals format used
> - updating svn via MacPorts requires a MacPorts update first
> - updating MacPorts implies a dev tools update (since it complains about
> Xcode 3.0 causing "problems")
> - installing the 3.2.2 devtools on my 10.5.8 G4 powerbook crashes the
> installer.app, consistently, while "looking for installation volumes"
> - downloading the 3.2.5 devtools took 3 hrs (3.52GB download, I was not
> able to find a Xcode-only .dmg, only Xcode+iPhone SDK, iPhone part which
> is not even supported on 10.5), download completed overnight
> - no time to continue this until tonight again
>
>>
>> Bill
>>
>> Subject: Re: how to locate an installed JDK?
>> From: Mike Swingler <sw...@apple.com>
>> Date: Wed, 8 Dec 2010 07:13:59 PST
>> Cc: java-dev <ja...@lists.apple.com>
>>
>> On Dec 7, 2010, at 7:08 PM, Bill Janssen wrote:
>>
>>> Now that we have /usr/libexec/java_home, is there a standard way to
>>> locate a JDK, with tools like "javac" and "jar" and header files like
>>> "jni.h"?
>>>
>>> The PyLucene project installs a tool called "JCC", which wraps a jar
>>> file as a Python module, but to build JCC, it has to find a Java JDK
>>> with header files. Is there a standard way of doing that yet?
>>
>> To find a $JAVA_HOME for the purposes of using the command line tools,
>> please use /usr/libexec/java_home. The man page for "java_home"
>> enumerates all of it's options.
>>
>> As for headers, always use
>> /System/Library/Frameworks/JavaVM.framework/Headers.
>>
>> It may be necessary to install the "Java for Mac OS X 10.6 Update 3
>> Developer Package" or "Java for Mac OS X 10.5 Update 8 Developer
>> Package" from <http://connect.apple.com> under the "Java" section, to
>> ensure the native headers are present in the JavaVM.framework. We are
>> aware that this has caused some inconvenience for otherwise native
>> projects that make use of the JNI API, and we are leaning towards just
>> shipping the headers in the regular customer software update package.
>>
>> Regards,
>> Mike Swingler
>> Java Engineering
>> Apple Inc.
>>
>
Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Posted by Andi Vajda <va...@apache.org>.
On Wed, 8 Dec 2010, Bill Janssen wrote:
> Andi Vajda <va...@apache.org> wrote:
>
>> Yes, two things made me do this:
>> 1. Bill Janssen said on this list that an Apple developer he talked to
>> said that the /Developer tree is the correct one to use.
>
> I asked again, and got this answer. Looks like I was (wrong? talking
> about a pre-release version of Snow Leopard?); Mike says to just use
> /System/Library/Frameworks/JavaVM.framework/Headers, and explains why
> that doesn't always work, and that they're aware of the problem.
>
> So let's just hardcode that path into the setup.py file for "darwin".
That would be the safer thing to do at this point, yes.
I wasn't able to build on 10.5 yesterday (my old G4 powerbook needs some
refreshing first [1]). Once I confirm 10.5 presents no problems, I'm
probably going to revert the setup.py change and prepare new release
artifacts and call for another vote.
Andi..
[1] bitrot story:
- the svn I have installed there doesn't support the externals format used
- updating svn via MacPorts requires a MacPorts update first
- updating MacPorts implies a dev tools update (since it complains about
Xcode 3.0 causing "problems")
- installing the 3.2.2 devtools on my 10.5.8 G4 powerbook crashes the
installer.app, consistently, while "looking for installation volumes"
- downloading the 3.2.5 devtools took 3 hrs (3.52GB download, I was not
able to find a Xcode-only .dmg, only Xcode+iPhone SDK, iPhone part which
is not even supported on 10.5), download completed overnight
- no time to continue this until tonight again
>
> Bill
>
> Subject: Re: how to locate an installed JDK?
> From: Mike Swingler <sw...@apple.com>
> Date: Wed, 8 Dec 2010 07:13:59 PST
> Cc: java-dev <ja...@lists.apple.com>
>
> On Dec 7, 2010, at 7:08 PM, Bill Janssen wrote:
>
>> Now that we have /usr/libexec/java_home, is there a standard way to
>> locate a JDK, with tools like "javac" and "jar" and header files like
>> "jni.h"?
>>
>> The PyLucene project installs a tool called "JCC", which wraps a jar
>> file as a Python module, but to build JCC, it has to find a Java JDK
>> with header files. Is there a standard way of doing that yet?
>
> To find a $JAVA_HOME for the purposes of using the command line tools,
> please use /usr/libexec/java_home. The man page for "java_home"
> enumerates all of it's options.
>
> As for headers, always use /System/Library/Frameworks/JavaVM.framework/Headers.
>
> It may be necessary to install the "Java for Mac OS X 10.6 Update 3
> Developer Package" or "Java for Mac OS X 10.5 Update 8 Developer
> Package" from <http://connect.apple.com> under the "Java" section, to
> ensure the native headers are present in the JavaVM.framework. We are
> aware that this has caused some inconvenience for otherwise native
> projects that make use of the JNI API, and we are leaning towards just
> shipping the headers in the regular customer software update package.
>
> Regards,
> Mike Swingler
> Java Engineering
> Apple Inc.
>
Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Posted by Bill Janssen <ja...@parc.com>.
Andi Vajda <va...@apache.org> wrote:
> Yes, two things made me do this:
> 1. Bill Janssen said on this list that an Apple developer he talked to
> said that the /Developer tree is the correct one to use.
I asked again, and got this answer. Looks like I was (wrong? talking
about a pre-release version of Snow Leopard?); Mike says to just use
/System/Library/Frameworks/JavaVM.framework/Headers, and explains why
that doesn't always work, and that they're aware of the problem.
So let's just hardcode that path into the setup.py file for "darwin".
Bill
Subject: Re: how to locate an installed JDK?
From: Mike Swingler <sw...@apple.com>
Date: Wed, 8 Dec 2010 07:13:59 PST
Cc: java-dev <ja...@lists.apple.com>
On Dec 7, 2010, at 7:08 PM, Bill Janssen wrote:
> Now that we have /usr/libexec/java_home, is there a standard way to
> locate a JDK, with tools like "javac" and "jar" and header files like
> "jni.h"?
>
> The PyLucene project installs a tool called "JCC", which wraps a jar
> file as a Python module, but to build JCC, it has to find a Java JDK
> with header files. Is there a standard way of doing that yet?
To find a $JAVA_HOME for the purposes of using the command line tools,
please use /usr/libexec/java_home. The man page for "java_home"
enumerates all of it's options.
As for headers, always use /System/Library/Frameworks/JavaVM.framework/Headers.
It may be necessary to install the "Java for Mac OS X 10.6 Update 3
Developer Package" or "Java for Mac OS X 10.5 Update 8 Developer
Package" from <http://connect.apple.com> under the "Java" section, to
ensure the native headers are present in the JavaVM.framework. We are
aware that this has caused some inconvenience for otherwise native
projects that make use of the JNI API, and we are leaning towards just
shipping the headers in the regular customer software update package.
Regards,
Mike Swingler
Java Engineering
Apple Inc.
Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Posted by Bill Janssen <ja...@parc.com>.
Andi Vajda <va...@apache.org> wrote:
> On Tue, 7 Dec 2010, Bill Janssen wrote:
>
> > Here's a patch to jcc/setup.py. With this it builds on both my 10.6 and
> > my 10.5 systems.
> >
> > Bill
> >
> > diff -u pylucene-3.0.3-1/jcc/setup.py.orig pylucene-3.0.3-1/jcc/setup.py
> > --- pylucene-3.0.3-1/jcc/setup.py.orig 2010-12-07 18:50:25.000000000 -0800
> > +++ pylucene-3.0.3-1/jcc/setup.py 2010-12-07 19:02:44.000000000 -0800
> > @@ -43,8 +43,23 @@
> > else:
> > JAVAHOME = None
> >
> > +if platform in ("darwin"):
> > + # possibly we shouldn't overwrite the platform module in the first place
> > + import platform as _platform
> > + import re
> > + JAVAHOME = None
> > + path = ("/Developer/SDKs/MacOSX" +
> > + re.match("[0-9]+\.[0-9]+", _platform.mac_ver()[0]).group(0) +
> > + ".sdk/System/Library/Frameworks/JavaVM.framework/Versions/Current")
> > + if os.path.exists(path):
> > + JAVAHOME = path
> > + else:
> > + path = "/System/Library/Frameworks/JavaVM.framework/Versions/Current"
> > + if os.path.isdir(path) and os.path.exists(os.path.join(path, "Headers", "jni.h")):
> > + JAVAHOME = path
> > +
> > JDK = {
> > - 'darwin': '/Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/JavaVM.framework/Versions/Current',
> > + 'darwin': JAVAHOME,
> > 'ipod': '/usr/include/gcc',
> > 'linux2': '/usr/lib/jvm/java-6-openjdk',
> > 'sunos5': '/usr/jdk/instances/jdk1.6.0',
>
> With this patch, it's going to pick the 10.5 SDK on my system. I have
> apparently both installed under /Developer/SDKs. It'd be nice if it
> picked the latest one.
It tries to pick the one that matches your OS. If you're running 10.5,
it should pick that -- it did on my system.
Bill
Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Posted by Andi Vajda <va...@apache.org>.
On Tue, 7 Dec 2010, Bill Janssen wrote:
> Here's a patch to jcc/setup.py. With this it builds on both my 10.6 and
> my 10.5 systems.
>
> Bill
>
> diff -u pylucene-3.0.3-1/jcc/setup.py.orig pylucene-3.0.3-1/jcc/setup.py
> --- pylucene-3.0.3-1/jcc/setup.py.orig 2010-12-07 18:50:25.000000000 -0800
> +++ pylucene-3.0.3-1/jcc/setup.py 2010-12-07 19:02:44.000000000 -0800
> @@ -43,8 +43,23 @@
> else:
> JAVAHOME = None
>
> +if platform in ("darwin"):
> + # possibly we shouldn't overwrite the platform module in the first place
> + import platform as _platform
> + import re
> + JAVAHOME = None
> + path = ("/Developer/SDKs/MacOSX" +
> + re.match("[0-9]+\.[0-9]+", _platform.mac_ver()[0]).group(0) +
> + ".sdk/System/Library/Frameworks/JavaVM.framework/Versions/Current")
> + if os.path.exists(path):
> + JAVAHOME = path
> + else:
> + path = "/System/Library/Frameworks/JavaVM.framework/Versions/Current"
> + if os.path.isdir(path) and os.path.exists(os.path.join(path, "Headers", "jni.h")):
> + JAVAHOME = path
> +
> JDK = {
> - 'darwin': '/Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/JavaVM.framework/Versions/Current',
> + 'darwin': JAVAHOME,
> 'ipod': '/usr/include/gcc',
> 'linux2': '/usr/lib/jvm/java-6-openjdk',
> 'sunos5': '/usr/jdk/instances/jdk1.6.0',
With this patch, it's going to pick the 10.5 SDK on my system. I have
apparently both installed under /Developer/SDKs. It'd be nice if it picked
the latest one.
Andi..
Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Posted by Bill Janssen <ja...@parc.com>.
Here's a patch to jcc/setup.py. With this it builds on both my 10.6 and
my 10.5 systems.
Bill
diff -u pylucene-3.0.3-1/jcc/setup.py.orig pylucene-3.0.3-1/jcc/setup.py
--- pylucene-3.0.3-1/jcc/setup.py.orig 2010-12-07 18:50:25.000000000 -0800
+++ pylucene-3.0.3-1/jcc/setup.py 2010-12-07 19:02:44.000000000 -0800
@@ -43,8 +43,23 @@
else:
JAVAHOME = None
+if platform in ("darwin"):
+ # possibly we shouldn't overwrite the platform module in the first place
+ import platform as _platform
+ import re
+ JAVAHOME = None
+ path = ("/Developer/SDKs/MacOSX" +
+ re.match("[0-9]+\.[0-9]+", _platform.mac_ver()[0]).group(0) +
+ ".sdk/System/Library/Frameworks/JavaVM.framework/Versions/Current")
+ if os.path.exists(path):
+ JAVAHOME = path
+ else:
+ path = "/System/Library/Frameworks/JavaVM.framework/Versions/Current"
+ if os.path.isdir(path) and os.path.exists(os.path.join(path, "Headers", "jni.h")):
+ JAVAHOME = path
+
JDK = {
- 'darwin': '/Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/JavaVM.framework/Versions/Current',
+ 'darwin': JAVAHOME,
'ipod': '/usr/include/gcc',
'linux2': '/usr/lib/jvm/java-6-openjdk',
'sunos5': '/usr/jdk/instances/jdk1.6.0',
Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Posted by Bill Janssen <ja...@parc.com>.
Andi Vajda <va...@apache.org> wrote:
> Yes, two things made me do this:
> 1. Bill Janssen said on this list that an Apple developer he talked to
> said that the /Developer tree is the correct one to use.
On a 10.6 system. Adil is talking about a 10.5 system, which will
(obviously?) not have a MacOSX10.6.sdk directory on it.
I don't think there is, any longer, a reliable way to specify a JDK on
an OS X system. We need a script like the one for Windows.
Bill
Re: [VOTE] Release PyLucene 2.9.4-1 and 3.0.3-1
Posted by Andi Vajda <va...@apache.org>.
Hi Adil,
On Tue, 7 Dec 2010, Adil Lotia wrote:
> I downloaded the release candidate from your staging area, and will be
> running pylucene on OS X.
> I am not sure if this is intentional, but was there a reason for this
> specific change?
>
> adil:681 lucene $ diff pylucene-3.0.2-1/jcc/setup.py
> pylucene-3.0.3-1/jcc/setup.py
> ...
> 47c47
> < 'darwin':
> '/System/Library/Frameworks/JavaVM.framework/Versions/Current',
> ---
>> 'darwin':
> '/Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/JavaVM.framework/Versions/Current',
> ...
>
> I have the standard JDK installation, which is in /System.
Yes, two things made me do this:
1. Bill Janssen said on this list that an Apple developer he talked to
said that the /Developer tree is the correct one to use.
2. After the last Java update on Mac OS X 10.6.x, the header files
disappeared from the Java framework tree under /System, so I switched
to the tree under /Developer.
Andi..
>
> Also, this is my system config:
> adil:689 lucene $ /usr/bin/sw_vers
> ProductName: Mac OS X
> ProductVersion: 10.5.8
> BuildVersion: 9L31a
>
> adil:690 lucene $ python -V
> Python 2.6.6
>
> adil:691 lucene $ java -version
> java version "1.5.0_26"
> Java(TM) 2 Runtime Environment, Standard Edition (build
> 1.5.0_26-b03-376-9M3263)
> Java HotSpot(TM) Client VM (build 1.5.0_26-156, mixed mode, sharing)
> adil:692 lucene
>
> And for both pylucene-3.0.3-1 (rc) and pylucene-3.0.2-1 when I run the make
> tests, most of the tests run fine, but a couple of them crash Python.
> ...
> /opt/local/bin/python test/test_PhraseQuery.py
> ........
> ----------------------------------------------------------------------
> Ran 8 tests in 0.162s
>
> OK
> /opt/local/bin/python test/test_PositionIncrement.py
> Invalid memory access of location 0x0 eip=0x240ba3b
> make: *** [test] Error 1
>
> I have tested this on three of our 10.5 systems, and it is reproduceable on
> all. (The unit tests complete okay on 10.6). I have tried switching to Java
> 6 and/or Python 2.7, and I still get the same behaviour. This crash is not
> a show-stopper for us. Pylucene is working fine for what we need.
>
> Cheers,
> -Adil
>
> On Sat, Dec 4, 2010 at 10:50 PM, Andi Vajda <va...@apache.org> wrote:
>
>>
>> With the recent releases of Lucene Java 2.9.4 and 3.0.3, the PyLucene
>> 2.9.4-1 and 3.0.3-1 releases closely tracking them are ready.
>>
>> Release candidates are 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_2_9/CHANGES
>>
>> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_0/CHANGES
>>
>> All versions of PyLucene are built with the same version of JCC, currently
>> version 2.7, included in these release artifacts.
>>
>> A list of Lucene Java changes can be seen at:
>> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/CHANGES.txt
>> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_3_0/CHANGES.txt
>>
>> Please vote to release these artifacts as PyLucene 2.9.4-1 and 3.0.3-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 2.9.4-1 and 3.0.3-1
Posted by Adil Lotia <ad...@gmail.com>.
Hi Andi
I downloaded the release candidate from your staging area, and will be
running pylucene on OS X.
I am not sure if this is intentional, but was there a reason for this
specific change?
adil:681 lucene $ diff pylucene-3.0.2-1/jcc/setup.py
pylucene-3.0.3-1/jcc/setup.py
...
47c47
< 'darwin':
'/System/Library/Frameworks/JavaVM.framework/Versions/Current',
---
> 'darwin':
'/Developer/SDKs/MacOSX10.6.sdk/System/Library/Frameworks/JavaVM.framework/Versions/Current',
...
I have the standard JDK installation, which is in /System.
Also, this is my system config:
adil:689 lucene $ /usr/bin/sw_vers
ProductName: Mac OS X
ProductVersion: 10.5.8
BuildVersion: 9L31a
adil:690 lucene $ python -V
Python 2.6.6
adil:691 lucene $ java -version
java version "1.5.0_26"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_26-b03-376-9M3263)
Java HotSpot(TM) Client VM (build 1.5.0_26-156, mixed mode, sharing)
adil:692 lucene
And for both pylucene-3.0.3-1 (rc) and pylucene-3.0.2-1 when I run the make
tests, most of the tests run fine, but a couple of them crash Python.
...
/opt/local/bin/python test/test_PhraseQuery.py
........
----------------------------------------------------------------------
Ran 8 tests in 0.162s
OK
/opt/local/bin/python test/test_PositionIncrement.py
Invalid memory access of location 0x0 eip=0x240ba3b
make: *** [test] Error 1
I have tested this on three of our 10.5 systems, and it is reproduceable on
all. (The unit tests complete okay on 10.6). I have tried switching to Java
6 and/or Python 2.7, and I still get the same behaviour. This crash is not
a show-stopper for us. Pylucene is working fine for what we need.
Cheers,
-Adil
On Sat, Dec 4, 2010 at 10:50 PM, Andi Vajda <va...@apache.org> wrote:
>
> With the recent releases of Lucene Java 2.9.4 and 3.0.3, the PyLucene
> 2.9.4-1 and 3.0.3-1 releases closely tracking them are ready.
>
> Release candidates are 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_2_9/CHANGES
>
> http://svn.apache.org/repos/asf/lucene/pylucene/branches/pylucene_3_0/CHANGES
>
> All versions of PyLucene are built with the same version of JCC, currently
> version 2.7, included in these release artifacts.
>
> A list of Lucene Java changes can be seen at:
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_2_9/CHANGES.txt
> http://svn.apache.org/repos/asf/lucene/java/branches/lucene_3_0/CHANGES.txt
>
> Please vote to release these artifacts as PyLucene 2.9.4-1 and 3.0.3-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
>