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
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
On Monday 20 March 2017, Andi Vajda wrote:
> > On Mar 20, 2017, at 05:16, Ruediger Meier <sweet_...@gmx.de> wrote:
> >> On Monday 20 March 2017, Andi Vajda wrote:
> >>
> >> On Mon, 20 Mar 2017, Ruediger Meier wrote:
> >>>> Someone with access
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
On Friday 17 March 2017, Andi Vajda wrote:
> Now, several people, including yourself, have proposed
> python 3 ports. I still have to figure a way to package this all up
> into a release that works with both. I need some time to integrate
> the three python 3 ports,
FYI I have the other two ports
On Thursday 16 March 2017, Andi Vajda wrote:
> Indeed, this is a bug of mine.
> What would you prefer:
>- include the actual .jar files in the distribution archive (tell
> tar to follow the symlinks when I build the PyLucene distribution) -
> or exclude the symlinks (tell tar to exclude
Hi,
I did some work to port jcc to python3, see
https://github.com/rudimeier/jcc
There are two interesting branches, py2 and py3
py2 should still work for python2 >=2.7 without any behavior change
py3 completes experimental python3 support (but still python2
incompatible).
