Python version and pre-commit

[schodet]

Allow usage of python version 3.13 as this is the one shipped with Debian stable since Trixie. This will make life easier for Debian users.

Add pre-commit configuration to automatically check coding style on commit. This is a useful tool, tell me what you think about it.

[github-actions]

Download the artifacts for this pull request:

• pr_number.zip
• mpy-cross.zip
• cityhub-firmware-build-4161-git47da6546.zip
• essentialhub-firmware-build-4161-git47da6546.zip
• movehub-firmware-build-4161-git47da6546.zip
• ev3-firmware-build-4161-git47da6546.zip
• nxt-firmware-build-4161-git47da6546.zip
• technichub-firmware-build-4161-git47da6546.zip
• primehub-firmware-build-4161-git47da6546.zip

[coveralls]

coverage: 58.75%. remained the same
when pulling 170de96 on schodet:python-pre-commit
into 9759e90 on pybricks:master.

[dlech]

Suggested change

	python = ">=3.10,<3.14"
	python = ">=3.10"

Then we don't have to change it in the future. If poetry lock fails with this, we can limit the python version in individual dependencies instead.

[schodet]

pybricks-micropython% poetry lock
Resolving dependencies... (5.9s)

The current project's supported Python range (>=3.10) is not compatible with some of the required packages Python requirement:
  - pybricksdev requires Python <3.14,>=3.10, so it will not be installable for Python >=3.14
  - pybricks requires Python <4.0,>=3.8, so it will not be installable for Python >=4.0
  - pybricks requires Python >=3.8,<4.0, so it will not be installable for Python >=4.0
  - pybricks requires Python >=3.8,<4.0, so it will not be installable for Python >=4.0
  - pybricks requires Python >=3.8,<4.0, so it will not be installable for Python >=4.0
  - pybricks requires Python >=3.8,<4.0, so it will not be installable for Python >=4.0
  - pybricks requires Python >=3.8,<4.0, so it will not be installable for Python >=4.0
  - pybricks requires Python <4.0,>=3.8, so it will not be installable for Python >=4.0
  - pybricks requires Python <4.0,>=3.8, so it will not be installable for Python >=4.0

    Because no versions of pybricksdev match >1.2.0,<2.0.0 || >2.0.0,<2.0.1 || >2.0.1
 and pybricksdev (2.0.0) depends on pybricks (>=3), pybricksdev (>1.2.0,<2.0.1 || >2.0.1) requires pybricks (>=3).
(1) So, because pybricksdev (2.0.1) depends on pybricks (>=3), pybricksdev (>1.2.0) requires pybricks (>=3).

    Because no versions of pybricks match >=3,<3.1.0 || >3.1.0,<3.2.0 || >3.2.0,<3.3.0 || >3.3.0,<3.4.0 || >3.4.0,<3.4.1 || >3.4.1,<3.5.0 || >3.5.0,<3.6.0 || >3.6.0,<3.6.1 || >3.6.1,<4.0.0
 and pybricks (3.1.0) requires Python >=3.8,<4.0, pybricks is forbidden.
    And because pybricks (3.2.0) requires Python >=3.8,<4.0
 and pybricks (3.3.0) requires Python >=3.8,<4.0, pybricks is forbidden.
    And because pybricks (3.4.0) requires Python >=3.8,<4.0
 and pybricks (3.4.1) requires Python >=3.8,<4.0, pybricks is forbidden.
    And because pybricks (3.5.0) requires Python <4.0,>=3.8
 and pybricks (3.6.0) requires Python <4.0,>=3.8, pybricks is forbidden.
    And because pybricksdev (>1.2.0) requires pybricks (>=3) (1), pybricksdev (>1.2.0) requires pybricks (3.6.1 || >=4.0.0)
    And because pybricksdev (1.2.0) requires Python <3.14,>=3.10
 and pybricks (3.6.1) requires Python <4.0,>=3.8, pybricksdev (>=1.2.0) requires pybricks (>=4.0.0).
    So, because pybricks-micropython depends on both pybricks (^3.0.0a5) and pybricksdev (>=1.2.0), version solving failed.

  * Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties

    For pybricksdev, a possible solution would be to set the `python` property to ">=3.10,<3.14"
For pybricks, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For pybricks, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For pybricks, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For pybricks, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For pybricks, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For pybricks, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For pybricks, a possible solution would be to set the `python` property to ">=3.10,<4.0"
For pybricks, a possible solution would be to set the `python` property to ">=3.10,<4.0"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers

I think ">=3.10,<4.0" would be safer, but it would at least mean to update the pybrickdev dep to 2.0.0.

[dlech]

Hmm... yeah, I guess since this isn't a library that others are depending on, that is fine.

[dlech]

Suggested change

	This can be run automatically using pre-commit. Install pre-commit, then run:
	This can be run automatically using `pre-commit`. Install [pre-commit], then run:

And at the end of the section...

[pre-commit]: https://pre-commit.com/

[dlech]

Or since it is a Python package, we could just add it as a development dependency so there isn't a separate install step.

[dlech]

Suggested change

	It will install a pre-commit hook for this repository. On every commit, the
	It will install a pre-commit git hook for this repository. On every commit, the

[dlech]

Checked or automatically formatted?

[schodet]

I made the changes, I do not know why github actions is stuck…

[dlech]

No source code files changed, so nothing triggered that job. It's normal.

[dlech]

Merged, thanks!