On Fri, 6 Jan 2017, Andi Vajda wrote:
On Fri, 6 Jan 2017, Jan HC8ydahl wrote:
Hi,
I hope you didn?t get this wrong! We all appreciate the existence of
JCC/PyLucene and especially all the effort you?ve put into this.
PyLucene is driven by its own community, and user involvement and
contr
> On Jan 12, 2017, at 03:47, Jan Høydahl wrote:
>
>
>>> The (sub)project will survive only to the extent that its current users
>>> invest in it.
>> so is this different to how the main (Java)Lucene project works? just
>> curious …
>
> This is the case for all ASF projects and sub projects.
> On Jan 12, 2017, at 02:22, Thomas Koch wrote:
>
> Dear Jan,
> thanks for your explanations.
>
>> PyLucene is driven by its own community, and user involvement and
>> contributions is a must.
> I’m quite familiar with community contributions - have already submitted code
> and feedback, tes
>> The (sub)project will survive only to the extent that its current users
>> invest in it.
> so is this different to how the main (Java)Lucene project works? just curious
> …
This is the case for all ASF projects and sub projects. If a project is unable
to produce
new releases, usually due to
Dear Andi,
many thanks for your review of the patch and helpful comments.
As mentioned in my previous mail to the list I’m afraid to let you know that we
currently cannot put more effort into this task. This may change in the future
of course.
However, with „funding“ my idea was to look for op
Dear Jan,
thanks for your explanations.
> PyLucene is driven by its own community, and user involvement and
> contributions is a must.
I’m quite familiar with community contributions - have already submitted code
and feedback, tested Pylucene releases, did provide support to other users and
vo
Dear Petrus,
thanks for your feedback - good to know that it’s useful for you application.
And at least one more user who asks for Python3 Support in JCC ,-)
best regards,
Thomas
—
> Am 11.01.2017 um 23:14 schrieb Petrus Hyvönen :
>
> Dear Thomas,
>
> Thanks for the patch files, I am not usin
On Fri, 6 Jan 2017, Jan Høydahl wrote:
Hi,
I hope you didn?t get this wrong! We all appreciate the existence of
JCC/PyLucene and especially all the effort you?ve put into this.
PyLucene is driven by its own community, and user involvement and contributions
is a must.
The (sub)project will
Hi Thomas,
On Fri, 6 Jan 2017, Thomas Koch wrote:
I?ve just sent the link to the public gist with the patch to Petrus and
this list. As mentioned by Oliver we?d be more than happy if a core
developer of JCC/PyLucene could review the patch and decide what to do
with it. It has been developed
Hi,
> I hope you didn’t get this wrong! We all appreciate the existence of
> JCC/PyLucene and especially all the effort you’ve put into this.
PyLucene is driven by its own community, and user involvement and contributions
is a must.
The (sub)project will survive only to the extent that its c
Dear Andi,
I’ve just sent the link to the public gist with the patch to Petrus and this
list. As mentioned by Oliver we’d be more than happy if a core developer of
JCC/PyLucene could review the patch and decide what to do with it. It has been
developed without intimate knowledge of JCC with the
> Am 04.01.2017 um 10:59 schrieb Petrus Hyvönen :
>
> Dear Thomas,
>
> I would be very interested in a python 3 port of JCC. I am not a very skilled
> developer, looked at starting a development based on the old python-3 version
> but it's beyond my current skills.
>
> I would be happy to hel
> On Jan 5, 2017, at 08:57, marco turchi wrote:
>
> Done! all testes passed!
Excellent !
>
> thanks a lot!
> Marco
>
>> On Thu, Jan 5, 2017 at 5:21 PM, Andi Vajda wrote:
>>
>>
>>> On Jan 5, 2017, at 07:27, marco turchi wrote:
>>>
>>> Perfect!!!
>>>
>>> For now, I keep the version as it
Done! all testes passed!
thanks a lot!
Marco
On Thu, Jan 5, 2017 at 5:21 PM, Andi Vajda wrote:
>
> > On Jan 5, 2017, at 07:27, marco turchi wrote:
> >
> > Perfect!!!
> >
> > For now, I keep the version as it is. I'll try later to install jcc with
> > --shared flag, because I'm not sure if the
> On Jan 5, 2017, at 07:27, marco turchi wrote:
>
> Perfect!!!
>
> For now, I keep the version as it is. I'll try later to install jcc with
> --shared flag, because I'm not sure if the patch for the setuptools
> requires root access.
Your JCC install is fine. It's PyLucene that needs to be reb
Perfect!!!
For now, I keep the version as it is. I'll try later to install jcc with
--shared flag, because I'm not sure if the patch for the setuptools
requires root access.
Thanks a lot for your help!
Marco
On Thu, Jan 5, 2017 at 2:27 AM, Andi Vajda wrote:
>
> > On Jan 4, 2017, at 13:51, marc
No I didn't.
I have run the codes in sample and they work. For my project the
functionalities in the samples are enough. If necessary I can recompile jcc
with --shared. What do you suggest?
Best
Marco
Il 04 Gen 2017 19:42, "Andi Vajda" ha scritto:
> On Jan 4, 2017, at 04:24, marco turchi wr
> On Jan 4, 2017, at 04:24, marco turchi wrote:
>
> Dear Andi and Thomas,
> following your advice I have removed the Windows error.
>
> I still have this
>
> ERROR: testThroughLayerException (__main__.PythonExceptionTestCase)
>
> To answer Andi, I have printed the config.SHARED just before th
On Jan 4, 2017, at 00:13, Thomas Koch wrote:
>> NameError: global name 'WindowsError' is not defined
>> in
>> ERROR: test_FieldEnumeration (__main__.Test_PyLuceneWithFSStore)
>
>
> I've downloaded current version
>pylucene-6.2.0-src.tar.gz2016-09-18 09:04 30M
> and was able to build
Dear Andi and Thomas,
following your advice I have removed the Windows error.
I still have this
ERROR: testThroughLayerException (__main__.PythonExceptionTestCase)
To answer Andi, I have printed the config.SHARED just before the error and
the output is true, in my opinion, showing that the share
Dear Thomas,
I would be very interested in a python 3 port of JCC. I am not a very
skilled developer, looked at starting a development based on the old
python-3 version but it's beyond my current skills.
I would be happy to help and test and review the JCC patches, I think your
patches would be a
> NameError: global name 'WindowsError' is not defined
> in
> ERROR: test_FieldEnumeration (__main__.Test_PyLuceneWithFSStore)
I've downloaded current version
pylucene-6.2.0-src.tar.gz2016-09-18 09:04 30M
and was able to build JCC and PyLucene on MacOS X10.11 (64-bit, Python 2.7.10 ,
On Tue, 3 Jan 2017, marco turchi wrote:
Nope different linux kernels and python versions (2.7.11 and 2.7.12).
Btw I have also similar problem on the machine with Web access.
I suspect you don't have shared mode enabled when running tests.
The WindowsError exception is a bug that no one hits
Nope different linux kernels and python versions (2.7.11 and 2.7.12).
Btw I have also similar problem on the machine with Web access.
Best,
Marco
On Tue, Jan 3, 2017 at 10:05 PM, Andi Vajda wrote:
>
> On Tue, 3 Jan 2017, marco turchi wrote:
>
> Dear Andi,
>> following you suggestions, I have f
On Tue, 3 Jan 2017, marco turchi wrote:
Dear Andi,
following you suggestions, I have first installed pyLucene on a machine
with access to the Web and than I have copied the tree on the cluster
machine where I have installed pyLucene.
Running the make test I have the following errors:
ERROR: te
Hi
I have also run the following commands to check if I'm using the shared
option of jcc:
>>> from jcc import config
>>> config.SHARED
True
Best,
Marco
On Tue, Jan 3, 2017 at 4:01 PM, marco turchi wrote:
> Dear Andi,
> following you suggestions, I have first installed pyLucene on a machine
>
Dear Andi,
following you suggestions, I have first installed pyLucene on a machine
with access to the Web and than I have copied the tree on the cluster
machine where I have installed pyLucene.
Running the make test I have the following errors:
ERROR: testThroughLayerException (__main__.PythonExce
> On Dec 30, 2016, at 15:07, marco turchi wrote:
>
> Dear Andi,
> thanks a lot for you answers!
>
>
>> You do not need root privileges if you don't modify the system python. One
>> way to achieve that is to setup a python virtualenv first and install jcc
>> and pylucene into it instead of the
Dear Andi,
thanks a lot for you answers!
> You do not need root privileges if you don't modify the system python. One
> way to achieve that is to setup a python virtualenv first and install jcc
> and pylucene into it instead of the system python.
>
>
Do you mean to install a new version of python
> On Dec 30, 2016, at 08:47, marco turchi wrote:
>
> Dear All,
> I'm newer with PyLucene and I'm trying to instal it on my local home on a
> cluster. In this environment, I do not have root privilege,
You do not need root privileges if you don't modify the system python. One way
to achieve tha
On Mon, 4 Jul 2016, Tom Kealy Kealy wrote:
Dear Lucene-dev,
I'm having difficulty installing pylucene on mac OS X 'El Captian' 10.11.
I've checked out the jcc source code:
svn co http://svn.apache.org/repos/asf/lucene/pylucene/trunk/jcc bcc
i've got idk 1.8, and have edited the setup.py
On Thu, 23 Apr 2009, Bill Janssen wrote:
Renaming build.xml to something more obscure could be done.
Would you like to send in a patch ?
Didn't I just do that :-? No, I'll let you deal with it.
Done.
Andi..
On Apr 23, 2009, at 13:15, Bill Janssen wrote:
Andi Vajda wrote:
If Apache Forrest, which is used to produce the web site, can be
used to
generate plain text, then this should be used for sure. What I
don't want
to do is maintain two versions of the docs, even one pagers.
No, of cours
Andi Vajda wrote:
> If Apache Forrest, which is used to produce the web site, can be used to
> generate plain text, then this should be used for sure. What I don't want
> to do is maintain two versions of the docs, even one pagers.
No, of course not. That's why I use ReST for the UpLib docs.
On Thu, 23 Apr 2009, Bill Janssen wrote:
I've just tried installing 2.4.1, and I've got a few suggestions for
packaging.
1. Put a plain-text version of readme.html in README, automatically
generated from readme.html (or whatever), as part of the src-dist
build process. I always hate it wh
35 matches
Mail list logo
