Pipreqs bug for mysql-python-connector
- Dominant language
- Python
- Stars
- 7.5k
- Forks
- 424
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I found a bug that I want to report.
I am using the **mysql-connector-python** connector to connect to a database.
When I run pipreqs in the terminal ---- ----- > in the requirements.txt file I get the mysql-connector-repackaged package instead of the mysql-connector-python one.
And it is consistent across all my windows machines where I have tried generating this.
I think it has something to do with updating :-?? because the repackaged version is an older one.
Thanks a lot!
Contributor guide
Research direction
Start by reproducing pipreqs on Windows with a project that imports mysql-connector-python, then inspect how that import is mapped to a package name. Done means the generated requirements.txt selects mysql-connector-python rather than mysql-connector-repackaged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100