trepan3k

Name	trepan3k JSON
Version	1.2.10 JSON
	download
home_page
Summary	Python cross-version byte-code library and disassembler
upload_time	2024-03-18 02:44:08
maintainer
docs_url	None
author
requires_python
license	GPL
keywords	python bytecode bytecode disassembler
VCS
bugtrack_url
requirements	No requirements were recorded.
Travis-CI	No Travis.
coveralls test coverage	No coveralls.

|packagestatus|

.. contents:: :local:

Abstract
========

This is a gdb-like debugger for Python. It is a rewrite of *pdb* from
the ground up. It is both a high-level debugger as well as a
lower-level bytecode debugger. By lower-level debugger, I mean that it
understands a lot about byte code and will try to make use of that in
its normal higher-level instructions.

A command-line interface (CLI) is provided as well as an remote access
interface over TCP/IP.

See the Tutorial_ for how to use. See ipython-trepan_ for using this
in *ipython* or an *ipython notebook*.

This package is for Python 3.2 and above. See trepan2_ for the same code
modified to work with Python 2.

Features
========

Since this debugger is similar to other_ trepanning_ debuggers_ and *gdb*
in general, knowledge gained by learning this is transferable to those
debuggers and vice versa.

There's a lot of cool stuff here that's not in the stock
Python debugger *pdb*, or in any other Python debugger that I know about.

More Exact location information
-------------------------------

Python reports line information on the granularity of a line. To get
more precise information, we can (de)parse into Python the byte code
around a bytecode offset such as the place you are stopped at.

So far as I know, there is no other debugger that decompile code at runtime.

See the deparse_ command for details.

We use information in the line number table in byte to understand
which lines are breakpointable, and in which module or function the
line appears in. Use info_line_ to see this information.

In the future we may allow specifiying an offset to indicate which
offset to stop at when there are several choices for a given line
number.

Debugging Python bytecode (no source available)
-----------------------------------------------

You can pass the debugger the name of Python bytecode and many times,
the debugger will merrily proceed. This debugger tries very hard find
the source code. Either by using the current executable search path
(e.g. ``PATH``) or for some by looking inside the bytecode for a
filename in the main code object (``co_filename``) and applying that
with a search path which takes into account directory where the
bytecode lives.

