Andi, one small thing: when you upload a new RC, you should remove the
old ones just to reduce chances for confusion...
Mike
Andi Vajda wrote:
On Wed, 11 Mar 2009, Aric Coady wrote:
On Mar 11, 2009, at 10:06 AM, Andi Vajda wrote:
With the recent release of Java Lucene 2.4.1, it's high time
PyLucene get its first release out as an Apache subproject. I hope
I got all the steps right and all the things into the right place.
Thanks.
Release candidate 1 of PyLucene 2.4.1 is available from:
http://people.apache.org/~vajda/staging_area/
Make install is failing with python 2.6 because of a conflict
between the new collections module and the builtin one.
Ugh. I moved the collections.py file to a python sub-directory.
This is only a problem during the build. The collections.py file is
installed into the lucene egg where it is accessible from under the
lucene package then.
I also backed out the earlier config.py build trick as it fails when
install is used without build first.
I uploaded a new release candidate, rc3, to the staging area:
http://people.apache.org/~vajda/staging_area/
Thank you for the bug report.
Andi..
...
File "/Library/Frameworks/Python.framework/Versions/2.6/lib/
python2.6/site-packages/setuptools-0.6c9-py2.6.egg/setuptools/
command/easy_install.py", line 21, in <module>
File "/Library/Frameworks/Python.framework/Versions/2.6/lib/
python2.6/site-packages/setuptools-0.6c9-py2.6.egg/setuptools/
package_index.py", line 2, in <module>
File "/Library/Frameworks/Python.framework/Versions/2.6/lib/
python2.6/urlparse.py", line 84, in <module>
from collections import namedtuple
ImportError: cannot import name namedtuple
make: *** [install] Error 255
Probably will be necessary to rename or move collections.py.
-Coady
