eliminate repeated "the" words
| | |
| | | lookup, because the registration will always be made with a specific |
| | | request interface, but registration may not be made with a specific |
| | | context interface. In general, when creating multiadapters, you |
| | | want to order the requires interfaces so that the the elements which |
| | | want to order the requires interfaces so that the elements which |
| | | are more likely to be registered using specific interfaces are |
| | | ordered before those which are less likely. |
| | | |
| | |
| | | Bug Fixes |
| | | --------- |
| | | |
| | | - The the long description of this package (as shown on PyPI) was not |
| | | - The long description of this package (as shown on PyPI) was not |
| | | valid reStructuredText, and so was not renderable. |
| | | |
| | | - Trying to use an HTTP method name string such as ``GET`` as a |
| | |
| | | - The import of ``repoze.bfg.security.Unauthorized`` is deprecated in |
| | | favor of ``repoze.bfg.exceptions.Forbidden``. The old location |
| | | still functions but emits a deprecation warning. The rename from |
| | | ``Unauthorized`` to ``Forbidden`` brings parity to the the name of |
| | | ``Unauthorized`` to ``Forbidden`` brings parity to the name of |
| | | the exception and the system view it invokes when raised. |
| | | |
| | | Backwards Incompatibilities |
| | |
| | | - An ``add_permission`` directive method was added to the Configurator. This |
| | | directive registers a free-standing permission introspectable into the |
| | | Pyramid introspection system. Frameworks built atop Pyramid can thus use |
| | | the the ``permissions`` introspectable category data to build a |
| | | the ``permissions`` introspectable category data to build a |
| | | comprehensive list of permissions supported by a running system. Before |
| | | this method was added, permissions were already registered in this |
| | | introspectable category as a side effect of naming them in an ``add_view`` |
| | |
| | | Assigning to one is still supported but will cause a deprecation |
| | | warning to be emitted, and eventually the feature will be removed. For |
| | | new code, instead of assigning ``response_*`` attributes to the |
| | | request, use API of the the :attr:`pyramid.request.Request.response` |
| | | request, use API of the :attr:`pyramid.request.Request.response` |
| | | object (exposed to view code as ``request.response``) to influence |
| | | rendered response behavior. |
| | | |
| | |
| | | |
| | | #) When I use the security proxy machinery, I can have a view that |
| | | conditionally displays certain HTML elements (like form fields) or |
| | | prevents certain attributes from being modified depending on the the |
| | | prevents certain attributes from being modified depending on the |
| | | permissions that the accessing user possesses with respect to a context |
| | | object. |
| | | |
| | |
| | | happen when the :meth:`~pyramid.config.Configurator.add_static_view` API |
| | | associated with the path fed to :meth:`~pyramid.request.Request.static_url` |
| | | is a *URL* instead of a view name. For example, the ``name`` argument may be |
| | | ``http://example.com`` while the the ``path`` given may be |
| | | ``http://example.com`` while the ``path`` given may be |
| | | ``mypackage:images``: |
| | | |
| | | .. code-block:: python |
| | |
| | | |
| | | This script uses the Python ``optparse`` module to allow us to make sense out |
| | | of extra arguments passed to the script. It uses the |
| | | :func:`pyramid.paster.bootstrap` function to get information about the the |
| | | :func:`pyramid.paster.bootstrap` function to get information about the |
| | | application defined by a config file, and prints the deployment settings |
| | | defined in that config file. |
| | | |
| | |
| | | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| | | |
| | | .. warning:: As of :app:`Pyramid` 1.1 this section is slated to be removed in |
| | | a later documentation release because the the ability to add views |
| | | a later documentation release because the ability to add views |
| | | directly to the :term:`route configuration` by passing a ``view`` argument |
| | | to ``add_route`` has been deprecated. |
| | | |
| | |
| | | '&callback=?'; |
| | | jqhxr = $.getJSON(api_url); |
| | | |
| | | The string ``callback=?`` above in the the ``url`` param to the JQuery |
| | | The string ``callback=?`` above in the ``url`` param to the JQuery |
| | | ``getAjax`` function indicates to jQuery that the query should be made as |
| | | a JSONP request; the ``callback`` parameter will be automatically filled |
| | | in for you and used. |
| | |
| | | and image files, for us, in this case, at |
| | | ``http://localhost:6543/static/`` and below. The first argument is the |
| | | "name" ``static``, which indicates that the URL path prefix of the view |
| | | will be ``/static``. the The second argument of this tag is the "path", |
| | | will be ``/static``. The second argument of this tag is the "path", |
| | | which is a relative :term:`asset specification`, so it finds the resources |
| | | it should serve within the ``static`` directory inside the ``tutorial`` |
| | | package. The scaffold could have alternately used an *absolute* asset |
| | |
| | | """ |
| | | subclass of :class:`~HTTPOk` |
| | | |
| | | This indicates that the the server has fulfilled the request and |
| | | This indicates that the server has fulfilled the request and |
| | | the user agent SHOULD reset the document view which caused the |
| | | request to be sent. |
| | | |
| | |
| | | """ |
| | | subclass of :class:`~HTTPClientError` |
| | | |
| | | This indicates that the the server refuses to accept the request |
| | | This indicates that the server refuses to accept the request |
| | | without a defined Content-Length. |
| | | |
| | | code: 411, title: Length Required |
| | |
| | | |
| | | If ``spec`` is a *relative* asset specification (an asset |
| | | specification without a ``:`` in it, e.g. ``templates/foo.pt``), the |
| | | ``package`` argument of the constructor is used as the the package |
| | | ``package`` argument of the constructor is used as the package |
| | | portion of the asset spec. For example: |
| | | |
| | | .. code-block:: python |