-
Notifications
You must be signed in to change notification settings - Fork 58
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
Luminaire to support higher dependent package versions #48
Comments
Maybe consider using dependabot |
dependabot is nice but i think cleanup of existing deps should be performed |
@shahsmit14 to unblock python 3.9 |
Hi! First of all great open-source tool you guys are developing! Going straight to the point: I'm having trouble using luminaire because of this issue. The requirements are too specific, so I'm having a hard time installing luminaire with other libs in my project. A common block is that a lot of tools nowadays already require pandas >=1.0.0. But here we have a strict dependency on an old version of pandas. In my case, I'm trying to benchmark Luminaire and Prophet and I'm falling into these requirements conflicts. Making requirements more flexible, so people could easily integrate luminaire in their projects, is in the roadmap for the next releases? While we don't have this issue fixed, how you guys recommend for me to test luminaire? Install it with no-deps and try to adjust dependencies on my own fork? 🤔 Thanks! |
@rafaelleinio Thanks for bringing up the strict package dependency issue and we are aware of it. This is one of the highest priorities for the next major release. Another major issue we are planing to fix is to support higher python versions beyond 3.6. At this moment there are couple ways you can test luminaire with other packages:
|
@shahsmit14 @Aristarhys @rafaelleinio We have started supporting latest version of most of the critical dependency packages except scipy and statsmodels. I have created a separate issue to address those two libraries and closing this one: #98 |
Right now the dependent packages defined in requirements.txt file are to a specific version. So, we should test and support future versions too.
The text was updated successfully, but these errors were encountered: