json-schema-org / json-schema-org/website
🐛 Bug: "python 3" filter should be removed
Open
Nobody has claimed this yet.
🐛 Bug
Status: Triage
- Dominant language
- HTML
- Stars
- 169
- Forks
- 484
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 6
Description
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
- go to https://json-schema.org/tools
- fitler on "language: Python 3" and "tooling type: Validator"
- apply filter
- see nothing
- 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the tools page and trace the configuration that supplies its language filters. Remove the “Python 3” option while retaining “Python,” then verify the reproduction steps no longer show the confusing choice and that Python tools remain discoverable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100