On Fri, 22 May 2009, Grant Ingersoll wrote:
+1
And here is mine: +1
This vote now has passed and the PyLucene 2.4.1-2 refresher release should
be made available shortly.
Andi..
On May 16, 2009, at 5:35 PM, Andi Vajda wrote:
Since the release of PyLucene 2.4.1-1 last month, some bugs
+1
On May 16, 2009, at 5:35 PM, Andi Vajda wrote:
Since the release of PyLucene 2.4.1-1 last month, some bugs and
annoyances were fixed that make it worth doing a refresher release
of PyLucene,
version 2.4.1-2.
Release candidate 1 of PyLucene 2.4.1-2 is available from:
http://people.
Since the release of PyLucene 2.4.1-1 last month, some bugs and annoyances
were fixed that make it worth doing a refresher release of PyLucene,
version 2.4.1-2.
Release candidate 1 of PyLucene 2.4.1-2 is available from:
http://people.apache.org/~vajda/staging_area/
The list of changes is
On Apr 1, 2009, at 13:12, Grant Ingersoll wrote:
Hey Andi,
I think you now have the necessary votes such that this has passed.
Feel free to finish out the release. If you need help on what that
is, both the Solr and Lucene wiki's have info on making releases.
Yep, I should get to this
Hey Andi,
I think you now have the necessary votes such that this has passed.
Feel free to finish out the release. If you need help on what that
is, both the Solr and Lucene wiki's have info on making releases.
Cheers,
Grant
On Mar 26, 2009, at 7:58 PM, Grant Ingersoll wrote:
+1
On Ma
I tried the install (for impatient users, nice!), and got this error
on the install of JCC:
Installed /Library/Python/2.5/site-packages/JCC-2.2-py2.5-macosx-10.5-
i386.egg
Processing dependencies for JCC==2.2
Searching for JCC==2.2
Reading http://pypi.python.org/simple/JCC/
No local packages
Ugh, forgot to CC pylucene-dev.
Mike
-- Forwarded message --
From: Michael McCandless
Date: Wed, Mar 25, 2009 at 10:40 AM
Subject: Re: [VOTE] release PyLucene 2.4.1
To: gene...@lucene.apache.org, Andi Vajda
+1 to release RC7.
I like your re-org of "For the Impatient/Re
: This is the way it used to be. In the interest of better maintenance by
: avoiding duplication and to have nicer presentation than plain text, I
: moved all the docs to the web site. That site's sources are all in svn
I'm not advocating duplication -- and i agree HTML based docs tend to be
On Tue, 24 Mar 2009, Chris Hostetter wrote:
I'm just suggesting that a "snapshot" of the HTML docs be
included future releases. (this is along the same lines as what some of
the other subprojects do)
PyLucene 2.1.4 RC7 received some documentation additions:
- a local copy of the PyLucene we
I was afraid you would say that! OK I'll work up a patch ;)
Mike
Andi Vajda wrote:
>
> On Tue, 24 Mar 2009, Michael McCandless wrote:
>
>> But don't forget the "for the impatient..." instructions ;)
>
> Oh, I thought you were going to contribute them :)
>
> Andi..
>
On Tue, 24 Mar 2009, Michael McCandless wrote:
But don't forget the "for the impatient..." instructions ;)
Oh, I thought you were going to contribute them :)
Andi..
But don't forget the "for the impatient..." instructions ;)
Mike
Andi Vajda wrote:
>
> On Tue, 24 Mar 2009, Chris Hostetter wrote:
>
>> : This is the way it used to be. In the interest of better maintenance by
>> : avoiding duplication and to have nicer presentation than plain text, I
>> : moved
On Tue, 24 Mar 2009, Chris Hostetter wrote:
: This is the way it used to be. In the interest of better maintenance by
: avoiding duplication and to have nicer presentation than plain text, I
: moved all the docs to the web site. That site's sources are all in svn
I'm not advocating duplication
On Tue, 24 Mar 2009, Chris Hostetter wrote:
: This is the way it used to be. In the interest of better maintenance by
: avoiding duplication and to have nicer presentation than plain text, I
: moved all the docs to the web site. That site's sources are all in svn
I'm not advocating duplication
On Tue, 24 Mar 2009, Chris Hostetter wrote:
My one comment is regarding the documentation: the README and INSTALL
files included in the release...
./README
./INSTALL
./jcc/README
./jcc/INSTALL
...are all simple one line files pointing people to URLs for HTML based
documentation on the website
: I uploaded RC6 with these fixes to the staging area:
: http://people.apache.org/~vajda/staging_area/
:
: Please vote to release these artifacts as PyLucene 2.4.1.
: Thanks !
+0
I attempted to review the release, but my complete lack of knowledge about
python, and my computer's aparent la
On Mon, 23 Mar 2009, Michael McCandless wrote:
I tested what happens when I fail to call initVM, and unfortunately I hit a
SEGV (different from previous Bus Error):
... snip ...
This is the code:
import lucene
#lucene.initVM(lucene.CLASSPATH)
store = lucene.FSDirectory.getDirectory('/lu
Last week's vote failed to get the 3 PMC votes to make an official release.
Only one PMC vote was cast, a +1 from Mike McCandless.
In the meantime, some bugs were fixed and PyLucene 2.4.1 RC5 was uploaded to
the staging area:
http://people.apache.org/~vajda/staging_area/
Please vote to
On Mar 12, 2009, at 16:32, Christian Heimes wrote:
Andi Vajda wrote:
That's the problem. If I change my env or edit setup.py and config.py
exists already because I already did a build, it is not going to be
re-generated if I do 'python setup.py install' even though it should
since 'install' c
Andi Vajda wrote:
> That's the problem. If I change my env or edit setup.py and config.py
> exists already because I already did a build, it is not going to be
> re-generated if I do 'python setup.py install' even though it should
> since 'install' calls 'build' (and people expect it to) yet 'build
On Mar 12, 2009, at 13:10, Christian Heimes wrote:
Andi Vajda wrote:
if not os.path.exists(self.jcc_config_file):
create_config = 1
else:
create_config = 0
for command in self.distribution.commands:
if command.startswith(("build", "bdist")):
create_config = 1
break
if crea
On Mar 12, 2009, at 13:07, Michael McCandless
wrote:
Michael McCandless wrote:
A OK; this is quite confusing.
Everyone seems to find it so. I advise Mac users at PARC to just
use
the system Python (unless and until they really know what they are
doing).
I will now do the same
Bill Janssen wrote:
Michael McCandless wrote:
Michael McCandless wrote:
A OK; this is quite confusing.
Everyone seems to find it so. I advise Mac users at PARC to just
use
the system Python (unless and until they really know what they are
doing).
I will now do the same to all M
Michael McCandless wrote:
> Michael McCandless wrote:
>
> >>> A OK; this is quite confusing.
> >>
> >> Everyone seems to find it so. I advise Mac users at PARC to just use
> >> the system Python (unless and until they really know what they are
> >> doing).
> >
> > I will now do the same to
jcc/jcc/config.py? Indeed it reflects my addition of -F/System/...,
with this:
LFLAGS=['-framework', 'JavaVM', '-F/System/Library/Frameworks', '-
framework', 'Python']
But, weirdly, I don't then see that in the final linking step when
running "make" in the pylucene dir. Here's the
Michael McCandless wrote:
> Weird, that was not what I was seeing.
>
> I think I cd'd to jcc, added -F into setup.py, "rm -r build", python
> (coming from the right framework) setup.py build (confirmed -F worked),
> sudo python setup.py install, cd .., make clean, make, and I didn't see
> the -F f
Andi Vajda wrote:
On Mar 12, 2009, at 12:40, Michael McCandless > wrote:
Andi Vajda wrote:
On Thu, 12 Mar 2009, Michael McCandless wrote:
Anyway, finally, a little bruised from the whole process, and
wondering what other Python things on my Mac may now be broken... I
was able to run t
Andi Vajda wrote:
>> if not os.path.exists(self.jcc_config_file):
>>create_config = 1
>> else:
>>create_config = 0
>>
>> for command in self.distribution.commands:
>>if command.startswith(("build", "bdist")):
>>create_config = 1
>>break
>>
>> if create_config:
>>self
Michael McCandless wrote:
A OK; this is quite confusing.
Everyone seems to find it so. I advise Mac users at PARC to just use
the system Python (unless and until they really know what they are
doing).
I will now do the same to all Mac+Python people I know & meet ;)
Though...
It'd be
On Mar 12, 2009, at 12:40, Michael McCandless
wrote:
Andi Vajda wrote:
On Thu, 12 Mar 2009, Michael McCandless wrote:
Anyway, finally, a little bruised from the whole process, and
wondering what other Python things on my Mac may now be broken... I
was able to run the tests successfull
Bill Janssen wrote:
Michael McCandless wrote:
Bill Janssen wrote:
Michael McCandless wrote:
But why do I have two separate 2.5 Python installs, compiled w/
different options, in the first place? It's weird and I'd like to
fix
it, I think (outside of building PyLucene, for my own sanity
Michael McCandless wrote:
> Bill Janssen wrote:
>
> > Michael McCandless wrote:
> >
> >> But why do I have two separate 2.5 Python installs, compiled w/
> >> different options, in the first place? It's weird and I'd like to
> >> fix
> >> it, I think (outside of building PyLucene, for my own sa
Andi Vajda wrote:
On Thu, 12 Mar 2009, Michael McCandless wrote:
Anyway, finally, a little bruised from the whole process, and
wondering what other Python things on my Mac may now be broken... I
was able to run the tests successfully!
Do not pollute your env with soft links. Use -F instead
Bill Janssen wrote:
Michael McCandless wrote:
But why do I have two separate 2.5 Python installs, compiled w/
different options, in the first place? It's weird and I'd like to
fix
it, I think (outside of building PyLucene, for my own sanity).
One (the one in /Library) is the Python.org
Michael McCandless wrote:
> But why do I have two separate 2.5 Python installs, compiled w/
> different options, in the first place? It's weird and I'd like to fix
> it, I think (outside of building PyLucene, for my own sanity).
One (the one in /Library) is the Python.org install, which I avoid
Andi Vajda wrote:
On Thu, 12 Mar 2009, Michael McCandless wrote:
Anyway, finally, a little bruised from the whole process, and
wondering what other Python things on my Mac may now be broken... I
was able to run the tests successfully!
Do not pollute your env with soft links. Use -F instead
On Thu, 12 Mar 2009, Michael McCandless wrote:
Anyway, finally, a little bruised from the whole process, and
wondering what other Python things on my Mac may now be broken... I
was able to run the tests successfully!
Do not pollute your env with soft links. Use -F instead. Really.
Maybe it'
On Thu, 12 Mar 2009, Michael McCandless wrote:
OK I was able to finally build (OS X 10.5.6) and run all tests
successfully.
I hit a few OS X issues that I think are my silliness/confused
environment. I'll try to document them here, for future Google
diggers, but note that I sort of desperatel
Anyway, finally, a little bruised from the whole process, and
wondering what other Python things on my Mac may now be broken... I
was able to run the tests successfully!
Maybe it's ambitious... but I'd really love a "for the impatient...",
in INSTALL, like this:
pushd jcc
python setup.py
OK I was able to finally build (OS X 10.5.6) and run all tests
successfully.
I hit a few OS X issues that I think are my silliness/confused
environment. I'll try to document them here, for future Google
diggers, but note that I sort of desperately rushed though things
trying to get it to work s
On Thu, 12 Mar 2009, Christian Heimes wrote:
Andi Vajda wrote:
In other words, you're fixing this with this patch by introducing
another such inconvenience, both with a silent failure. It doesn't look
like the trade off is worthwhile.
This is not saying anything about the quality or clevernes
Andi Vajda wrote:
> In other words, you're fixing this with this patch by introducing
> another such inconvenience, both with a silent failure. It doesn't look
> like the trade off is worthwhile.
>
> This is not saying anything about the quality or cleverness of the patch
> itself. It taught me so
On Thu, 12 Mar 2009, Christian Heimes wrote:
I've attached a patch that hooks into the build process. With the patch
the config file is created right before the .py files are copied into
the build directory.
Thanks for the patch. A few comments:
def run(self):
if (not os.path.ex
Christian Heimes wrote:
[...]
I forgot to include the changes in jcc/python.py. You have to rename
SHARED to ENABLE_SHARED.
Christian
Andi Vajda wrote:
> Does 'install' without 'build' invoke 'build' ?
> If that's the case, then yeah, there is a problem and this should be
> backed out. If not, then where is the problem ? 'install' without a
> prior 'build' would make no sense, no ?
Yes, it does. Every step in the installation pr
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 t
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.
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 i
On Wed, 11 Mar 2009, Christian Heimes wrote:
Andi Vajda wrote:
Fixed. config.py is not written when 'build' is not in the command line
args anymore. I uploaded a new release candidate, rc2, to
http://people.apache.org/~vajda/staging_area.
Thank you for the bug report.
Your solution breaks a
Andi Vajda wrote:
> Fixed. config.py is not written when 'build' is not in the command line
> args anymore. I uploaded a new release candidate, rc2, to
> http://people.apache.org/~vajda/staging_area.
>
> Thank you for the bug report.
Your solution breaks an installation when a user doesn't call "
On Wed, 11 Mar 2009, Andi Vajda wrote:
Could you stop setup.py from overwriting config.py when the file already
exists and "install" is used as distutils command?
Not when the file already exists since that would prevent changes to setup.py
from being reflected in config.py but it shouldn't
On Wed, 11 Mar 2009, Christian Heimes wrote:
Andi Vajda schrieb:
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.
Release candidate 1 of PyLucene
Andi Vajda schrieb:
>
> 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.
>
> Release candidate 1 of PyLucene 2.4.1 is available from:
>
> http
On Wed, 11 Mar 2009, Grant Ingersoll wrote:
1. I think you need to upload your Key to a public server (i.e.
pgp.mit.edu)
How do I do that ?
http://pgp.mit.edu:11371/ There's a place to submit a key there.
Done.
Andi..
On Mar 11, 2009, at 2:48 PM, Andi Vajda wrote:
On Wed, 11 Mar 2009, Grant Ingersoll wrote:
First off, I'm a total Python newbie, so bear with me...
Couple of comments:
1. I think you need to upload your Key to a public server (i.e.
pgp.mit.edu)
How do I do that ?
http://pgp.mit.edu:1
On Wed, 11 Mar 2009, Grant Ingersoll wrote:
First off, I'm a total Python newbie, so bear with me...
Couple of comments:
1. I think you need to upload your Key to a public server (i.e. pgp.mit.edu)
How do I do that ?
Alternatively, it seems that you can import my key from the KEYS file in t
Hi Andi,
First off, I'm a total Python newbie, so bear with me...
Couple of comments:
1. I think you need to upload your Key to a public server (i.e.
pgp.mit.edu)
See:
@molly[1003]$ gpg --verify pylucene-2.4.1-rc1-src.tar.gz.asc
gpg: Signature made Wed Mar 11 12:42:58 2009 EDT using DSA key
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.
Release candidate 1 of PyLucene 2.4.1 is available from:
http://people.apache.org/~vajda/stag
58 matches
Mail list logo
