pycapnp/capnp
Lasse Blaauwbroek 3aade70bfa Some fixes to the magic import system
- Stop adding the directory of every .capnp file to the import path. If a .capnp
  file wants to import a file in its own directory, it should use a relative
  import. Fixes #278
- Stop using /usr/include/capnp as an import path. This is incorrect. It should
  only be /usr/include.
- Stop allowing additional paths to be specified for magic imports. This leads
  to inconsistencies. More specifically, the way that a nested import like
  `ma.mb.mc_capnp` gets imported by python, is to first import `ma`, then import
  `ma.mb`, and finally `ma.mb.mc_capnp`. Pycapnp's magic importing is only
  involved in the last step. So any additional paths specified don't work for
  nested imports. It is very confusing to only have this for non-nested imports.
  Users with folder layouts that don't follow pythons import paths can still use
  `capnp.load(.., .., imports=[blah])`.
2023-11-25 08:16:38 -08:00
..
helpers Allow cancellation of all capability contexts 2023-11-08 07:09:10 -08:00
includes Support _DynamicListReader in _setDynamicField 2023-11-08 07:02:09 -08:00
lib Some fixes to the magic import system 2023-11-25 08:16:38 -08:00
templates bool → cbool (probably just a typo) 2021-04-25 21:51:12 +02:00
__init__.pxd Refactor layout of pxd files 2013-12-08 17:27:59 -08:00
__init__.py Get rid of VoidPromise and (almost) Promise 2023-06-08 08:02:07 +02:00
_gen.py Applying black formatting 2021-10-01 11:12:21 -07:00