Failing to find source code this way, and in other situations where
source code can't be found, the debugger will decompile the bytecode
and use that for showing source test. *This allows us to debug `eval`'d
or `exec''d code.*

But if you happen to know where the source code is located, you can
associate a file source code with the current name listed in the
bytecode. See the set_substitute_ command for details here.

Source-code Syntax Colorization
-------------------------------

Terminal source code is colorized via pygments_ . And with that you
can set the pygments color style, e.g. "colorful", "paraiso-dark". See
set_style_ . Furthermore, we make use of terminal bold and emphasized
text in debugger output and help text. Of course, you can also turn
this off. You can use your own
pygments_style_, provided you have a terminal that supports 256
colors. If your terminal supports the basic ANSI color sequences only,
we support that too in both dark and light themes.

Command Completion
------------------

GNU readline command completion is available. Command completion is
not just a simple static list, but varies depending on the
context. For example, for frame-changing commands which take optional
numbers, on the list of *valid numbers* is considered.

Terminal Handling
-----------------

We can adjust debugger output depending on the line width of your
terminal. If it changes, or you want to adjust it, see set_width_ .

Smart Eval
----------

If you want to evaluate the current source line before it is run in
the code, use ``eval``. To evaluate text of a common fragment of line,
such as the expression part of an *if* statement, you can do that with
``eval?``. See eval_ for more information.

Function Breakpoints
---------------------

Many Python debuggers only allow setting a breakpoint at a line event
and functions are treated like line numbers. But functions and lines
are fundamentally different. If I write::

def five(): return 5

this line means has three different kinds of things. First there is
the code in Python that defines function ``five()`` for the first
time. Then there is the function itself, and then there is some code
inside that function.

In this debugger, you can give the name of a *function* by surrounding
adding ``()`` at the end::

break five()

Also ``five`` could be a method of an object that is currently defined when the
``breakpoint`` command is given::

self.five()

More Stepping Control
---------------------

Sometimes you want small steps, and sometimes large stepping.

This fundamental issue is handled in a couple ways:

Step Granularity
................

There are now ``step`` *event* and ``next`` *event* commands with
aliases to ``s+``, ``s>`` and so on. The plus-suffixed commands force
a different line on a subsequent stop, the dash-suffixed commands
don't. Suffixes ``>``, ``<``, and ``!`` specify ``call``, ``return``
and ``exception`` events respectively. And without a suffix you get
the default; this is set by the ``set different`` command.

Event Filtering and Tracing
...........................

By default the debugger stops at every event: ``call``, ``return``,
``line``, ``exception``, ``c-call``, ``c-exception``. If you just want
to stop at ``line`` events (which is largely what you happens in
*pdb*) you can. If however you just want to stop at calls and returns,
that's possible too. Or pick some combination.

In conjunction with handling *all* events by default, the event status is shown when stopped. The reason for stopping is also available via ``info program``.

Event Tracing of Calls and Returns
----------------------------------

I'm not sure why this was not done before. Probably because of the
lack of the ability to set and move by different granularities,
tracing calls and returns lead to too many uninteresting stops (such
as at the same place you just were at). Also, stopping on function
definitions probably also added to this tedium.

Because we're really handling return events, we can show you the return value. (*pdb* has an "undocumented" *retval* command that doesn't seem to work.)

Debugger Macros via Python Lambda expressions
---------------------------------------------

There are debugger macros. In *gdb*, there is a *macro* debugger
command to extend debugger commands.

However Python has its own rich programming language so it seems silly
to recreate the macro language that is in *gdb*. Simpler and more
powerful is just to use Python here. A debugger macro here is just a
lambda expression which returns a string or a list of strings. Each
string returned should be a debugger command.

We also have *aliases* for the extremely simple situation where you
want to give an alias to an existing debugger command. But beware:
some commands, like step_ inspect command suffixes and change their
behavior accordingly.

We also envision a number of other ways to allow extension of this
debugger either through additional modules, or user-supplied debugger
command directories.

Byte-code Instruction Introspection
------------------------------------

We do more in the way of looking at the byte codes to give better information. Through this we can provide:

* a *skip* command. It is like the *jump* command, but you don't have
to deal with line numbers.
* disassembly of code fragments. You can now disassemble relative to
the stack frames you are currently stopped at.
* Better interpretation of where you are when inside *execfile* or
*exec*. (But really though this is probably a Python compiler
misfeature.)
* Check that breakpoints are set only where they make sense.
* A more accurate determination of if you are at a function-defining
*def* or *class* statements (because the caller instruction contains
``MAKE_FUNCTION`` or ``BUILD_CLASS``.)

Even without "deparsing" mentioned above, the ability to disassemble
where the PC is currently located (see `info pc <info_pc>`_), by line
number range or byte-offset range lets you tell exactly where you are
and code is getting run.

Some Debugger Command Arguments can be Variables and Expressions
----------------------------------------------------------------

Commands that take integer arguments like *up*, *list*, or
*disassemble* allow you to use a Python expression which may include
local or global variables that evaluates to an integer. This
eliminates the need in *gdb* for special "dollar" debugger
variables. (Note however because of *shlex* parsing, expressions can't
have embedded blanks.)

Out-of-Process Debugging
------------------------

You can now debug your program in a different process or even a different computer on a different network!

Related, is flexible support for remapping path names from file
system, e.g. that inside a docker container or on a remote filesystem
with locally-installed files. See subst_ for more information.

Egg, Wheel, and Tarballs
------------------------

Can be installed via the usual *pip* or *easy_install*. There is a
source tarball. `How To Install
<https://python3-trepan.readthedocs.io/en/latest/install.html>`_ has
full instructions and installing from git and by other means.

Modularity
----------

The Debugger plays nice with other trace hooks. You can have several debugger objects.

Many of the things listed below doesn't directly effect end-users, but
it does eventually by way of more robust and featureful code. And
keeping developers happy is a good thing.(TM)

* Commands and subcommands are individual classes now, not methods in a class. This means they now have properties like the context in which they can be run, minimum abbreviation name or alias names. To add a new command you basically add a file in a directory.
* I/O is it's own layer. This simplifies interactive readline behavior from reading commands over a TCP socket.
* An interface is it's own layer. Local debugging, remote debugging, running debugger commands from a file (``source``) are different interfaces. This means, for example, that we are able to give better error reporting if a debugger command file has an error.
* There is an experimental Python-friendly interface for front-ends
* more testable. Much more unit and functional tests. More of *pydb*'s integration test will eventually be added.

