Glossary¶

ACE¶

An access control entry. An access control entry is one element in an ACL. An access control entry is a three-tuple that describes three things: an action (one of either Allow or Deny), a principal (a string describing a user or group), and a permission. For example the ACE, (Allow, 'bob', 'read') is a member of an ACL that indicates that the principal bob is allowed the permission read against the resource the ACL is attached to.

ACL¶

An access control list. An ACL is a sequence of ACE tuples. An ACL is attached to a resource instance. An example of an ACL is [ (Allow, 'bob', 'read'), (Deny, 'fred', 'write')]. If an ACL is attached to a resource instance, and that resource is findable via the context resource, it will be consulted any active security policy to determine whether a particular request can be fulfilled given the authentication information in the request.

action¶

Represents a pending configuration statement generated by a call to a configuration directive. The set of pending configuration actions are processed when pyramid.config.Configurator.commit() is called.

add-on¶

A Python distribution that uses Pyramid's extensibility to plug into a Pyramid application and provide extra, configurable services.

Agendaless Consulting¶

A consulting organization formed by Paul Everitt, Tres Seaver, and Chris McDonough.

参考

See also Internationalization.

Localizer¶

An instance of the class pyramid.i18n.Localizer which provides translation and pluralization services to an application. It is retrieved via the pyramid.i18n.get_localizer() function.

location¶

The path to an object in a resource tree. See Location-Aware Resources for more information about how to make a resource object location-aware.

Mako¶

Mako is a template language which refines the familiar ideas of componentized layout and inheritance using Python with Python scoping and calling semantics.

matchdict¶

The dictionary attached to the request object as request.matchdict when a URL dispatch route has been matched. Its keys are names as identified within the route pattern; its values are the values matched by each pattern name.

media type¶

A label representing the type of some content. A media type is a nested structure containing a top-level type and a subtype. Optionally, a media type can also contain parameters specific to the type. See RFC 6838 for more information about media types.

Message Catalog¶

A gettext .mo file containing translations.

Message Identifier¶

A string used as a translation lookup key during localization. The msgid argument to a translation string is a message identifier. Message identifiers are also present in a message catalog.

METAL¶

Macro Expansion for TAL, a part of ZPT which makes it possible to share common look and feel between templates.

middleware¶

Middleware is a WSGI concept. It is a WSGI component that acts both as a server and an application. Interesting uses for middleware exist, such as caching, content-transport encoding, and other functions. See WSGI documentation or PyPI to find middleware for your application.

mod_wsgi¶

mod_wsgi is an Apache module developed by Graham Dumpleton. It allows WSGI applications (such as applications developed using Pyramid) to be served using the Apache web server.

module¶

A Python source file; a file on the filesystem that typically ends with the extension .py or .pyc. Modules often live in a package.

multidict¶

An ordered dictionary that can have multiple values for each key. Adds the methods getall, getone, mixed, add and dict_of_lists to the normal dictionary interface. See Multidict and pyramid.interfaces.IMultiDict.

mutable¶

In Python, a value is mutable if it can be changed in place. The Python list and dict types are mutable. When a value is added to or removed from an instance of either, the original object remains. The opposite of mutable is immutable.

Not Found View¶

An exception view invoked by Pyramid when the developer explicitly raises a pyramid.httpexceptions.HTTPNotFound exception from within view code or root factory code, or when the current request doesn't match any view configuration. Pyramid provides a default implementation of a Not Found View; it can be overridden. See Changing the Not Found View.

package¶

A directory on disk which contains an __init__.py file, making it recognizable to Python as a location which can be import -ed. A package exists to contain module files.

PasteDeploy¶

PasteDeploy is a library used by Pyramid which makes it possible to configure WSGI components together declaratively within an .ini file. It was developed by Ian Bicking.

permission¶

A string that represents an action being taken against a context resource. A permission is associated with a view name and a resource type by the developer. Resources are decorated with security declarations (e.g. an ACL), which reference these tokens also. Permissions are used by the active security policy to match the view permission against the resources's statements about which permissions are granted to which principal in a context in order to answer the question "is this user allowed to do this". Examples of permissions: read, or view_blog_entries.

physical path¶

