Skip to content
New issue

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

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

Already on GitHub? # to your account

pmdarima setuptools update #401

Closed
rodrigo-carvalho93 opened this issue Dec 1, 2020 · 2 comments · Fixed by #402
Closed

pmdarima setuptools update #401

rodrigo-carvalho93 opened this issue Dec 1, 2020 · 2 comments · Fixed by #402
Labels
feature request A tag for feature requests

Comments

@rodrigo-carvalho93
Copy link

pmdarima 1.7.1 requires setuptools<50.0.0, but you'll have setuptools 50.3.2 which is incompatible.

I'm part of a team that's developing an app and we would like to use pmdarima to support our predictions, but we are having a big conflict with the version of setuptools. I heard it is pinned at version 50.0.0 because of some conflicts with distutils, but I wonder if you guys intend upgrading its version?
I kinda tried to run-around this trouble making my own home-made auto_arima, but its defenitely not as good as the one you guys made.
Thanks anyway! Keep up the awesome job

@rodrigo-carvalho93 rodrigo-carvalho93 added the feature request A tag for feature requests label Dec 1, 2020
@aaronreidsmith aaronreidsmith linked a pull request Dec 2, 2020 that will close this issue
8 tasks
@aaronreidsmith
Copy link
Member

Yeah, that's our bad. We had an issue in the middle of a release when they simultaneously released setuptools 50.0.0 (see #379 and pypa/setuptools#2356), so we pinned it and I guess we forgot about it. I just opened #402 which should fix it, and we will get that out when we release 1.8.0 soon

@tgsmith61591
Copy link
Member

Merged in #402. We will get 1.8.0 out this week with the fix included.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
feature request A tag for feature requests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants