Skip to content

Add log_level = "INFO" to pytest configuration (PP304) - #7

Closed
nstarman with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-log-level-in-pytest
Closed

nstarman with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-log-level-in-pytest

Conversation

Copilot AI commented Dec 1, 2025 •

Copy link
Copy Markdown

Description

This pull request is to address the PP304 check from Scientific Python Development Guide.

Adds log_level = "INFO" to [tool.pytest.ini_options] in pyproject.toml. This enables log capture during test runs, allowing logs to be displayed on test failures for easier debugging.

  • By checking this box, the PR author has requested that maintainers do NOT use the "Squash and Merge" button. Maintainers should respect this when possible; however, the final decision is at the discretion of the maintainer that merges the PR.
Original prompt

Help me fix https://learn.scientific-python.org/development/guides/pytest#PP304\Sets the log level in pytest]8;;\ ❌
log_level should be set. This will allow logs to be displayed on failures.

 [tool.pytest.ini_options]                                                  
 log_level = "INFO"

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Copilot AI changed the title [WIP] Fix log level setting in pytest configuration Add log_level = "INFO" to pytest configuration (PP304) Dec 1, 2025
Copilot AI requested a review from nstarman December 1, 2025 17:42
@nstarman nstarman closed this Dec 1, 2025
@neutrinoceros
neutrinoceros deleted the copilot/fix-log-level-in-pytest branch December 2, 2025 08:24
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