Open o11c opened 8 years ago
There is a Python standard for registering and discovering plugins, but that's using eggs, which aren't supposed to be used anymore.
https://pythonhosted.org/setuptools/pkg_resources.html#locating-plugins
If not, I'm all for just documenting the import.
Note, since you haven't been on IRC: I've been sketching out an idea for removing the need for any -gdb.py
files or import
s for pretty printers in favor of some magic with __path__
. Something similiar could possibly be used here, since gui
is not a good top-level package name, and gdb.gui
is not directly possible.
I still need to investigate how stuff works with Python2, since Debian's gdb-python2 package is completely and utterly broken.
Regarding the gui
or gdb.gui
issue -- I am not averse to renaming the package.
It seems reasonable but we're still left with the issue of integrating into gdbinit somehow. I guess we can just document "python import mumble".