-
Notifications
You must be signed in to change notification settings - Fork 50
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
MAINT: add optional packages for tensorflow and tensorflow-cpu; update documentation #262
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, only issue is the pinned versions
You will need to manually install TensorFlow; due to TensorFlow's packaging it is not a direct dependency of SciKeras. | ||
You can do this by running: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's worth leaving a comment in explaining why we recommend installing with extras. Something like:
SciKeras packages TensorFlow as an optional dependency because there are several flavors of TensorFlow available (
tensorflow
,tensorflow-cpu
, etc.).pip install scikeras[tensorflow]
is equivalent topip install scikeras tensorflow
and is offered just for convenience. You can also install just SciKeras withpip install scikeras
, but you will need a version of tensorflow installed at runtime or SciKeras will throw an error when you try to import it.
Thinking about this a bit more: do you see any advantage in making these optional dependencies |
Codecov Report
@@ Coverage Diff @@
## master #262 +/- ##
==========================================
- Coverage 98.27% 98.13% -0.14%
==========================================
Files 7 7
Lines 752 752
==========================================
- Hits 739 738 -1
- Misses 13 14 +1
Continue to review full report at Codecov.
|
I guess adding it as an optional dependency makes it more obvious, in my opinion, in terms of what is going on. It reminds me of using I'm happy to change whatever you prefer though. |
I think this change works. I agree with your assessment of it being more "obvious" even if it's just thin syntactic sugar.
It's not necessarily a poetry issue (in fact, poetry kinda support this usage when installing a local package via dependency groups). Really this is a pip / package ecosystem issue: pypa/setuptools#1139 |
Thanks @metasyn ! |
Description
Fixes #261
Changes
Update documentation. I updated all pip install sites - but maybe only some need to be updated?