diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml index fb3124cd9..6f084c3b2 100644 --- a/.pre-commit-config.yaml +++ b/.pre-commit-config.yaml @@ -25,7 +25,7 @@ repos: exclude: "^tests" - repo: https://github.com/astral-sh/ruff-pre-commit - rev: v0.8.0 + rev: v0.8.1 hooks: - id: ruff args: ["--fix", "--show-fixes"] @@ -51,7 +51,7 @@ repos: exclude: ^src/scikit_build_core/resources/find_python - repo: https://github.com/rbubley/mirrors-prettier - rev: "v3.3.3" + rev: "v3.4.1" hooks: - id: prettier types_or: [yaml, markdown, html, css, scss, javascript, json] @@ -130,12 +130,12 @@ repos: additional_dependencies: [cogapp] - repo: https://github.com/henryiii/validate-pyproject-schema-store - rev: 2024.10.21 + rev: 2024.11.25 hooks: - id: validate-pyproject - repo: https://github.com/python-jsonschema/check-jsonschema - rev: 0.29.4 + rev: 0.30.0 hooks: - id: check-dependabot - id: check-github-workflows diff --git a/docs/faqs.md b/docs/faqs.md index b7fd9ca61..cdddf29a1 100644 --- a/docs/faqs.md +++ b/docs/faqs.md @@ -5,10 +5,10 @@ This section covers common needs. ## Starting a new project The easiest way to get started is to use the [Scientific Python cookie][], which -makes a new project following the [Scientific Python Development Guidelines][]. Scikit-build-core -is one of the backends you can select. The project will have a lot of tooling prepared -for you as well, including pre-commit checks and a noxfile; be sure to read the guidelines -to see what is there and how it works. +makes a new project following the [Scientific Python Development Guidelines][]. +Scikit-build-core is one of the backends you can select. The project will have a +lot of tooling prepared for you as well, including pre-commit checks and a +noxfile; be sure to read the guidelines to see what is there and how it works. Another option is the [pybind11 example][]. @@ -78,8 +78,8 @@ automatically does this for you. See [repairing](#repairing-wheels). ## Making a Conda recipe -`scikit-build-core` is available on conda-forge, and is used in [dozens -of recipes][]. There are a few things to keep in mind. +`scikit-build-core` is available on conda-forge, and is used in [dozens of +recipes][]. There are a few things to keep in mind. You need to recreate your `build-system.requires` in the `host` table, with the conda versions of your dependencies. You also need to add `cmake` and either diff --git a/docs/getting_started.md b/docs/getting_started.md index b0bb00954..49cb1a222 100644 --- a/docs/getting_started.md +++ b/docs/getting_started.md @@ -1,10 +1,10 @@ # Getting started If you've never made a Python package before, [packaging.python.org's -tutorial][] is a great place to start. It walks you through creating a simple package -in pure Python using modern tooling and configuration. Another great resource is -the [Scientific Python Developer Guide][]. And a tutorial can be found at -[INTERSECT Training: Packaging][]. +tutorial][] is a great place to start. It walks you through creating a simple +package in pure Python using modern tooling and configuration. Another great +resource is the [Scientific Python Developer Guide][]. And a tutorial can be +found at [INTERSECT Training: Packaging][]. ## Quick start diff --git a/docs/overrides.md b/docs/overrides.md index ef53da7fa..7dbd62549 100644 --- a/docs/overrides.md +++ b/docs/overrides.md @@ -2,9 +2,9 @@ Scikit-build-core has an override system, similar to cibuildwheel and mypy. You specify a `tool.scikit-build.overrides` array with an `if` key. That `if` key -can take several values, including several based on [PEP 508][]. Inside the override, -you can set any value `tool.scikit-build` supports, and it will override if the `if` -condition is true. +can take several values, including several based on [PEP 508][]. Inside the +override, you can set any value `tool.scikit-build` supports, and it will +override if the `if` condition is true. ## If conditions @@ -110,8 +110,8 @@ The value of `sys.implementation.name`. Takes a regex. Some common values: ### `implementation-version` (version) -Derived from `sys.implementation.version`, following [PEP 508][]. Takes a specifier -set. This is the PyPy version on PyPy, for example. +Derived from `sys.implementation.version`, following [PEP 508][]. Takes a +specifier set. This is the PyPy version on PyPy, for example. ### `env.*` (string or bool) diff --git a/pyproject.toml b/pyproject.toml index da240ddf5..b4a423784 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -251,7 +251,7 @@ extend-select = [ "S", # eval -> literal_eval "SIM", # flake8-simplify "T20", # flake8-print - "TCH", # flake8-type-checking + "TC", # flake8-type-checking "TID251", # flake8-tidy-imports.banned-api "TRY", # tryceratops "UP", # pyupgrade