Thank you for your interest in contributing to the pyprintf Python library! We value contributions from the community to enhance this project for all users. Whether you're fixing bugs, adding features, improving documentation, or extending functionality, your efforts are greatly appreciated.
By participating in this project, you agree to adhere to our Code of Conduct. Please review it before engaging with the community.
To contribute effectively, ensure you have:
- A basic understanding of Git and GitHub workflows
- Familiarity with Python development
- Python 3.10 or higher installed on your system
- A virtual environment for testing and development
pipandsetuptoolsinstalled- Access to the project's dependencies (see
pyproject.toml)
To report an issue:
- Review the existing issues to avoid duplicates, or open a ticket on the support page.
- Provide detailed information, including:
- Python version
- Steps to reproduce the issue
- Expected and actual behavior
- Screenshots or logs (if applicable)
- Any relevant error messages or stack traces
To propose a new feature, open an issue and include:
- The problem your feature addresses
- A clear and concise description of the proposed solution
- Relevant use cases or examples
To submit a pull request (PR):
- Fork the repository.
- Create a descriptive branch:
git checkout -b feat/your-feature-nameorfix/your-bug-name - Install the project in editable mode:
pip install -e . - Commit your changes with meaningful messages.
- Push your branch:
git push origin your-branch-name - Open a PR with a clear title and detailed description.
- Ensure your changes are compatible with supported Python environments (Python 3.10+).
- Update relevant documentation (e.g., README, inline comments) as needed.
- Submit your PR for review. Maintainers may request changes.
- Once approved, your contribution will be merged into the project.
- Follow PEP 8 coding standards.
- Use descriptive and meaningful names for variables and functions.
- Add comments to clarify complex logic.
- Write in present tense (e.g., "Add feature" instead of "Added feature").
- Limit the first line to 72 characters.
- Provide additional details in the body if necessary.
To ensure the quality of your contributions:
- Test changes in a virtual environment.
- Validate edge cases, such as different input formats or special characters.
- Confirm that your changes do not conflict with existing functionality.
- Use the
Makefilecommands for testing and linting:make testto run testsmake lintto check for linting issuesmake coverageto generate a test coverage report
By contributing to this project, you agree that your work will be licensed under the project's BSD-3-Clause License.
We value and acknowledge significant contributions. Contributors may be recognized in:
- The project's README
- Release notes
- A dedicated "Contributors" section
If you have any questions or need assistance, feel free to reach out via: