diff options
| author | Tres Seaver <tseaver@palladion.com> | 2013-04-03 11:26:08 -0700 |
|---|---|---|
| committer | Tres Seaver <tseaver@palladion.com> | 2013-04-03 11:26:08 -0700 |
| commit | 84e455cf7c8d9cbfe6658548a61af2ecbbc1749e (patch) | |
| tree | 23c77ac62ab9d6c93131874f835ae3166d4af53b /docs/narr | |
| parent | 20c57e6cbdd28fba9fa660d6d47f940a6b9c730b (diff) | |
| parent | e3d07fd8792bb06c69909e2b664403ae3bbba5d3 (diff) | |
| download | pyramid-84e455cf7c8d9cbfe6658548a61af2ecbbc1749e.tar.gz pyramid-84e455cf7c8d9cbfe6658548a61af2ecbbc1749e.tar.bz2 pyramid-84e455cf7c8d9cbfe6658548a61af2ecbbc1749e.zip | |
Merge pull request #968 from tshepang/diff
add cross-refs for zope.component
Diffstat (limited to 'docs/narr')
| -rw-r--r-- | docs/narr/zca.rst | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/docs/narr/zca.rst b/docs/narr/zca.rst index 2ef8a7373..b0e9b1709 100644 --- a/docs/narr/zca.rst +++ b/docs/narr/zca.rst @@ -83,7 +83,7 @@ While this services a reasonable goal, it causes some issues when trying to use patterns which you might use to build a typical :term:`Zope` application to build a :app:`Pyramid` application. Without special help, ZCA "global" APIs such as -``zope.component.getUtility`` and ``zope.component.getSiteManager`` +:func:`zope.component.getUtility` and :func:`zope.component.getSiteManager` will use the ZCA "global" registry. Therefore, these APIs will appear to fail when used in a :app:`Pyramid` application, because they'll be consulting the ZCA global registry rather than the @@ -104,8 +104,8 @@ Disusing the Global ZCA API +++++++++++++++++++++++++++ ZCA "global" API functions such as ``zope.component.getSiteManager``, -``zope.component.getUtility``, ``zope.component.getAdapter``, and -``zope.component.getMultiAdapter`` aren't strictly necessary. Every +``zope.component.getUtility``, :func:`zope.component.getAdapter`, and +:func:`zope.component.getMultiAdapter` aren't strictly necessary. Every component registry has a method API that offers the same functionality; it can be used instead. For example, presuming the ``registry`` value below is a Zope Component Architecture component @@ -113,7 +113,6 @@ registry, the following bit of code is equivalent to ``zope.component.getUtility(IFoo)``: .. code-block:: python - :linenos: registry.getUtility(IFoo) |