Re: AW: release votes
On Thu, Apr 24, 2014 at 2:40 PM, Andi Vajda va...@apache.org wrote: I agree with you that making releases is important. However, when votes are called to actually make them, it's been hard to get voters to respond. Anyone can vote. Anyone with an interest should vote. Three PMC votes are required to make a release happen, though. But any vote for or against is important, PMC or not. Lately, it's been hard to get the TWO extra PMC votes needed to make a release happen (since mine is cast when I cut the release candidate). I think this is in part _because_ no one else is showing an interest in the release and casting a vote either. I don't think thats necessarily the case, for me (as someone who tries to vote for pylucene releases), the problem was a combination of two things, as I did try to actually test it over the weekend: 1. being on travel, meaning stuck with a mac os X computer. 2. release candidate not compiling on my mac os X computer, because something tries to apply -mno-fused-madd when compiling, apparently this is a common issue with python and mavericks? Two things that may have nothing to do with pylucene, but was pretty annoying specially for a non-python developer :) I am happy to try it on my linux machine tonight!
Re: [VOTE] Release PyLucene 4.3.0-1
+1 On Mon, May 6, 2013 at 8:27 PM, Andi Vajda va...@apache.org wrote: It looks like the time has finally come for a PyLucene 4.x release ! The PyLucene 4.3.0-1 release tracking the recent release of Apache Lucene 4.3.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_4_3/CHANGES PyLucene 4.3.0 is built with JCC 2.16 included in these release artifacts: http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc/CHANGES A list of Lucene Java changes can be seen at: http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_4_3_0/lucene/CHANGES.txt Please vote to release these artifacts as PyLucene 4.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
s/ivy-fail/ivy-availability-check/ in Makefile?
I think ivy-fail target will always fail, causing this to always download ivy. On the other hand ivy-availability-check will conditionally call ivy-fail only if its unavailable.
Re: FacetExample.py
On Tue, Feb 12, 2013 at 3:11 AM, Andi Vajda va...@apache.org wrote: I then found that the test case from hell, TestSort.java, has majorly changed again and test_Sort.py needs to be ported again. Sigh. Andi.. I'm not laughing at your expense Andi... but this made me laugh out loud multiple times today. I've done battle with this thing several times, I feel like I always lose!
Re: FacetExample.py
On Wed, Feb 13, 2013 at 7:54 PM, Andi Vajda va...@apache.org wrote: On Wed, 13 Feb 2013, Robert Muir wrote: On Tue, Feb 12, 2013 at 3:11 AM, Andi Vajda va...@apache.org wrote: I then found that the test case from hell, TestSort.java, has majorly changed again and test_Sort.py needs to be ported again. Sigh. Andi.. I'm not laughing at your expense Andi... but this made me laugh out loud multiple times today. I've done battle with this thing several times, I feel like I always lose! I found lines 170 - 195 particularly clever :-) Jokes aside, I did spend a bunch of time of yesterday battling with the unspelled assumptions made in the Lucene random number generation code in the Lucene test framework. In particular, it seems that it expects different threads, sometimes, to get the same random values, no ? (I'm using Python's random number generator in PyLucene). The field cache sanity checker would otherwise complain, sometimes... Andi.. in all seriousness I dont like that committers' time is wasted on this. just a day or two ago I created a bug in this thing merging, and mike spent time tracking it down. I'd like to think i'm pretty careful about not breaking things when merging (I think i spent at least an hour merging this file alone very carefully, yet still screwed it up). so i opened https://issues.apache.org/jira/browse/LUCENE-4779 about the randomness: I think this should not be the case. if different threads try to share the same random, actually there should be an exception from the test framework saying that each thread should get its own random (eg. initialized by a long value). So lucene-java tests should not have code that does this: otherwise it really makes test failures difficult to reproduce. Unfortunately I'm not very familiar with what python does here, but I cc'ed Dawid just in case he knows off the top of his head.
tiny patch for java7 on os X
i installed java7 on my os X... with the following build patch
pylucene seems to work fine (tests pass etc).
I think java7 is just pickier about -source/-target both being set for
jcc. And the extensions should use the same explicit source/target (or
the build can hit classfile version problems).
Index: extensions.xml
===
--- extensions.xml (revision 1425975)
+++ extensions.xml (working copy)
@@ -16,7 +16,7 @@
target name=compile
mkdir dir=${classes.dir}/
-javac srcdir=java destdir=${classes.dir} classpathref=classpath /
+javac srcdir=java destdir=${classes.dir}
classpathref=classpath source=1.5 target=1.5 /
/target
target name=jar depends=compile
Index: jcc/setup.py
===
--- jcc/setup.py(revision 1425975)
+++ jcc/setup.py(working copy)
@@ -149,7 +149,7 @@
LFLAGS['linux2'] = LFLAGS['linux2/%s' %(machine)]
JAVAC = {
-'darwin': ['javac', '-target', '1.5'],
+'darwin': ['javac', '-source', '1.5', '-target', '1.5'],
'ipod': ['jikes', '-cp', '/usr/share/classpath/glibj.zip'],
'linux2': ['javac'],
'sunos5': ['javac'],
http://pastebin.com/raw.php?i=qHpMw9Na
Re: [VOTE] Release PyLucene 3.6.2
On Wed, Dec 26, 2012 at 11:14 AM, Andi Vajda va...@apache.org wrote: Very strange. Why would it go out to pypi to install unrelated packages ? Odd. Did you run just 'make' first before running 'make test' ? (my workflow). I just tried make, followed by make test, and it worked fine. So I think i must have just tried 'make test' in one shot... must be a little build thing. doesn't seem like a blocker to me, just seemed a bit odd.
Re: [VOTE] Release PyLucene 3.6.1-2
On Thu, Aug 23, 2012 at 12:21 AM, Andi Vajda va...@apache.org wrote: On Thu, 23 Aug 2012, Christian Heimes wrote: Am 21.08.2012 07:14, schrieb Andi Vajda: Please vote to release these artifacts as PyLucene 3.6.1-2. -1, sorry :) test_ICUTransformFilter.py is segfaulting on my system. I haven't been able to get a sensible stack trace yet. I'm going to recompile everything with debug infos tomorrow. I'm getting errors there too (if I build PyICU into PyLucene's install tree, otherwise these tests are not enabled). I believe the problem lies with the utr30.dat resource file. Their format requirements probably changed with the upgrade to ICU 49. Hi Andi, you are correct. these files only work with 4.8.1.1 If you are interested in working with 49 (which uses a newer format version), then you have to either regenerate yourself or if you want you can just use our files from http://svn.apache.org/repos/asf/lucene/dev/branches/branch_4x/lucene/analysis/icu/src/resources/ since Steven Rowe already upgraded our 4.x branch to 49 and regenerated them for that. Of course if you do this you will break any users using 4.8.x as well unless you include both and conditionalize it based on the version: our code/resources only support the version we ship with (not arbitrary versions of ICU), so we don't worry about that. -- lucidworks.com
Re: [VOTE] Release PyLucene 3.6.0 rc2
+1 to release. Downloaded on OS X, verified sig/md5, built jcc and pylucene and ran tests. On Mon, May 7, 2012 at 8:20 PM, Andi Vajda va...@apache.org wrote: Please vote to release these artifacts as PyLucene 3.6.0-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 -- lucidimagination.com
Re: [VOTE] Release PyLucene 3.3 (rc3)
+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] [Take 3] Release PyLucene 2.9.4-1 and 3.0.3-1
+1 On Sun, Dec 12, 2010 at 7:51 PM, Andi Vajda va...@apache.org wrote: A patch that improves the finding of jni.h on Mac OS X was integrated. It made it worth blocking this release and preparing new release artifacts. No one voted on the [Take 2] artifacts and I hope this is not inconveniencing anyone. I also hope that this is it for PyLucene 2.9.4/3.0.3 :-) So please vote to release the artifacts available from http://people.apache.org/~vajda/staging_area/ as PyLucene 2.9.4 and PyLucene 3.0.3. Here is my +1 Thanks ! Andi.. --- 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
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: Bring out SmartChineseAnalyzer in PyLucene?
On Mon, Sep 27, 2010 at 1:35 AM, Andi Vajda va...@apache.org wrote:
On Mon, 27 Sep 2010, Robert Muir wrote:
On Sun, Sep 26, 2010 at 10:05 PM, Andi Vajda va...@apache.org wrote:
Doing so causes this complaint to be emitted while building the
wrappers:
WARNING: Can not find lexical dictionary directory!
WARNING: This will cause unpredictable exceptions in your application!
WARNING: Please refer to the manual to download the dictionaries.
What's the trick to have the lexical dictionary directory found ?
A quick glance at the javadocs [1] doesn't seem to say.
Andi..
[1] http://lucene.apache.org/java/3_0_2/api/contrib-smartcn/index.html
the way this analyzer loads resources is a bit hairy. take a look at
WordDictionary.getInstance() for example.
so when this is called, it first checks, in this order:
* from inside the jar itself: resources/.../hmm/coredict.mem [this should
always succeed!]
* from the AnalyzerProfile thing, which is whats emitting the error.
try {
singleInstance.load();
} catch (IOException e) {
String wordDictRoot = AnalyzerProfile.ANALYSIS_DATA_DIR;
singleInstance.load(wordDictRoot);
So when you are building the wrappers, is it just that you are causing
java
to load this AnalyzerProfile some other way manually? because as soon as
you try to load AnalyzerProfile its going to emit these
warnings...
if pylucene is just loading this class itself (to make it accessible via
python), i think this is just harmless?
Yes, that's most likely it. JCC loads each and every public class unless
told not to to generate wrappers for it. If this AnalyzerProfile class is
not necessary from Python, it should be put on the --exclude list.
yeah i just tested, i get the same error in java if i do this:
Class.forName(org.apache.lucene.analysis.cn.smart.AnalyzerProfile);
So really we just need to clean up this analyzer some, because the data
files are packaged in the jar and i think this AnalyzerProfile stuff is not
needed and confusing.
--
Robert Muir
rcm...@gmail.com
Re: Korean analyzer in PyLucene
Hi Boris, this looks like it would be a welcome contribution to Lucene-java also... I think if we put it in Lucene-java then pylucene can use it :) if you decide to help here is a start, and I am happy to help: http://wiki.apache.org/lucene-java/HowToContribute Do you know the status of this Korean analyzer (I checked and there were recent commits as of last month)? On Tue, Jun 22, 2010 at 12:23 AM, Boris D boris@gmail.com wrote: Hi, I would like to make an additional analyzer for Korean available to pylucene (http://sourceforge.net/projects/lucenekorean/). Can someone describe the procedure to do so? Thanks in advance. -- Boris -- Robert Muir rcm...@gmail.com
