Skip to content

Conversation

@rahuldevikar
Copy link
Contributor

@rahuldevikar rahuldevikar commented Jan 2, 2026

Thanks for contributing, make sure you address all the checklists (for details on how see development documentation)

  • ran the linter to address style issues (tox -e fix)
  • wrote descriptive pull request text
  • ensured there are test(s) validating the fix
  • added news fragment in docs/changelog folder
  • updated/extended the documentation

Find and use any Python >= 3.12

virtualenv --python='>=3.12' venv

Use Python compatible with ~=3.11.0 (i.e., 3.11.x)

virtualenv --python='~=3.11.0' venv

Use Python exactly 3.10

virtualenv --python='==3.10' venv

Backward compatible - still works

virtualenv --python=python3.11 venv
virtualenv --python=/usr/bin/python3 venv

Copy link
Contributor

@gaborbernat gaborbernat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, but no pull request will be reviewed or merged without 100% test coverage for all your changes.

@rahuldevikar
Copy link
Contributor Author

rahuldevikar commented Jan 2, 2026

Thanks, but no pull request will be reviewed or merged without 100% test coverage for all your changes.

@gaborbernat Agree, make sense. Will get this fixed

@gaborbernat
Copy link
Contributor

The CI will run on your fork.

@gaborbernat gaborbernat marked this pull request as draft January 2, 2026 15:17
@rahuldevikar
Copy link
Contributor Author

Branch seems corrupted. Moving to new Pull request: #3008

@rahuldevikar
Copy link
Contributor Author

@gaborbernat can you please take a look at #3008 when you get a chance. Test coverage are linked in the comment in that same PR

@gaborbernat gaborbernat closed this Jan 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants