Nate Jensen

It looks like maybe numpy wasn't built correctly. Does it import ok in a regular Python interpreter?

This ticket is in limbo until someone can solve the memory freeing issues described by @bsteffensmeier.

We have nothing to do with conda or conda-forge and don't know how it works.

Interesting, looks like it doesn't like the static assert line in jep_platform.h. https://github.com/ninia/jep/blob/v4.0.3/src/main/c/Include/jep_platform.h#L38 I don't understand why.

I don't think we want to add `hasAttr` to Jep's Java PyObject since the Python data model does not have a `__hasattr__` method. https://docs.python.org/3/reference/datamodel.html#customizing-attribute-access

It's certainly something we should solve, it's just not a priority. It was a small feat to get the build working as well as it does today, and getting wheels...

In short, you think that we should release a wheel for Python 2.7 and latest Python (currently 3.5), without numpy support, 64-bit only, latest Jep only, for each of the...

A couple of thoughts: I had been avoiding depending on setuptools since it didn't come with the standard library, even though most Python packages require it. I was trying to...

I did not intend to discourage the idea of wheels if I came across that way. Further thoughts: 1. I think we should drop numpy support for the wheels. Keep...

Interestingly enough, I encountered this on Linux too, so it is not limited to Windows. The problem is that Java 8 type inference is smarter than Java 7 type inference,...