-
Notifications
You must be signed in to change notification settings - Fork 111
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
Dependencies during installation of pyroSAR #140
Comments
Any comments on this please? Thank you. :) |
Hi @sid-ks, thanks for addressing this issue. |
Wow, really appreciate your time and efforts. I would be very glad to help out in someway, but its quite hectic at work even for me, and also being a beginner I wouldn't wanna slow down your schedule. Great package ! Have a nice day! :) |
Thanks mate! I had a quick search of how to solve this with little effort. With pip you have the PEP 508 convention. For the conda package the best approach seems to be to split |
Hi, just a quick question.
Why does pyroSAR install matplotlib, jupyter, notebook and other such dependencies when doing a pip3 install?
Is there a way to make it more lean, with only pure dependencies of pyroSAR being installed?
If so, can you tell me how, if not, please explain why these are required.
Im quite a fan of pyroSAR and how actively it is maintained and updated. Thanks for your efforts! :)
The text was updated successfully, but these errors were encountered: