python310: Update to version 3.10.6

[th0ma7]

Description

python310: Update to version 3.10.6

NOTE: numpy fails to build using setuptools >= 64.x

Checklist

• Build rule all-supported completed successfully
• New installation of package completed successfully
• Package upgrade completed successfully (Manually install the package again)
• Package functionality was tested
• Any needed documentation is updated/created

Type of change

• Bug fix
• New Package
• Package update
• Includes small framework changes
• This change requires a documentation update (e.g. Wiki)

[hgy59]

@th0ma7 see comment in numpy/numpy#22135 (comment), numpy has pinned setuptools to v59.2.0 in their environment. So this is probably not a bug, but not supported by intention.

[th0ma7]

@th0ma7 see comment in numpy/numpy#22135 (comment), numpy has pinned setuptools to v59.2.0 in their environment. So this is probably not a bug, but not supported by intention.

Good catch. They actually mention <=64.x numpy/numpy#22135 (comment)

[th0ma7]

This was tested and LGTM. @hgy59 seing anything missing before I merge & shoule I wait for #5399 before publishing?

[hgy59]

This was tested and LGTM. @hgy59 seing anything missing before I merge & shoule I wait for #5399 before publishing?

Or you could cherry pick the setuptools-rust (3262891) from it, so #5399 will not trigger the build of all python310 dependent packages.
But I am not sure, whether it is the right way to build cryptography within crossenv. Regular builds use PyO3 and I am very confused about how pip builds cryptography with setuptools-rust and what is going on under the hood... (python is still a strange ecosystem for me...).

[th0ma7]

cherry pick the setuptools-rust

Will do.

I am very confused about how pip builds cryptography with setuptools-rust and what is going on under the hood... (python is still a strange ecosystem for me...).

indeed, it's not all that easy to follow, nor am I understanding it all...