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

Add proper control-flow analysis

Open
#115 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

Start by reading the scanner phase and its handling of the pseudo control-flow opcodes, especially COME_FROM. Then study the requested basic blocks, interval analysis, and control-flow dominators. Done means control flow is analyzed precisely enough to produce more accurate pseudo-ops and simplify grammar rules.

Written by the indexing model from the issue text.

Description

code refactor Control Flow

They uncompyle6 is way way too hacky for determining control flow. Right now, this is the crap done in the "scanner" phase which adds psuedo control-flow opcodes, namely COME_FROM....

We need to do real control flow with basic blocks, interval analysis and control-flow dominators. The result could still be pseudo-ops, but they would be a lot more precise and simplify grammar rules.

Dominant language
Python
Stars
4.3k
Forks
464
Avg merge
6d 12h
Merged PRs (30d)
2

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.