The path required by a traversal which resolve a resource starting from the physical root. For example, the physical path of the abc subobject of the physical root object is /abc. Physical paths can also be specified as tuples where the first element is the empty string (representing the root), and every other element is a Unicode string, e.g. ('', 'abc'). Physical paths are also sometimes called "traversal paths".

physical root¶

The object returned by the application root factory. Unlike the virtual root of a request, it is not impacted by Virtual Hosting: it will always be the actual object returned by the root factory, never a subobject.

pip¶

The Python Packaging Authority's recommended tool for installing Python packages.

pipeline¶

The PasteDeploy term for a single configuration of a WSGI server, a WSGI application, with a set of middleware in-between.

pkg_resources¶

A module which ships with Setuptools that provides an API for addressing "asset files" within a Python package. Asset files are static files, template files, etc; basically anything non-Python-source that lives in a Python package can be considered a asset file.

参考

plaster¶

plaster is a library used by Pyramid which acts as an abstraction between command-line scripts and the file format used to load the WSGI components and application settings. By default Pyramid ships with the plaster_pastedeploy library installed which provides integrated support for loading a PasteDeploy INI file.

predicate¶

A test which returns True or False. Two different types of predicates exist in Pyramid: a view predicate and a route predicate. View predicates are attached to view configuration and route predicates are attached to route configuration.

predicate factory¶

A callable which is used by a third party during the registration of a route, view, or subscriber predicates to extend the configuration system. See Adding a Custom View, Route, or Subscriber Predicate for more information.

pregenerator¶

A pregenerator is a function associated by a developer with a route. It is called by route_url() in order to adjust the set of arguments passed to it by the user for special purposes. It will influence the URL returned by route_url(). See pyramid.interfaces.IRoutePregenerator for more information.

principal¶

A principal is a string representing an entity, typically a user or group. Principals are provided by an authentication policy. For example, if a user has the userid bob, and is a member of two groups named group foo and group bar, then the request might have information attached to it indicating that Bob was represented by three principals: bob, group foo and group bar.

project¶

Setuptools / Python packaging terminology. A directory on disk which contains a setup.py and / or pyproject.toml file and one or more Python packages. The project files contain metadata that allow the package(s) to be installed, distributed, and tested.

Pylons¶

A lightweight Python web framework and a predecessor of Pyramid.

PyPI¶

The Python Package Index, a collection of software available for Python.

PyPy¶

PyPy is an "alternative implementation of the Python language": http://pypy.org/

Pyramid Community Cookbook¶

Additional, community-based documentation for Pyramid which presents topical, practical uses of Pyramid: Pyramid Community Cookbook

pyramid_debugtoolbar¶

A Pyramid add-on which displays a helpful debug toolbar "on top of" HTML pages rendered by your application, displaying request, routing, and database information. pyramid_debugtoolbar is configured into the development.ini of all applications which use a Pyramid cookiecutter. For more information, see https://docs.pylonsproject.org/projects/pyramid_debugtoolbar/en/latest/.

pyramid_exclog¶

A package which logs Pyramid application exception (error) information to a standard Python logger. This add-on is most useful when used in production applications, because the logger can be configured to log to a file, to Unix syslog, to the Windows Event Log, or even to email. See its documentation.

pyramid_handlers¶

An add-on package which allows Pyramid users to create classes that are analogues of Pylons 1 "controllers". See https://docs.pylonsproject.org/projects/pyramid_handlers/en/latest/.

pyramid_jinja2¶

Jinja2 templating system bindings for Pyramid, documented at https://docs.pylonsproject.org/projects/pyramid_jinja2/en/latest/. This package also includes a scaffold named pyramid_jinja2_starter, which creates an application package based on the Jinja2 templating system.

pyramid_redis_sessions¶

A package by Eric Rasmussen which allows you to store Pyramid session data in a Redis database. See https://pypi.org/project/pyramid_redis_sessions/ for more information.

pyramid_zcml¶

An add-on package to Pyramid which allows applications to be configured via ZCML. It is available on PyPI. If you use pyramid_zcml, you can use ZCML as an alternative to imperative configuration or configuration decoration.

Python¶

The programming language in which Pyramid is written.

Python Packaging Authority¶

The Python Packaging Authority (PyPA) is a working group that maintains many of the relevant projects in Python packaging.

renderer¶

