-
Notifications
You must be signed in to change notification settings - Fork 271
Deprecation Warnings #476
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
Comments
Looks like Django dealt with exactly the same issue here: django/django#4846 |
And Scipy did so here: ev-br/scipy@a9843db (With code taken from the Django solution) |
This is a bit of a mess -- I'd suggest reading this thread on the Python issue tracker, and maybe this one. The story is that the Python maintainers decided to deprecate this two years ago in Python 3.0 but not include a deprecation warning until 3.5. Plus it seems that We can either adopt the scipy fix or just do nothing while the Python maintainers make up their minds. If we adopt the fix now, I vote we simply import the function from scipy (but scipy isn't currently a requirement for axelrod). |
I don't like the idea of making scipy a requirement just for this. I'd vote for doing nothing for now... |
Yep, let's sit tight. Too much of a mess to be worth getting into! |
I suggest we keep this issue open (just in case someone else wanted to raise it). |
Looks like the function won't be removed until 2.7 end-of-life (2020). Hopefully by then there's a standard solution, and if not, we can adopt scipy's approach. |
Should be fixable >= 02-Dec-2016 #605 |
Running the unit tests gives the following:
The text was updated successfully, but these errors were encountered: