trackpy does not seem to be compatible with v0.12 of numba about trackpy HOT 3 CLOSED

Agreed. I'll have a look.

nathan

On Feb 10, 2014, at 7:45 PM, Dan Allan [email protected] wrote:

See this failed Travis job. For now I am forcing the Travis build to use 0.11, which is the version I have been developing on.

Can I pass this off to you, @nkeim ? If it comes down to Travis problems feel free to tap me in. For now I'm guessing this is an actual problem with numba 0.12 that one can reproduce locally with the latest version of conda.

—
Reply to this email directly or view it on GitHub.

from trackpy.

If I had to guess, I'd say that the future numba 0.13 won't break things — 0.12 has some pretty big internal changes. So we should either go back to testing against the latest release, or test against both 0.11 and the latest.

I'm inclined to be pretty forgiving about users who wait 1 year or even more before updating Python. In fact, maybe we should always test against the previous entire release of miniconda, as well as the latest. Thoughts?

nathan

On Feb 10, 2014, at 7:45 PM, Dan Allan [email protected] wrote:

See this failed Travis job. For now I am forcing the Travis build to use 0.11, which is the version I have been developing on.

Can I pass this off to you, @nkeim ? If it comes down to Travis problems feel free to tap me in. For now I'm guessing this is an actual problem with numba 0.12 that one can reproduce locally with the latest version of conda.

—
Reply to this email directly or view it on GitHub.

from trackpy.

Yeah, that sounds fine. It's way too soon to stop testing against numpy 1.7.1, and with that comes numba 0.11. Four builds is a reasonable number.

from trackpy.