radareorg/radare2-r2papi

High Level API on top of the R2Pipe interface

radare2-r2papi

Formerly known as r2pipe-api, but papi sounds better.

This repository contains a high-level API on top of r2pipe, abstracting the r2 commands with a human-friendly taste.

As long as this API will require some discussion because it will serve as a way to redesign the R2 C Apis at some point, we must focus on practical use cases, flexibility, ortogonality and other ities.

Feel free to open issues, send PRs with proposals.

--pancake

radare2-r2papi's Issues

Fix tests

Tests broken, probably because the latest radare2

Export graph api also

To get the petgraph representation of radare2 graph commands output, like agj or dmhg.

use context manager for more pythonic code?

I'm trying to think about how the usage of the python library can be made cleaner.

I'm hesitant about this proposal, but it occurred to me that using context managers for the R2Api objects would give a cleaner usage pattern, at least for short interactions:

For instance, the main api instantiation It would look something like this:

with open_in_radare('/bin/ls') as bin:
  if bin.is_stripped:
    print "this binary is stripped"
 searchIn(bin, 'io.sections.exec')
 analyzeCalls(bin)

basically this avoids having to manually quit() the api object - but it makes code indentated. I find it more readable this way tho. what do you think, is it worthy to explore this? maybe the change makes more sense with some other objects instead.

Missing objects in python r2api

From comments in #9

Let's enumerate the missing objects:

• eval
• graph
• print
• flags
• search
• signatures
• write
• bins

Create sphinx docs

We should document current methods and classes, and generate docs based on that.
Probably sphinx is the best choice, it can be integrated with beta r2 website.