Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Merge decompyle3's 3.7 and 3.8 goodness into uncompyle6

Open
#307 13 comments 0 reactions 1 assignee View on GitHub

@x0ret is already working on this.

Since Mar 20, 2020.

Assessment

This issue has not been assessed yet.

Description

Volunteer wanted

At this point probably 3.7 and 3.8 decompilation with its refactored parsing and reduction-rule checking is better than the code in uncompyle6.

Although there still is much to do in decompyle3, there is benefit in backporting it here.

Any volunteers?

Dominant language
Python
Stars
4.3k
Forks
465
Avg merge
4d 11h
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rocky/python-uncompyle6

All issues in rocky/python-uncompyle6

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.