ses SystemError in Python 3.
>
>
> Key: PYLUCENE-45
> URL: https://issues.apache.org/jira/browse/PYLUCENE-45
> Project: PyLucene
> Issue Type: Bug
>Reporter: A. Coady
>
A. Coady created PYLUCENE-45:
Summary: JArray.cast_ raises SystemError in Python 3.
Key: PYLUCENE-45
URL: https://issues.apache.org/jira/browse/PYLUCENE-45
Project: PyLucene
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PYLUCENE-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Vajda resolved PYLUCENE-39.
Resolution: Fixed
fixed in rev 1812596
> JArrays are no longer sliceable under Pytho
A. Coady created PYLUCENE-39:
Summary: JArrays are no longer sliceable under Python 3.
Key: PYLUCENE-39
URL: https://issues.apache.org/jira/browse/PYLUCENE-39
Project: PyLucene
Issue Type: Bug
I am pleased to announce the availability of Apache PyLucene 6.5.0.
New in this release: Python 3 support.
PyLucene is now supported with both Python 2 and Python 3.
JCC 3.0 maintains compatibility with both Python versions.
Apache PyLucene, a subproject of Apache Lucene, is a Python extension
ports Python 3.3+ (in addition to Python 2.3+).
PyLucene may be built with Python 2 or Python 3.
Please vote to release these artifacts as PyLucene 6.5.0.
Anyone interested in this release can and should vote !
Thanks !
Andi..
ps: the KEYS file for PyLucene release signing is at:
https://dist.apach
12:27:53 -0700 (PDT)
From: Andi Vajda
To: pylucene-dev@lucene.apache.org
Cc: gene...@lucene.apache.rog
Subject: [VOTE] Release PyLucene 6.5.0 (rc2) (now with Python 3 support)
A few fixes were needed in JCC for better Windows support.
The PyLucene 6.5.0 rc1 vote is thus cancelled.
I'm now
øydahl, search solution architect
>> Cominvent AS - www.cominvent.com
>>
>>> 4. apr. 2017 kl. 20.56 skrev Andi Vajda :
>>>
>>>
>>> One more PMC vote is needed to make this release !
>>> Thanks !
>>>
>>> Andi..
>>>
>>&
te: Thu, 30 Mar 2017 12:27:53 -0700 (PDT)
>> From: Andi Vajda
>> To: pylucene-dev@lucene.apache.org
>> Cc: gene...@lucene.apache.rog
>> Subject: [VOTE] Release PyLucene 6.5.0 (rc2) (now with Python 3 support)
>>
>>
>> A few fixes were needed in JCC for
ge --
> Date: Thu, 30 Mar 2017 12:27:53 -0700 (PDT)
> From: Andi Vajda
> To: pylucene-dev@lucene.apache.org
> Cc: gene...@lucene.apache.rog
> Subject: [VOTE] Release PyLucene 6.5.0 (rc2) (now with Python 3 support)
>
>
> A few fixes were needed in JCC for better W
Python 3 support)
A few fixes were needed in JCC for better Windows support.
The PyLucene 6.5.0 rc1 vote is thus cancelled.
I'm now calling for a vote on PyLucene 6.5.0 rc2.
The PyLucene 6.5.0 (rc2) release tracking the recent release of
Apache Lucene 6.5.0 is ready.
A release candidate is avai
g/repos/dist/dev/lucene/pylucene/6.5.0-rc2/
> >
> > PyLucene 6.5.0 is built with JCC 3.0 included in these release artifacts.
> >
> > JCC 3.0 now supports Python 3.3+ (in addition to Python 2.3+).
> > PyLucene may be built with Python 2 or Python 3.
> >
> > Plea
.apache.org/repos/dist/dev/lucene/pylucene/6.5.0-rc2/
>
> PyLucene 6.5.0 is built with JCC 3.0 included in these release artifacts.
>
> JCC 3.0 now supports Python 3.3+ (in addition to Python 2.3+).
> PyLucene may be built with Python 2 or Python 3.
>
> Please vote to release t
ow supports Python 3.3+ (in addition to Python 2.3+).
> PyLucene may be built with Python 2 or Python 3.
>
> Please vote to release these artifacts as PyLucene 6.5.0.
> Anyone interested in this release can and should vote !
>
> Thanks !
>
> Andi..
>
> ps: the KEYS file for PyL
from:
https://dist.apache.org/repos/dist/dev/lucene/pylucene/6.5.0-rc2/
PyLucene 6.5.0 is built with JCC 3.0 included in these release artifacts.
JCC 3.0 now supports Python 3.3+ (in addition to Python 2.3+).
PyLucene may be built with Python 2 or Python 3.
Please vote to release these artifac
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
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
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
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
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
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
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
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
yUnicode_FromStringAndSize(buffer, hexdig);
}
I don't understand the PRIxMAX stuff there, what does it mean?
MANY thanks for working with the Python 3 port...
Regards
/Petrus
On Wed, Mar 29, 2017 at 10:43 PM, Andi Vajda wrote:
On Mar 29, 2017, at 13:36, Ruediger Meier wrote:
On Wednesd
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
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
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
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
the jcc.cpp code is:
> static PyObject *t_jccenv_strhash(PyObject *self, PyObject *arg)
> {
> static const size_t hexdig = sizeof(uintmax_t) * 2;
> uintmax_t hash = (uintmax_t) PyObject_Hash(arg);
> char buffer[hexdig + 1];
>
> sprintf(buffer, "%0*"PR
ig);
}
I don't understand the PRIxMAX stuff there, what does it mean?
MANY thanks for working with the Python 3 port...
Regards
/Petrus
On Wed, Mar 29, 2017 at 10:43 PM, Andi Vajda wrote:
>
> > On Mar 29, 2017, at 13:36, Ruediger Meier wrote:
> >
> > On Wednesday 29 M
> 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
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
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 Python 3.3+ (in addition to Python 2.3+).
>> PyLucene may be built with Python 2 or P
.5.0 is built with JCC 3.0 included in these release
> artifacts.
>
> JCC 3.0 now supports Python 3.3+ (in addition to Python 2.3+).
> PyLucene may be built with Python 2 or Python 3.
>
> Please vote to release these artifacts as PyLucene 6.5.0.
> Anyone interested in this rele
ports Python 3.3+ (in addition to Python 2.3+).
PyLucene may be built with Python 2 or Python 3.
Please vote to release these artifacts as PyLucene 6.5.0.
Anyone interested in this release can and should vote !
Thanks !
Andi..
ps: the KEYS file for PyLucene release signing is at:
ediger Meier wrote:
>>>>>> Someone with access to Windows, please help test/fix/finish
>>>>>> support for Python 3 on Windows, both with the MSVC and Mingw
>>>>>> compilers. I have no access to Windows anymore.
>>>>>
>>
to Windows, please help test/fix/finish
support for Python 3 on Windows, both with the MSVC and Mingw
compilers. I have no access to Windows anymore.
I know already about one MSVC issue:
https://github.com/rudimeier/jcc/issues/1
probably fixed by
https://github.com/rudimeier/jcc/commit
On Monday 20 March 2017, Andi Vajda wrote:
> > On Mar 20, 2017, at 05:16, Ruediger Meier wrote:
> >> On Monday 20 March 2017, Andi Vajda wrote:
> >>
> >> On Mon, 20 Mar 2017, Ruediger Meier wrote:
> >>>> Someone with access to Windows, please hel
> On Mar 20, 2017, at 05:16, Ruediger Meier wrote:
>
>> On Monday 20 March 2017, Andi Vajda wrote:
>> On Mon, 20 Mar 2017, Ruediger Meier wrote:
>
>>>> Someone with access to Windows, please help test/fix/finish
>>>> support for Python 3 on Windows
On Monday 20 March 2017, Andi Vajda wrote:
> On Mon, 20 Mar 2017, Ruediger Meier wrote:
> >> Someone with access to Windows, please help test/fix/finish
> >> support for Python 3 on Windows, both with the MSVC and Mingw
> >> compilers. I have no access to Windows a
I just now checked in support for Python 3 (3.5+), built and tested on
Mac OS X 10.12 only, with Python 3.6. Linux support should be next. I have no
access to Windows anymore and thus can't test support there.
I manually integrated/merged/changed/fixed the patches proposed by Rüdiger
Meie
> On Jun 23, 2015, at 09:02, Petrus Hyvönen wrote:
>
> Hi,
>
> Just a heads-up, I'm not a PyLucene user but a frequent user of JCC in
> another context wrapping scientific libraries in java. I would appreciate a
> Python 3 compatible JCC in the future, most
Hi,
Just a heads-up, I'm not a PyLucene user but a frequent user of JCC in
another context wrapping scientific libraries in java. I would appreciate a
Python 3 compatible JCC in the future, most libraries are now Python 3
compatible and I think in the future this will be the python standar
On Mon, 1 Jun 2015, Johan Jonkers wrote:
Hello everyone,
I was wondering if there are plans to support python 3 for PyLucene. I know
there is an experimental Python 3 version of JCC but it is from 2010 I think,
so a bit outdated. We would like to migrate from python 2.7 to 3.0 but we
need
Hello everyone,
I was wondering if there are plans to support python 3 for PyLucene. I
know there is an experimental Python 3 version of JCC but it is from
2010 I think, so a bit outdated. We would like to migrate from python
2.7 to 3.0 but we need PyLucene to work for that. Any information
45 matches
Mail list logo