Documentation
-------------

Documentation: http://python3-trepan.readthedocs.org

Raw data

            {
    "_id": null,
    "home_page": "",
    "name": "trepan3k",
    "maintainer": "",
    "docs_url": null,
    "requires_python": "",
    "maintainer_email": "",
    "keywords": "Python bytecode,bytecode,disassembler",
    "author": "",
    "author_email": "Rocky Bernstein <rb@dustyfeet.com>",
    "download_url": "https://files.pythonhosted.org/packages/c2/85/b9e22c5bc68f4c64a07257214206fac2bda33b77016c398245c2fa663b42/trepan3k-1.2.10.tar.gz",
    "platform": null,
    "description": "|CircleCI| |Pypi Installs| |license| |Supported Python Versions|\n\n|packagestatus|\n\n.. contents:: :local:\n\nAbstract\n========\n\nThis is a gdb-like debugger for Python. It is a rewrite of *pdb* from\nthe ground up. It is both a high-level debugger as well as a\nlower-level bytecode debugger. By lower-level debugger, I mean that it\nunderstands a lot about byte code and will try to make use of that in\nits normal higher-level instructions.\n\nA command-line interface (CLI) is provided as well as an remote access\ninterface over TCP/IP.\n\nSee the Tutorial_ for how to use. See ipython-trepan_ for using this\nin *ipython* or an *ipython notebook*.\n\nThis package is for Python 3.2 and above. See trepan2_ for the same code\nmodified to work with Python 2.\n\nFeatures\n========\n\nSince this debugger is similar to other_ trepanning_ debuggers_ and *gdb*\nin general, knowledge gained by learning this is transferable to those\ndebuggers and vice versa.\n\nThere's a lot of cool stuff here that's not in the stock\nPython debugger *pdb*, or in any other Python debugger that I know about.\n\n\nMore Exact location information\n-------------------------------\n\nPython reports line information on the granularity of a line. To get\nmore precise information, we can (de)parse into Python the byte code\naround a bytecode offset such as the place you are stopped at.\n\nSo far as I know, there is no other debugger that decompile code at runtime.\n\nSee the deparse_ command for details.\n\nWe use information in the line number table in byte to understand\nwhich lines are breakpointable, and in which module or function the\nline appears in. Use info_line_ to see this information.\n\nIn the future we may allow specifiying an offset to indicate which\noffset to stop at when there are several choices for a given line\nnumber.\n\n\nDebugging Python bytecode (no source available)\n-----------------------------------------------\n\nYou can pass the debugger the name of Python bytecode and many times,\nthe debugger will merrily proceed.  This debugger tries very hard find\nthe source code. Either by using the current executable search path\n(e.g. ``PATH``) or for some by looking inside the bytecode for a\nfilename in the main code object (``co_filename``) and applying that\nwith a search path which takes into account directory where the\nbytecode lives.\n\nFailing to find source code this way, and in other situations where\nsource code can't be found, the debugger will decompile the bytecode\nand use that for showing source test. *This allows us to debug `eval`'d\nor `exec''d code.*\n\nBut if you happen to know where the source code is located, you can\nassociate a file source code with the current name listed in the\nbytecode. See the set_substitute_ command for details here.\n\nSource-code Syntax Colorization\n-------------------------------\n\nTerminal source code is colorized via pygments_ . And with that you\ncan set the pygments color style, e.g. \"colorful\", \"paraiso-dark\". See\nset_style_ . Furthermore, we make use of terminal bold and emphasized\ntext in debugger output and help text. Of course, you can also turn\nthis off. You can use your own\npygments_style_, provided you have a terminal that supports 256\ncolors. If your terminal supports the basic ANSI color sequences only,\nwe support that too in both dark and light themes.\n\n\nCommand Completion\n------------------\n\nGNU readline command completion is available. Command completion is\nnot just a simple static list, but varies depending on the\ncontext. For example, for frame-changing commands which take optional\nnumbers, on the list of *valid numbers* is considered.\n\nTerminal Handling\n-----------------\n\nWe can adjust debugger output depending on the line width of your\nterminal. If it changes, or you want to adjust it, see set_width_ .\n\nSmart Eval\n----------\n\nIf you want to evaluate the current source line before it is run in\nthe code, use ``eval``. To evaluate text of a common fragment of line,\nsuch as the expression part of an *if* statement, you can do that with\n``eval?``. See eval_ for more information.\n\nFunction Breakpoints\n---------------------\n\nMany Python debuggers only allow setting a breakpoint at a line event\nand functions are treated like line numbers. But functions and lines\nare fundamentally different. If I write::\n\n     def five(): return 5\n\nthis line means has three different kinds of things. First there is\nthe code in Python that defines function ``five()`` for the first\ntime. Then there is the function itself, and then there is some code\ninside that function.\n\nIn this debugger, you can give the name of a *function* by surrounding\nadding ``()`` at the end::\n\n    break five()\n\nAlso ``five`` could be a method of an object that is currently defined when the\n``breakpoint`` command is given::\n\n    self.five()\n\nMore Stepping Control\n---------------------\n\nSometimes you want small steps, and sometimes large stepping.\n\nThis fundamental issue is handled in a couple ways:\n\nStep Granularity\n................\n\nThere are now ``step`` *event* and ``next`` *event* commands with\naliases to ``s+``, ``s>`` and so on. The plus-suffixed commands force\na different line on a subsequent stop, the dash-suffixed commands\ndon't.  Suffixes ``>``, ``<``, and ``!`` specify ``call``, ``return``\nand ``exception`` events respectively. And without a suffix you get\nthe default; this is set by the ``set different`` command.\n\nEvent Filtering and Tracing\n...........................\n\nBy default the debugger stops at every event: ``call``, ``return``,\n``line``, ``exception``, ``c-call``, ``c-exception``. If you just want\nto stop at ``line`` events (which is largely what you happens in\n*pdb*) you can. If however you just want to stop at calls and returns,\nthat's possible too. Or pick some combination.\n\nIn conjunction with handling *all* events by default, the event status is shown when stopped. The reason for stopping is also available via ``info program``.\n\nEvent Tracing of Calls and Returns\n----------------------------------\n\nI'm not sure why this was not done before. Probably because of the\nlack of the ability to set and move by different granularities,\ntracing calls and returns lead to too many uninteresting stops (such\nas at the same place you just were at). Also, stopping on function\ndefinitions probably also added to this tedium.\n\nBecause we're really handling return events, we can show you the return value. (*pdb* has an \"undocumented\" *retval* command that doesn't seem to work.)\n\nDebugger Macros via Python Lambda expressions\n---------------------------------------------\n\nThere are debugger macros.  In *gdb*, there is a *macro* debugger\ncommand to extend debugger commands.\n\nHowever Python has its own rich programming language so it seems silly\nto recreate the macro language that is in *gdb*. Simpler and more\npowerful is just to use Python here. A debugger macro here is just a\nlambda expression which returns a string or a list of strings. Each\nstring returned should be a debugger command.\n\nWe also have *aliases* for the extremely simple situation where you\nwant to give an alias to an existing debugger command. But beware:\nsome commands, like step_ inspect command suffixes and change their\nbehavior accordingly.\n\nWe also envision a number of other ways to allow extension of this\ndebugger either through additional modules, or user-supplied debugger\ncommand directories.\n\nByte-code Instruction Introspection\n------------------------------------\n\nWe do more in the way of looking at the byte codes to give better information. Through this we can provide:\n\n* a *skip* command. It is like the *jump* command, but you don't have\n  to deal with line numbers.\n* disassembly of code fragments. You can now disassemble relative to\n  the stack frames you are currently stopped at.\n* Better interpretation of where you are when inside *execfile* or\n  *exec*. (But really though this is probably a Python compiler\n  misfeature.)\n* Check that breakpoints are set only where they make sense.\n* A more accurate determination of if you are at a function-defining\n  *def* or *class* statements (because the caller instruction contains\n  ``MAKE_FUNCTION`` or ``BUILD_CLASS``.)\n\nEven without \"deparsing\" mentioned above, the ability to disassemble\nwhere the PC is currently located (see `info pc <info_pc>`_), by line\nnumber range or byte-offset range lets you tell exactly where you are\nand code is getting run.\n\nSome Debugger Command Arguments can be Variables and Expressions\n----------------------------------------------------------------\n\nCommands that take integer arguments like *up*, *list*, or\n*disassemble* allow you to use a Python expression which may include\nlocal or global variables that evaluates to an integer. This\neliminates the need in *gdb* for special \"dollar\" debugger\nvariables. (Note however because of *shlex* parsing, expressions can't\nhave embedded blanks.)\n\nOut-of-Process Debugging\n------------------------\n\nYou can now debug your program in a different process or even a different computer on a different network!\n\nRelated, is flexible support for remapping path names from file\nsystem, e.g. that inside a docker container or on a remote filesystem\nwith locally-installed files. See subst_ for more information.\n\nEgg, Wheel, and Tarballs\n------------------------\n\nCan be installed via the usual *pip* or *easy_install*. There is a\nsource tarball. `How To Install\n<https://python3-trepan.readthedocs.io/en/latest/install.html>`_ has\nfull instructions and installing from git and by other means.\n\nModularity\n----------\n\nThe Debugger plays nice with other trace hooks. You can have several debugger objects.\n\nMany of the things listed below doesn't directly effect end-users, but\nit does eventually by way of more robust and featureful code. And\nkeeping developers happy is a good thing.(TM)\n\n* Commands and subcommands are individual classes now, not methods in a class. This means they now have properties like the context in which they can be run, minimum abbreviation name or alias names. To add a new command you basically add a file in a directory.\n* I/O is it's own layer. This simplifies interactive readline behavior from reading commands over a TCP socket.\n* An interface is it's own layer. Local debugging, remote debugging, running debugger commands from a file (``source``) are different interfaces. This means, for example, that we are able to give better error reporting if a debugger command file has an error.\n* There is an experimental Python-friendly interface for front-ends\n* more testable. Much more unit and functional tests. More of *pydb*'s integration test will eventually be added.\n\nDocumentation\n-------------\n\nDocumentation: http://python3-trepan.readthedocs.org\n\nSee Also\n--------\n\n* trepan2_ : trepan debugger for Python 2\n* trepanxpy_ : trepan debugger for `x-python <https://pypi.python.org/pypi/x-python>`_, the bytecode interpreter written in Python\n* pydbgr_  : previous incarnation of the Python 2 debugger\n* pydb_ : even older incarnation of debugger (for very old Python 2)\n* Tutorial_: Tutorial for how to use\n* https://github.com/rocky/trepan-xpy : Python debugger using this code to support `x-python <https://pypi.python.org/pypi/x-python>`_\n* https://pypi.python.org/pypi/uncompyle6 : Python decompiler\n* https://pypi.python.org/pypi/decompyle3 : Python 3.7 and 3.8 decompiler\n* https://pypi.python.org/pypi/xdis : cross-platform disassembler\n\n\n.. _pygments:  http://pygments.org\n.. _pygments_style:  http://pygments.org/docs/styles/\n.. _howtoinstall: https://github.com/rocky/python3-trepan/wiki/How-to-Install\n.. _pydb:  http://bashdb.sf.net/pydb\n.. _pydbgr: https://pypi.python.org/pypi/pydbgr\n.. _trepan2: https://pypi.python.org/pypi/trepan2\n.. _trepan3: https://github.com/rocky/python3-trepan\n.. _trepanxpy: https://pypi.python.org/pypi/trepanxpy\n.. _other: https://repology.org/project/zshdb/versions\n.. _trepanning: https://rubygems.org/gems/trepanning\n.. _debuggers: https://metacpan.org/pod/Devel::Trepan\n.. _this: http://bashdb.sourceforge.net/pydb/features.html\n.. _Tutorial: http://python2-trepan.readthedocs.io/en/latest/entry-exit.html\n.. |downloads| image:: https://img.shields.io/pypi/dd/trepan3k.svg\n   :target: https://pypi.python.org/pypi/trepan3k/\n.. |TravisCI| image:: https://api.travis-ci.org/rocky/python3-trepan.svg\n   :target: https://travis-ci.org/rocky/python3-trepan\n.. |CircleCI| image:: https://circleci.com/gh/rocky/python3-trepan.svg?style=svg\n   :target: https://circleci.com/gh/rocky/python3-trepan\n.. _ipython-trepan: https://github.com/rocky/ipython-trepan\n.. |license| image:: https://img.shields.io/pypi/l/trepan.svg\n    :target: https://pypi.python.org/pypi/trepan3k\n    :alt: License\n.. _deparse:  https://python3-trepan.readthedocs.io/en/latest/commands/data/deparse.html\n.. _info_line:  https://python3-trepan.readthedocs.io/en/latest/commands/info/line.html\n.. _set_style:  https://python3-trepan.readthedocs.org/en/latest/commands/set/style.html\n.. _set_substitute:  https://python3-trepan.readthedocs.org/en/latest/commands/set/substitute.html\n.. _set_width:  https://python3-trepan.readthedocs.org/en/latest/commands/set/width.html\n.. _eval: https://python3-trepan.readthedocs.org/en/latest/commands/data/eval.html\n.. _step: https://python3-trepan.readthedocs.org/en/latest/commands/running/step.html\n.. _subst: https://python3-trepan.readthedocs.io/en/latest/commands/set/substitute.html\n.. _install: http://python3-trepan.readthedocs.org/en/latest/install.html\n.. |Supported Python Versions| image:: https://img.shields.io/pypi/pyversions/trepan3k.svg\n   :target: https://pypi.python.org/pypi/trepan3k/\n.. |Pypi Installs| image:: https://pepy.tech/badge/trepan3k\n.. |packagestatus| image:: https://repology.org/badge/vertical-allrepos/python:trepan3k.svg\n\t\t :target: https://repology.org/project/python:trepan3k/versions\n",
    "bugtrack_url": null,
    "license": "GPL",
    "summary": "Python cross-version byte-code library and disassembler",
    "version": "1.2.10",
    "project_urls": {
        "Downloads": "https://github.com/rocky/python-trepan3k/releases",
        "Homepage": "https://pypi.org/project/trepan3k/"
    },
    "split_keywords": [
        "python bytecode",
        "bytecode",
        "disassembler"
    ],
    "urls": [
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "b0414ce019ee0a4d52c9137143d3fa7f39683ada859af363781f57529600ed90",
                "md5": "c3460c7836c23e6e253268b6f878eacb",
                "sha256": "e94008a6c9f7de12647181e4303f610b99d14b3f0e3c3d815bd673f770943506"
            },
            "downloads": -1,
            "filename": "trepan3k-1.2.10-py2.py3-none-any.whl",
            "has_sig": false,
            "md5_digest": "c3460c7836c23e6e253268b6f878eacb",
            "packagetype": "bdist_wheel",
            "python_version": "py2.py3",
            "requires_python": null,
            "size": 549210,
            "upload_time": "2024-03-18T02:44:06",
            "upload_time_iso_8601": "2024-03-18T02:44:06.419206Z",
            "url": "https://files.pythonhosted.org/packages/b0/41/4ce019ee0a4d52c9137143d3fa7f39683ada859af363781f57529600ed90/trepan3k-1.2.10-py2.py3-none-any.whl",
            "yanked": false,
            "yanked_reason": null
        },
        {
            "comment_text": "",
            "digests": {
                "blake2b_256": "c285b9e22c5bc68f4c64a07257214206fac2bda33b77016c398245c2fa663b42",
                "md5": "e6cb00872449142c82225dfb894f1579",
                "sha256": "d3664b7eadc8764f8ad63ebd5830eb1cea0af329df2f1c514403b75e2203e0ed"
            },
            "downloads": -1,
            "filename": "trepan3k-1.2.10.tar.gz",
            "has_sig": false,
            "md5_digest": "e6cb00872449142c82225dfb894f1579",
            "packagetype": "sdist",
            "python_version": "source",
            "requires_python": null,
            "size": 404728,
            "upload_time": "2024-03-18T02:44:08",
            "upload_time_iso_8601": "2024-03-18T02:44:08.895883Z",
            "url": "https://files.pythonhosted.org/packages/c2/85/b9e22c5bc68f4c64a07257214206fac2bda33b77016c398245c2fa663b42/trepan3k-1.2.10.tar.gz",
            "yanked": false,
            "yanked_reason": null
        }
    ],
    "upload_time": "2024-03-18 02:44:08",
    "github": true,
    "gitlab": false,
    "bitbucket": false,
    "codeberg": false,
    "github_user": "rocky",
    "github_project": "python-trepan3k",
    "github_not_found": true,
    "lcname": "trepan3k"
}