Skip to content

Update configuration to support .toml files#1352

Open
a1-su wants to merge 4 commits into
pyta-uoft:masterfrom
a1-su:support-toml-configuration
Open

Update configuration to support .toml files#1352
a1-su wants to merge 4 commits into
pyta-uoft:masterfrom
a1-su:support-toml-configuration

Conversation

@a1-su

@a1-su a1-su commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

Proposed Changes

This PR updates the configuration options to support .toml files, in addition to the .pylintrc that is currently used. In addition, it updates the tests to add .toml checking.

Type of Change

(Write an X or a brief description next to the type or types that best describe your changes.)

Type Applies?
🚨 Breaking change (fix or feature that would cause existing functionality to change)
New feature (non-breaking change that adds functionality) X
🐛 Bug fix (non-breaking change that fixes an issue)
♻️ Refactoring (internal change to codebase, without changing functionality)
🚦 Test update (change that only adds or modifies tests)
📚 Documentation update (change that only updates documentation)
📦 Dependency update (change that updates a dependency)
🔧 Internal (change that only affects developers or continuous integration)

Checklist

(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)

Before opening your pull request:

  • I have performed a self-review of my changes.
    • Check that all changed files included in this pull request are intentional changes.
    • Check that all changes are relevant to the purpose of this pull request, as described above.
  • I have added tests for my changes, if applicable.
    • This is required for all bug fixes and new features.
  • I have updated the project documentation, if applicable.
    • This is required for new features.
  • I have updated the project Changelog (this is required for all changes).
  • If this is my first contribution, I have added myself to the list of contributors.

After opening your pull request:

  • I have verified that the CI tests have passed.
  • I have reviewed the test coverage changes reported by Coveralls.
  • I have requested a review from a project maintainer.

Questions and Comments

(Include any questions or comments you have regarding your changes.)

@coveralls

coveralls commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator

Coverage Report for CI Build 27395431043

Warning

Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes.
Quick fix: rebase this PR. Learn more →

Coverage increased (+0.2%) to 90.929%

Details

  • Coverage increased (+0.2%) from the base build.
  • Patch coverage: 2 uncovered changes across 2 files (29 of 31 lines covered, 93.55%).
  • No coverage regressions found.

Uncovered Changes

File Changed Covered %
packages/python-ta/src/python_ta/check/helpers.py 4 3 75.0%
packages/python-ta/src/python_ta/config/init.py 25 24 96.0%
Total (3 files) 31 29 93.55%

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 4057
Covered Lines: 3689
Line Coverage: 90.93%
Coverage Strength: 17.67 hits per line

💛 - Coveralls

@a1-su a1-su requested a review from david-yz-liu June 2, 2026 14:35

@david-yz-liu david-yz-liu left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Hi @a1-su, nice work. The changes overall look good. A few general comments:

  1. We should update the PythonTA documentation with this new behaviour (accepting toml files, the [tool.python-ta] section, looking for pyproject.toml file by default, anything else).
  2. There are a few other places in the code base (e.g., variable names) that refer to pylintrc explicitly. These should be modified to use more general terms for "config files" or something similar.

@a1-su a1-su requested a review from david-yz-liu June 8, 2026 16:43
return args_list

try:
with open(config_location, "r") as f:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

In general use a UTF8 encoding for text file reading

# Configuration

PythonTA supports configuration through an "rc file" in the [INI format](https://docs.python.org/3/library/configparser.html).
PythonTA supports configuration through `pyproject.toml` files and "rc files" in the [INI format](https://docs.python.org/3/library/configparser.html).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I would just say "TOML" files. The filename pyproject.toml is a default, but users can pass in arbitrary toml files as the config argument to python_ta.check_all, I believe (please make sure to test this)

PythonTA supports configuration through `pyproject.toml` files and "rc files" in the [INI format](https://docs.python.org/3/library/configparser.html).
A custom configuration file can be passed in the command-line using the `--config <path>` option,
and to `python_ta.check_all` with the `config=<path>` argument.
When using a `pyproject.toml` file, PythonTA-specific options must be placed under the [tool.python-ta] section, while standard Pylint options should be placed under [tool.pylint] (e.g., [tool.pylint.FORMAT]).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Same comment as above about the filename.

Also, please put all section headers in monospace font, e.g. [tool.python-ta].

@a1-su a1-su requested a review from david-yz-liu June 12, 2026 05:09
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.

3 participants