🐛 Bug: "python 3" filter should be removed

[xmo-odoo]

Describe the bug

The "Python 3" language filter is useless and confusing:

• Python 2 was EOL'd with the end of support for Python 2.7 on January 1st, 2020 (https://www.python.org/doc/sunset-python-2/)
• only one package is listed under python 3 (jsonschema-models), which seems to have been more out of confusion than any logic
• per (1), every package listed under "python" should run on python 3 unless they have been unmaintained for a very very long time

Steps To Reproduce

1. go to https://json-schema.org/tools
2. fitler on "language: Python 3" and "tooling type: Validator"
3. apply filter
4. see nothing
5. realise you should have selected "python" because that's where most of the libraries live

Expected Behavior

Not having a confusing option for python.

Are you working on this issue?

No

Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)

No

[AnujAga2005]

Hi! I’d like to work on this issue.

It seems the current “Python 3” filter is misleading, since all actively maintained Python libraries should already support Python 3, and the separate filter causes confusion.

Before I begin, could you please confirm the expected behavior?
My understanding is that we should remove the “Python 3” filter and consolidate everything under a single “Python” category.

If this approach is correct, could you assign the issue to me so I can proceed?
Thanks!

[IshaanXCoder]

Hi! I'd like to take this up. The fix seems straightforward, i.e. removing the redundant "Python 3" filter and keeping a single unified "Python" category.
Please assign this issue to me so I can start working on it. Thanks!