"trino" entry points conflicts with `sqlalchemy-trino`
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 42/100
Research direction
Start with the SQLAlchemy entry-point definitions in setup.py around line 72 and inspect how the "trino" name is registered. Confirm the naming used by sqlalchemy-trino and check the project’s existing tests or packaging checks. Done means PyHive no longer registers the conflicting name while its dialect remains discoverable under the agreed replacement.
Written by the indexing model from the issue text.
Description
PyHive defines a "trino" entry point for a SQLAlchemy dialect:
https://github.com/dropbox/PyHive/blob/master/setup.py#L72
If you have both PyHive and sqlalchemy-trino installed both will register the same dialect, and each request will randomly use one of the libraries.
Can we rename the PyHive entry point to trino+pyhive, or something else different?
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 545
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dropbox/PyHive
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100