A serializer which converts non-Response return values from a view into a string, and ultimately into a response, usually through view configuration. Using a renderer can make writing views that require templating or other serialization, like JSON, less tedious. See Writing View Callables Which Use a Renderer for more information.

renderer factory¶

A factory which creates a renderer. See Adding and Changing Renderers for more information.

renderer globals¶

Values injected as names into a renderer by a pyramid.event.BeforeRender event.

Repoze¶

"Repoze" is essentially a "brand" of software developed by Agendaless Consulting and a set of contributors. The term has no special intrinsic meaning. The project's website has more information. The software developed "under the brand" is available in a Subversion repository. Pyramid was originally known as repoze.bfg.

repoze.catalog¶

An indexing and search facility (fielded and full-text) based on zope.index. See the documentation for more information.

repoze.lemonade¶

Zope2 CMF-like data structures and helper facilities for CA-and-ZODB-based applications useful within Pyramid applications.

repoze.who¶

Authentication middleware for WSGI applications. It can be used by Pyramid to provide authentication information.

repoze.workflow¶

Barebones workflow for Python apps . It can be used by Pyramid to form a workflow system.

request¶

An object that represents an HTTP request, usually an instance of the pyramid.request.Request class. See Request and Response Objects (narrative) and pyramid.request (API documentation) for information about request objects.

request factory¶

An object which, provided a WSGI environment as a single positional argument, returns a Pyramid-compatible request.

request type¶

An attribute of a request that allows for specialization of view invocation based on arbitrary categorization. The every request object that Pyramid generates and manipulates has one or more interface objects attached to it. The default interface attached to a request object is pyramid.interfaces.IRequest.

resource¶

An object representing a node in the resource tree of an application. If traversal is used, a resource is an element in the resource tree traversed by the system. When traversal is used, a resource becomes the context of a view. If URL dispatch is used, a single resource is generated for each request and is used as the context resource of a view.

Resource Location¶

The act of locating a context resource given a request. Traversal and URL dispatch are the resource location subsystems used by Pyramid.

resource tree¶

A nested set of dictionary-like objects, each of which is a resource. The act of traversal uses the resource tree to find a context resource.

response¶

An object returned by a view callable that represents response data returned to the requesting user agent. It must implement the pyramid.interfaces.IResponse interface. A response object is typically an instance of the pyramid.response.Response class or a subclass such as pyramid.httpexceptions.HTTPFound. See Request and Response Objects for information about response objects.

response adapter¶

A callable which accepts an arbitrary object and "converts" it to a pyramid.response.Response object. See Changing How Pyramid Treats View Responses for more information.

response callback¶

A user-defined callback executed by the router at a point after a response object is successfully created.

参考

See also URL dispatch.

route configuration¶

Route configuration is the act of associating request parameters with a particular route using pattern matching and route predicate statements. See URL Dispatch for more information about route configuration.

route predicate¶

An argument to a route configuration which implies a value that evaluates to True or False for a given request. All predicates attached to a route configuration must evaluate to True for the associated route to "match" the current request. If a route does not match the current request, the next route (in definition order) is attempted.

route prefix¶

A route prefix is a path prefix that is prepended to any routes that are configured while it is active. A route prefix can be set via pyramid.config.Configurator.include() or pyramid.config.Configurator.route_prefix_context().

router¶

The WSGI application created when you start a Pyramid application. The router intercepts requests, invokes traversal and/or URL dispatch, calls view functions, and returns responses to the WSGI server on behalf of your Pyramid application.

Routes¶

A system by Ben Bangert which parses URLs and compares them against a number of user defined mappings. The URL pattern matching syntax in Pyramid is inspired by the Routes syntax (which was inspired by Ruby On Rails pattern syntax).

routes mapper¶

An object which compares path information from a request to an ordered set of route patterns. See URL Dispatch.

scan¶

The term used by Pyramid to define the process of importing and examining all code in a Python package or module for configuration decoration.

security policy¶

A security policy in Pyramid terms is an object implementing the pyramid.interfaces.ISecurityPolicy API which identifies the user associated with the current request (perhaps via a cookie or Authorization header) and determines whether or not that user is permitted to access the requested resource.

session¶

A namespace that is valid for some period of continual activity that can be used to represent a user's interaction with a web application.

session factory¶

