rocky / rocky/python-decompile3
Run python test suite after decompiling it
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 167
- PR merge metrics
- No merged PRs in 30d
Description
Description
We should have a way to run the Python tests that python uses to check itself after we decompile that bytecode.
Background
I have a hacky program that works for Python 2.7 only in uncompyle6. Python 3 testing works differently.
With this we can also hook this into Ci testing.
Tests
Note that there is a way to exclude fragile tests. For example those like debugger tests that expect a particular line of the test to have particular text. Or tests that take too long to run.
Contributor guide
No contributing guide indexed for this repository
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 by reading test/stdlib/runtests.sh and compare its Python 2.7 workflow with how the Python 3 tests are currently organized. Identify the test invocation and supported exclusions for fragile or slow tests, then determine how the resulting run can be connected to CI. Done means the decompiled output can be checked with the Python test suite and the selected tests run reliably in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100