Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-30 Thread Andi Vajda
On Thu, 30 Mar 2017, Rüdiger Meier wrote: On 03/30/2017 09:05 PM, Andi Vajda wrote: On Thu, 30 Mar 2017, Petrus HyvC6nen wrote: Hi, My current diff to the svn is below (as in the chain of mails). Now i get it to wrap my library in both 2.7, 3.5 and 3.6. I believe, I've now applied all

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-30 Thread Rüdiger Meier
On 03/30/2017 09:05 PM, Andi Vajda wrote: On Thu, 30 Mar 2017, Petrus Hyvönen wrote: Hi, My current diff to the svn is below (as in the chain of mails). Now i get it to wrap my library in both 2.7, 3.5 and 3.6. I believe, I've now applied all these diffs (or equivalents). Thank you Petrus

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-30 Thread Andi Vajda
On Thu, 30 Mar 2017, Petrus Hyvönen wrote: Hi, My current diff to the svn is below (as in the chain of mails). Now i get it to wrap my library in both 2.7, 3.5 and 3.6. I believe, I've now applied all these diffs (or equivalents). Thank you Petrus for testing on Windows, I'm going to release

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-30 Thread Petrus Hyvönen
Hi, My current diff to the svn is below (as in the chain of mails). Now i get it to wrap my library in both 2.7, 3.5 and 3.6. /Regards Index: jcc2/__init__.py === --- jcc2/__init__.py (revision 1789413) +++ jcc2/__init__.py (workin

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-30 Thread Petrus Hyvönen
Hi, I was trying the python 2.7 build and I think the line 23 in jcc2/__init__.py should be: from jcc.config import SHARED (instead of from jcc2.config import..) Regards /Petrus On Thu, Mar 30, 2017 at 9:10 AM, Petrus Hyvönen wrote: > Hi, > > With this version of of t_jccenv_strhash I c

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-30 Thread Petrus Hyvönen
Hi, With this version of of t_jccenv_strhash I can build both JCC and wrap the library I'm using! Regards /Petrus > > >> static PyObject *t_jccenv_strhash(PyObject *self, PyObject *arg) >> { >>unsigned long long hash = (unsigned long long) PyObject_Hash(arg); >>static const size_t hexd

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-29 Thread Andi Vajda
On Thu, 30 Mar 2017, Ruediger Meier wrote: On Wednesday 29 March 2017, Andi Vajda wrote: On Wed, 29 Mar 2017, Petrus Hyvönen wrote: Hi, With the /DLL, sprintf(buffer, "%0*%jx", (int) hexdig, hash); and Py_SIZE it compiles under windows (Windows 7, 64 bit) I haven't set up for building pyluc

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-29 Thread Ruediger Meier
On Wednesday 29 March 2017, Andi Vajda wrote: > On Wed, 29 Mar 2017, Petrus Hyvönen wrote: > > Hi, > > > > With the /DLL, sprintf(buffer, "%0*%jx", (int) hexdig, hash); and > > Py_SIZE it compiles under windows (Windows 7, 64 bit) > > > > I haven't set up for building pylucene but has another libra

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-29 Thread Andi Vajda
On Wed, 29 Mar 2017, Petrus Hyvönen wrote: Hi, Assuming the Prixmax stuff is just some typo, if I remove that I get same error as in Ruedigers github version - MS linker error LNK1561 - missing starting point. This seems to be fixed by the /DLL directive. https://msdn.microsoft.com/en-us/lib

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-29 Thread Andi Vajda
On Wed, 29 Mar 2017, Petrus Hyvönen wrote: Hi, With the /DLL, sprintf(buffer, "%0*%jx", (int) hexdig, hash); and Py_SIZE it compiles under windows (Windows 7, 64 bit) I haven't set up for building pylucene but has another library that I build. For that I get a udf-8 error on: File "C:\User

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-29 Thread Petrus Hyvönen
Hi, With the /DLL, sprintf(buffer, "%0*%jx", (int) hexdig, hash); and Py_SIZE it compiles under windows (Windows 7, 64 bit) I haven't set up for building pylucene but has another library that I build. For that I get a udf-8 error on: File "C:\Users\phy\AppData\Local\Continuum\Anaconda3-430\co

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-29 Thread Ruediger Meier
On Wednesday 29 March 2017, Petrus Hyvönen wrote: > Hi, > > Assuming the Prixmax stuff is just some typo, if I remove that I get > same error as in Ruedigers github version - MS linker error LNK1561 - > missing starting point. This seems to be fixed by the /DLL > directive. > > https://msdn.micros

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-29 Thread Ruediger Meier
On Wednesday 29 March 2017, Petrus Hyvönen wrote: > Hi, > > Yes, there are windows users :) > > I've ran a quick test, it builds fine on python 2.7 but I'm getting > some linker error under python 3.6 and 3.5 (didn't try lower). > > The linker error states: > > jcc3/sources/jcc.cpp(202): error C368

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-29 Thread Petrus Hyvönen
Hi, Assuming the Prixmax stuff is just some typo, if I remove that I get same error as in Ruedigers github version - MS linker error LNK1561 - missing starting point. This seems to be fixed by the /DLL directive. https://msdn.microsoft.com/en-us/library/ky737ya4.aspx and fix at https://github.c

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-29 Thread Petrus Hyvönen
Hi, Yes, there are windows users :) I've ran a quick test, it builds fine on python 2.7 but I'm getting some linker error under python 3.6 and 3.5 (didn't try lower). The linker error states: jcc3/sources/jcc.cpp(202): error C3688: invalid literal suffix 'PRIxMAX'; literal operator or literal o

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-29 Thread Andi Vajda
> On Mar 29, 2017, at 13:36, Ruediger Meier wrote: > > On Wednesday 29 March 2017, Andi Vajda wrote: > >>> Regarding that release candidate. There are still one or two minor >>> issues on Linux >> >> I'm aware of the fsct that the -lpython... link line for shared mode >> on linux needs editing

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-29 Thread Ruediger Meier
On Wednesday 29 March 2017, Andi Vajda wrote: > > Regarding that release candidate. There are still one or two minor > > issues on Linux > > I'm aware of the fsct that the -lpython... link line for shared mode > on linux needs editing depending on the versions of python used. Are > there other iss

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-29 Thread Andi Vajda
> On Mar 29, 2017, at 12:11, Ruediger Meier wrote: > >> On Tuesday 28 March 2017, Andi Vajda wrote: >> The PyLucene 6.5.0 (rc1) release tracking today's release of >> Apache Lucene 6.5.0 is ready. >> >> A release candidate is available from: >> https://dist.apache.org/repos/dist/dev/lucene/py

Re: [VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-29 Thread Ruediger Meier
On Tuesday 28 March 2017, Andi Vajda wrote: > The PyLucene 6.5.0 (rc1) release tracking today's release of > Apache Lucene 6.5.0 is ready. > > A release candidate is available from: >https://dist.apache.org/repos/dist/dev/lucene/pylucene/6.5.0-rc1/ > > PyLucene 6.5.0 is built with JCC 3.0 inclu

[VOTE] Release PyLucene 6.5.0 (rc1) (now with Python 3 support)

2017-03-27 Thread Andi Vajda
The PyLucene 6.5.0 (rc1) release tracking today's release of Apache Lucene 6.5.0 is ready. A release candidate is available from: https://dist.apache.org/repos/dist/dev/lucene/pylucene/6.5.0-rc1/ PyLucene 6.5.0 is built with JCC 3.0 included in these release artifacts. JCC 3.0 now supports P