This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Breakout dependency sets into extras, establish a better pattern for adapters with missing imports #35
Labels
tag: internal
Issues and PRs for maintainance of the project - not interesting to external users
type: enhancement
Issues and PRs related to improvements to existing features
We haven't yet decided whether we want to push for adapters to all be part of
csp
proper, or if we want/expect adapters to be maintained independently. Regardless, we currently have C++-basedparquet
andkafka
adapters, python-baseddb
,csv
,perspective
,websocket
,symphony
, andslack
adapters, with plans for C++-basedredis
, andwebsocket
adapters, so it seems likely that we will have a reliance on lots of python libraries.We will want to establish a (better) pattern for optional dependency sets, at the very least moving optional dependencies to their own extras blocks in
pyproject.toml
, and having a more graceful handling at runtime when dependencies are missing.The text was updated successfully, but these errors were encountered: