D7376: help: create packages for the help text

[martinvonz (Martin von Zweigbergk)]

martinvonz added a comment.


  In D7376#108863 <https://phab.mercurial-scm.org/D7376#108863>, @indygreg wrote:
  
  > FWIW I have a series of patches somewhere that teach the help, templates, etc subsystems to use the `importlib.resources` API if available.
  
  I'd be happy to see those soon. I had just started working on that.
  
  > I also have plans to enable PyOxidizer to package resources with more flexibility so we wouldn't necessarily have to rename a bunch of files and add `__init__.py` files to mark directories as packages so `importlib.resources` *just works*. I haven't gotten around to it yet. I figured if Mercurial has resources files like this, other projects would, so I would need to teach PyOxidizer to handle wonky layouts like this.
  > But if we want to continue and support the `importlib.resources` API so things work with the current state of PyOxidizer, that's fine by me. It just isn't strictly required if there is resistance to mass renaming files and conforming to the wonky requirements imposed today.
  
  I'm fine with fixing it in mercurial. It seems like the right way of doing it anyway and it's not that much work.

REPOSITORY
  rHG Mercurial

CHANGES SINCE LAST ACTION
  https://phab.mercurial-scm.org/D7376/new/

REVISION DETAIL
  https://phab.mercurial-scm.org/D7376

To: mharbison72, #hg-reviewers, marmoute
Cc: indygreg, martinvonz, mercurial-devel