Updating requirements.txt `ipython-sql`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 55
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Not sure if still active.
It might make more sense to update from ipython-sql to Jupysql.
Adding more context on depracation.
This transition should help you avoid compatibility issues and get access to newer features.
Just switching the name and version as backward compatibility is on.
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.
Research direction
Open requirements.txt and compare the existing ipython-sql entry with the proposed Jupysql replacement and version. Review the linked ipython-sql deprecation context, then confirm the Oracle command-line client still installs with the updated dependency; done means the requirements entry is updated without breaking the stated backward compatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sql
- Domain
- cli, database
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100