A callable, which, when called with a single argument named request (a request object), returns a session object. See Using the Default Session Factory, Using Alternate Session Factories and pyramid.config.Configurator.set_session_factory() for more information.

settings¶

Settings control the runtime behavior of a Pyramid application. They are the aggregation of configuration file declarations, process environment values, other additions generated by Pyramid or its add-ons and tweens, and values produced by your own code. Settings are collected at application startup. They can affect all the components which make up the the application. Pyramid itself, any tweens or Pyramid add-ons used, and your own code may reference and act on settings.

Setuptools¶

Setuptools builds on Python's distutils to provide easier building, distribution, and installation of libraries and applications.

side effect¶

A statement or function has a side effect when it changes a value outside its own scope. Put another way, if one can observe the change made by a function from outside that function, it has a side effect.

singleton¶

A singleton is a class which will only ever have one instance. As there is only one, it is shared by all other code. This makes it an example of global state.

Using a singleton is considered a poor design choice. As mutable global state, it can be changed by any other code, and so the values it represents cannot be reasoned about or tested properly.

SQLAlchemy¶

SQLAlchemy is an object relational mapper used in tutorials within this documentation.

subpath¶

A list of element "left over" after the router has performed a successful traversal to a view. The subpath is a sequence of strings, e.g. ['left', 'over', 'names']. Within Pyramid applications that use URL dispatch rather than traversal, you can use *subpath in the route pattern to influence the subpath. See Using *subpath in a Route Pattern for more information.

subscriber¶

A callable which receives an event. A callable becomes a subscriber via imperative configuration or via configuration decoration. See Using Events for more information.

template¶

A file with replaceable parts that is capable of representing some text, XML, or HTML when rendered.

thread local¶

A thread-local variable is one which is essentially a global variable in terms of how it is accessed and treated, however, each thread used by the application may have a different value for this same "global" variable. Pyramid uses a small number of thread local variables, as described in Thread Locals.

参考

See also the stdlib documentation for more information.

Translation Context¶

A string representing the "context" in which a translation was made within a given translation domain. See the gettext documentation, 11.2.5 Using contexts for solving ambiguities for more information.

Translation Directory¶

A translation directory is a gettext translation directory. It contains language folders, which themselves contain LC_MESSAGES folders, which contain .mo files. Each .mo file represents a set of translations for a language in a translation domain. The name of the .mo file (minus the .mo extension) is the translation domain name.

Translation Domain¶

A string representing the "context" in which a translation was made. For example the word "java" might be translated differently if the translation domain is "programming-languages" than would be if the translation domain was "coffee". A translation domain is represented by a collection of .mo files within one or more translation directory directories.

Translation String¶

An instance of pyramid.i18n.TranslationString, which is a class that behaves like a string, but has several extra attributes such as domain, msgid, and mapping for use during translation. Translation strings are usually created by hand within software, but are sometimes created on the behalf of the system for automatic template translation. For more information, see Internationalization and Localization.

Translator¶

A callable which receives a translation string and returns a translated string for the purposes of internationalization. A localizer supplies a translator to a Pyramid application accessible via its translate method.

traversal¶

The act of descending "up" a tree of resource objects from a root resource in order to find a context resource. The Pyramid router performs traversal of resource objects when a root factory is specified. See the Traversal chapter for more information. Traversal can be performed instead of URL dispatch or can be combined with URL dispatch. See Combining Traversal and URL Dispatch for more information about combining traversal and URL dispatch (advanced).

truthy string¶

A string represeting a value of True. Acceptable values are t, true, y, yes, on and 1.

tween¶

A bit of code that sits between the Pyramid router's main request handling function and the upstream WSGI component that uses Pyramid as its 'app'. The word "tween" is a contraction of "between". A tween may be used by Pyramid framework extensions, to provide, for example, Pyramid-specific view timing support, bookkeeping code that examines exceptions before they are returned to the upstream WSGI application, or a variety of other features. Tweens behave a bit like WSGI middleware but they have the benefit of running in a context in which they have access to the Pyramid application registry as well as the Pyramid rendering machinery. See Registering Tweens.

URL dispatch¶

An alternative to traversal as a mechanism for locating a context resource for a view. When you use a route in your Pyramid application via a route configuration, you are using URL dispatch. See the URL Dispatch for more information.

