This is also deprecating the symbols in the pythons_hub and the other parts as was suggested in #2565. If this is not (yet) desirable, please comment on this PR. I personally think that we might be able to do this, but I am not sure if there are no problems (e.g. with using 3.10 in non-root modules).

If we want to start printing deprecation messages in 3.10 or add a flag that is controlling this behaviour via rules_python_internal or some other method, I am happy to amend to this PR.

Maybe the with_deprecation symbol should be in //python/private:with_deprecacion?

I ran out of time today, so that is it for today.

This now only warns if RULES_PYTHON_DEPRECATION_WARNINGS is 1, which defaults to 0. I am fine with defaulting it to 1 if we want to default to a more noisy default.

This is great, thank you! I didn't realized I missed so many other spots, sorry about that.

re: deprecating pythons_hub symbols: Yes, deprecating those also makes sense

re: move deprecation helper elsewhere: yes, I agree

re: environment variable: Thanks for creating this. I like this idea a lot.

addendum: I've approved, but not queued for merge, in case you want to move with_deprecated elsewhere before merging. I'm OK with that being done in a separate PR, too.

OK, extra changes that I needed to do:

• Change the usage of rctx.os.environ to rctx.getenv via repo_utils in the config repo.
• Move the deprecation utility to a separate file.

I think this makes the change much more robust and we have a single place for the deprecated symbols.

If we wanted we could add a buildozer command for the migration, but I think we can merge as is right now.