Description:
🐍 Reverse mapping tool: from Python import statements to pip package names. Perfect for AI-generated code!
Website:
https://pypi.org/project/pyimport2pkg/
Topics (Keywords):
python
pip
package-manager
dependencies
import
requirements
packaging
pypi
developer-tools
ai-coding
code-analysis
dependency-management
module-mapping
reverse-mapping
static-analysis
Enable the following features:
- ✅ Issues
- ✅ Projects
- ✅ Wiki (optional)
- ✅ Discussions (recommended for Q&A)
- ✅ Sponsorships (if applicable)
Image recommendation: Create a 1280x640px banner with:
- PyImport2Pkg logo/name
- Tagline: "Python Import → Pip Package"
- Example:
import cv2→opencv-python
Current badges in README.md:
- Python 3.10+
- MIT License
- Latest Release v1.0.0
Consider adding:
- PyPI Downloads:
 - PyPI Version:
 - GitHub Stars:
 - Tests:

Title:
v1.0.0 - First Stable Release 🎉
Tag:
v1.0.0
Target: master branch
Release Notes: Use content from RELEASE_v1.0.0.md
Assets: Automatically included from git tag
Consider setting up:
-
Tests on PR/Push
- Run pytest on Python 3.10, 3.11, 3.12, 3.13 - Check code style - Run type checking
-
Auto-publish to PyPI
- Trigger on new tag `v*.*.*` - Build and publish to PyPI
-
Auto-generate Release Notes
- Extract changes from CHANGELOG - Post to GitHub Releases
Already have:
- ✅ README.md (English)
- ✅ README.zh_CN.md (Chinese)
- ✅ LICENSE (MIT)
Consider adding:
CONTRIBUTING.md- How to contributeCODE_OF_CONDUCT.md- Community guidelinesSECURITY.md- Security policy.github/ISSUE_TEMPLATE/- Issue templates.github/PULL_REQUEST_TEMPLATE.md- PR template
For master branch:
- ✅ Require pull request reviews before merging
- ✅ Require status checks to pass before merging
- ✅ Require branches to be up to date before merging
- ✅ Include administrators
Recommended labels:
Type:
bug- Something isn't workingenhancement- New feature or requestdocumentation- Improvements or additions to documentationquestion- Further information is requested
Priority:
priority: high- High prioritypriority: medium- Medium prioritypriority: low- Low priority
Status:
wontfix- This will not be worked onduplicate- This issue or pull request already existsgood first issue- Good for newcomershelp wanted- Extra attention is needed
Area:
area: cli- CLI relatedarea: api- Python API relatedarea: database- Database buildingarea: mapping- Module-to-package mapping
Create a project board for issue tracking:
Columns:
- 📋 To Do - Planned features/fixes
- 🚧 In Progress - Currently working on
- 👀 Review - Awaiting review
- ✅ Done - Completed
Recommended categories:
- 💬 General - General discussions
- 💡 Ideas - Feature requests and ideas
- 🙏 Q&A - Questions and answers
- 📣 Announcements - Project announcements
- 🎉 Show and Tell - Share your usage
On PyPI (https://pypi.org/project/pyimport2pkg/):
Project Links:
- Homepage:
https://github.com/buptanswer/pyimport2pkg - Documentation:
https://github.com/buptanswer/pyimport2pkg/blob/master/README.md - Bug Tracker:
https://github.com/buptanswer/pyimport2pkg/issues - Changelog:
https://github.com/buptanswer/pyimport2pkg/blob/master/documents/CHANGELOG/ - Source Code:
https://github.com/buptanswer/pyimport2pkg
Consider adding sections:
- Star History - Show growth
- Contributors - Thank contributors
- Sponsors - If applicable
- Similar Projects - Comparison with alternatives
- Citation - How to cite in academic work
This document provides configuration guidelines for maintaining the PyImport2Pkg GitHub repository.