userid¶

A userid is the string representation of an identity. Just like the identity, it should identify the user associated with the current request. Oftentimes this is the ID of the user object in a database.

Venusian¶

Venusian is a library which allows framework authors to defer decorator actions. Instead of taking actions when a function (or class) decorator is executed at import time, the action usually taken by the decorator is deferred until a separate "scan" phase. Pyramid relies on Venusian to provide a basis for its scan feature.

venv¶

The Python Packaging Authority's recommended tool for creating virtual environments on Python 3.3 and greater.

Note: whenever you encounter commands prefixed with $VENV (Unix) or %VENV (Windows), know that that is the environment variable whose value is the root of the virtual environment in question.

view¶

Common vernacular for a view callable.

view callable¶

A "view callable" is a callable Python object which is associated with a view configuration; it returns a response object . A view callable accepts a single argument: request, which will be an instance of a request object. An alternate calling convention allows a view to be defined as a callable which accepts a pair of arguments: context and request: this calling convention is useful for traversal-based applications in which a context is always very important. A view callable is the primary mechanism by which a developer writes user interface code within Pyramid. See Views for more information about Pyramid view callables.

view configuration¶

View configuration is the act of associating a view callable with configuration information. This configuration information helps map a given request to a particular view callable and it can influence the response of a view callable. Pyramid views can be configured via imperative configuration, or by a special @view_config decorator coupled with a scan. See View Configuration for more information about view configuration.

view deriver¶

A view deriver is a composable component of the view pipeline which is used to create a view callable. A view deriver is a callable implementing the pyramid.interfaces.IViewDeriver interface. Examples of built-in derivers including view mapper, the permission checker, and applying a renderer to a dictionary returned from the view.

View handler¶

A view handler ties together pyramid.config.Configurator.add_route() and pyramid.config.Configurator.add_view() to make it more convenient to register a collection of views as a single class when using URL dispatch. View handlers ship as part of the pyramid_handlers add-on package.

View Lookup¶

The act of finding and invoking the "best" view callable, given a request and a context resource.

view mapper¶

A view mapper is a class which implements the pyramid.interfaces.IViewMapperFactory interface, which performs view argument and return value mapping. This is a plug point for extension builders, not normally used by "civilians".

view name¶

The "URL name" of a view, e.g index.html. If a view is configured without a name, its name is considered to be the empty string (which implies the default view).

view predicate¶

An argument to a view configuration which evaluates to True or False for a given request. All predicates attached to a view configuration must evaluate to true for the associated view to be considered as a possible callable for a given request.

virtual environment¶

An isolated Python environment that allows packages to be installed for use by a particular application, rather than being installed system wide.

virtual root¶

A resource object representing the "virtual" root of a request; this is typically the physical root object unless Virtual Hosting is in use.

virtualenv¶

The virtualenv tool that allows one to create virtual environments. In Python 3.3 and greater, venv is the preferred tool.

Note: whenever you encounter commands prefixed with $VENV (Unix) or %VENV (Windows), know that that is the environment variable whose value is the root of the virtual environment in question.

Waitress¶

A WSGI server that runs on Unix and Windows under Python 2.7+ and Python 3.3+. Projects generated via Pyramid cookiecutters use Waitress as a WGSI server. See https://docs.pylonsproject.org/projects/waitress/en/latest/ for detailed information.

WebOb¶

WebOb is a WSGI request/response library created by Ian Bicking.

WebTest¶

WebTest is a package which can help you write functional tests for your WSGI application.

WSGI¶

Web Server Gateway Interface. This is a Python standard for connecting web applications to web servers, similar to the concept of Java Servlets. Pyramid requires that your application be served as a WSGI application.

ZCML¶

Zope Configuration Markup Language, an XML dialect used by Zope and pyramid_zcml for configuration tasks.

ZODB¶

Zope Object Database, a persistent Python object store.

Zope¶

The Z Object Publishing Framework, a full-featured Python web framework.

Zope Component Architecture¶

The Zope Component Architecture (aka ZCA) is a system which allows for application pluggability and complex dispatching based on objects which implement an interface. Pyramid uses the ZCA "under the hood" to perform view dispatching and other application configuration tasks.

ZPT¶

The Zope Page Template templating language.