Ignas Anikevicius

@Ubehebe, I think what you are describing could be a separate issue even if it originatesdue to similar reasons. Could you please create a new ticket? One way to debug...

The https://github.com/jvolkman/repairwheel can then be used to ensure that the wheel works correctly.

The output to `stdout` should be in addition to the output to the file. Is the file and the stdout output different? Could you create a small reproducible example that...

Closing as part of cleaning stale issues, if this is an issue on the latest release, please retest and update the original description.

Regarding the flag value handling, you could 1. Normalize the dictionary so that you are sure that the keys are strings. 2. Set the default of free_threading value to "no"...

Regarding platform names, yes we would have to add free-threading suffix to the platform name. Regarding the version, Hmm... Yeah, adding something special at the end of the version crossed...

FYI, I did a few experiments in https://github.com/aignas/rules_python/tree/exp/freethreading and I think that going with defining extra `PLATFORM` values will make it the easiest. the things that are remaining: * PyPI...

I finally had some time to look into this and finished my previous POC, could you please test https://github.com/bazelbuild/rules_python/pull/2372?

I know there are analysis tests for the python rules and toolchains, but I am not sure how easy that would be to implement that.

Ideally we would like to move to a direction that would allow different test runners to be used in the `py_test` rule and them being able to override the coverage...