make ray and semver dependencies optional #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed that our builds were failing because I did not have
ray
orsemver
installed and they were added tobtrdb/utils/ray.py
with Gabe's serialization work. I was hesitant to add them as requirements because they are only really necessary when the user is trying to use ray with the bindings, so I added a try/except to throw an exception when a user tries to register a custom serializer but does not have these modules installed.I'm open to feedback on this, this is just the first thing that came to mind.