Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation issues with Python 3.9 #122

Closed
aegerton opened this issue Feb 14, 2021 · 11 comments
Closed

Installation issues with Python 3.9 #122

aegerton opened this issue Feb 14, 2021 · 11 comments

Comments

@aegerton
Copy link
Contributor

There appears to be an issue installing on Python 3.9 due to numba installation issues as detailed in the following Issue;-

https://github.com/numba/numba/issues/6345#issue-718596580

Is there a workaround available, please?

@jbogaardt
Copy link
Collaborator

Hi @aegerton , Thankd for reporting as I wasn't aware of this. numba is a hard requirement by way of the sparse package. chainladder doesn't have too many dependencies, but the ones it has are major ones.

  • pandas
  • scikit-learn
  • sparse
  • dill
  • xlcompose (deprecated)

Most of these packages have professional development teams supporting them, numba included. So if they don't have a work-around, I doubt I'd be skilled enough to find one - specifically a workaround for using chainladder on python>=3.9. conda environments help and if I create one with chainladder as the only requirement, it gives me python==3.8.5 if you're okay with a downgrade.

#121 is another recent chainladder issue due to upgrading to the latest in other dependencies. I think what I need to do with this issue is to create a "bleeding edge" CI/CD pipeline that tests against the latest releases of all dependencies to at least be aware of these conflicts when they arise.

@jbogaardt
Copy link
Collaborator

Oh, it's already in, which means it should be in the next release.

Originally posted by @hameerabbasi in pydata/sparse#426 (comment)

It looks like this should resolve once the sparse package does its next release. It looks like their workaround is:

Sparse now installs for python 3.9 if the exact following version is used as a dependency:
numba==0.53.0rc1.post1. But a regular pip install sparse does not work unless numba==0.53.0rc1.post1 is already installed.

Originally posted by @JackWetherell in pydata/sparse#426 (comment)

@aegerton
Copy link
Contributor Author

Thanks @jbogaardt for the usual prompt and helpful response. It is greatly appreciated.

I'll keep an eye open for the sparse release and try again then. In the meantime, I have it working with Python 3.8.6 after downgrading.

Is it worth adding a note about dependency issues with 3.9 to the README, please?

@jbogaardt
Copy link
Collaborator

Is it worth adding a note about dependency issues with 3.9 to the README, please?

Yes, of course.

@hameerabbasi
Copy link

It looks like this should resolve once the sparse package does its next release. It looks like their workaround is:

Small correction, sparse doesn't need a new release, numba does. sparse should magically "just work".

@jbogaardt
Copy link
Collaborator

Thank you @hameerabbasi. You do fantastic work on sparse!

@JackWetherell
Copy link

I will leave a comment here once the final numba/llvmlite release is published, and the suggested workaround from my sparse issue is no longer needed.

jbogaardt added a commit that referenced this issue Feb 16, 2021
@aegerton
Copy link
Contributor Author

Is it worth adding a note about dependency issues with 3.9 to the README, please?

Yes, of course.

Thanks again @jbogaardt. Saw the change. Congratulations on the release of 0.8.0

@JackWetherell
Copy link

JackWetherell commented Mar 22, 2021

The numba/llvmlite release is published. The above workaround is no longer needed. sparse now installs with python 3.9.
The current versions of the relevant dependencies are:

sparse==0.11.2
numba==0.53.0
llvmlite==0.36.0

@jbogaardt
Copy link
Collaborator

Thank you @JackWetherell for letting us know. I'll give it a try.

@jbogaardt
Copy link
Collaborator

Resolved by #139

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants