Skip to content

Test/lint baseline#43

Open
sjswerdloff wants to merge 3 commits intokyegomez:mainfrom
sjswerdloff:test/lint-baseline
Open

Test/lint baseline#43
sjswerdloff wants to merge 3 commits intokyegomez:mainfrom
sjswerdloff:test/lint-baseline

Conversation

@sjswerdloff
Copy link
Copy Markdown

Add CI to check formatting (black) and linting (ruff), using poetry per contents of pyproject.toml.
Testing is commented out (see PR #42).
Adjusting python version range to avoid clashing with triton requirements (so poetry will be able to resolve).

These two files were the only ones not conforming to the project's
own black configuration (line-length=88, target-version=py310).
Runs on push to main and PRs:
- black --check (formatting)
- ruff check (linting)
- pytest (tests)

Uses Poetry (matching pyproject.toml build-system) on Python 3.10 and 3.12.
torch 2.11.0 depends on triton 3.6.0 which requires Python <3.15.
The previous range (>=3.10,<4.0) caused Poetry dependency resolution
to fail because it couldn't guarantee compatibility for Python >=3.15.
@Qodo-Free-For-OSS
Copy link
Copy Markdown

Hi, pyproject.toml allows Python >=3.10,<3.15 but classifiers only declare Python 3.10, which is inconsistent metadata for users and packaging tooling. This can misrepresent supported versions on PyPI.

Severity: informational | Category: maintainability

How to fix: Align classifiers with version range

Agent prompt to fix - you can give this to your LLM of choice:

Issue description

Package classifiers don’t reflect the Python version range declared in python = ">=3.10,<3.15".

Issue Context

Classifiers are used for metadata/discoverability and can affect user expectations.

Fix Focus Areas

  • pyproject.toml[30-41]

Suggested direction

Add classifiers for the supported versions (e.g., 3.11–3.14) or narrow the version range to match what you actually support/test.


Qodo code review - free for open-source.

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