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.
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 believe it would be better if we treat this table as an example and point the reader to the files where the most up to date versions can be found such as
setup.py
andrequirements/*
. That way, this documentation will be more resilient to version upgrades.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.
Agree, should I extend the scope of the current PR, or open a new PR for this?
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.
Thank you for opening a new PR for it.
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.
@michael-s-molina
I tried looking into this issue once before. I couldn't figure out why this table had been changed from referencing the optional extras requirements that are managed in the setup.py to the state the table now is in where it no longer specifies the optional extras requirements but instead directly lists the actual driver package names in the documentation table itself.
I think there is a bigger question of how to manage the driver compatibility and support in general. I.e. should the be such a concept of "officially supported and tested drivers" that should have an expectation of always working, vs community-supported and tested drivers?
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.
That's an interesting question @cwegener. My suggestion would be to create a GitHub discussion and tag some folks such as @dpgaspar @villebro @john-bodley @rusackas @betodealmeida and myself or bring this to the Town Hall.