fz0x1/HPI
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

try to add html id

Browse source
This commit is contained in:
Sean Breckenridge 2021-04-11 07:53:23 -07:00
parent 2d6dc17903
commit 30acca7f63
2 changed files with 7 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/MODULE_DESIGN.org
View file

@ -54,9 +54,11 @@ Not all HPI Modules are currently at that level of complexity -- some are simple
A related concern is [[*An Extendable module structure][how to structure namespace packages]] to allow users to easily extend them, and how this conflicts with single file modules. If a module is converted from a single file module to a namespace with multiple files, it seems this is a breaking change, see [[https://github.com/karlicoss/HPI/issues/89][#89]] for an example of this.
#+html <div id="addingmodules"></div>
* Adding new modules
As always, if the changes you wish to make are small, or you just want to add a few modules, you can clone and edit an editable install of HPI. See [[file:SETUP.org::*Adding/modifying modules][adding/modifying modules]]
As always, if the changes you wish to make are small, or you just want to add a few modules, you can clone and edit an editable install of HPI. See [[file:SETUP.org][SETUP]] for more information
The "proper way" (unless you want to contribute to the upstream) is to create a separate file hierarchy and add your module to =PYTHONPATH=.