summaryrefslogtreecommitdiff
path: root/docs/whatsnew-1.3.rst
AgeCommit message (Collapse)Author
2012-02-17docs rearranging / fixingChris McDonough
2012-02-17docs fixesChris McDonough
2012-02-17docs fixesChris McDonough
2012-02-17FeaturesChris McDonough
-------- - Add ``pyramid.config.Configurator.add_resource_url_adapter`` API method. See the Hooks narrative documentation section entitled "Changing How pyramid.request.Request.resource_url Generates a URL" for more information. This is not a new feature, it just provides an API for adding a resource url adapter without needing to use the ZCA API. - A new interface was added: ``pyramid.interfaces.IResourceURL``. An adapter implementing its interface can be used to override resource URL generation when ``request.resource_url`` is called. This interface replaces the now-deprecated ``pyramid.interfaces.IContextURL`` interface. - The dictionary passed to a resource's ``__resource_url__`` method (see "Overriding Resource URL Generation" in the "Resources" chapter) now contains an ``app_url`` key, representing the application URL generated during ``request.resource_url``. It represents a potentially customized URL prefix, containing potentially custom scheme, host and port information passed by the user to ``request.resource_url``. It should be used instead of ``request.application_url`` where necessary. - The ``request.resource_url`` API now accepts these arguments: ``app_url``, ``scheme``, ``host``, and ``port``. The app_url argument can be used to replace the URL prefix wholesale during url generation. The ``scheme``, ``host``, and ``port`` arguments can be used to replace the respective default values of ``request.application_url`` partially. - A new API named ``request.resource_path`` now exists. It works like ``request.resource_url`` but produces a relative URL rather than an absolute one. - The ``request.route_url`` API now accepts these arguments: ``_app_url``, ``_scheme``, ``_host``, and ``_port``. The ``_app_url`` argument can be used to replace the URL prefix wholesale during url generation. The ``_scheme``, ``_host``, and ``_port`` arguments can be used to replace the respective default values of ``request.application_url`` partially. Backwards Incompatibilities --------------------------- - The ``pyramid.interfaces.IContextURL`` interface has been deprecated. People have been instructed to use this to register a resource url adapter in the "Hooks" chapter to use to influence ``request.resource_url`` URL generation for resources found via custom traversers since Pyramid 1.0. The interface still exists and registering such an adapter still works, but this interface will be removed from the software after a few major Pyramid releases. You should replace it with an equivalent ``pyramid.interfaces.IResourceURL`` adapter, registered using the new ``pyramid.config.Configurator.add_resource_url_adapter`` API. A deprecation warning is now emitted when a ``pyramid.interfaces.IContextURL`` adapter is found when ``request.resource_url`` is called. Misc ---- - Change ``set_traverser`` API name to ``add_traverser``. Ref #438.
2012-02-15Use req instead of r for #413. It's more likely that somebody is already ↵Chris McDonough
passing something named r, and a template may depend on its existence or nonexistence to conditionalize rendering a bit of html.
2012-02-15- The system value ``r`` is now supplied to renderers as an alias forChris McDonough
``request``. This means that you can now, for example, in a template, do ``r.route_url(...)`` instead of ``request.route_url(...)``. Fixes #413.
2012-02-15update whatsnewChris McDonough
2012-02-09FeaturesChris McDonough
-------- - The ``scan`` method of a ``Configurator`` can be passed an ``ignore`` argument, which can be a string, a callable, or a list consisting of strings and/or callables. This feature allows submodules, subpackages, and global objects from being scanned. See http://readthedocs.org/docs/venusian/en/latest/#ignore-scan-argument for more information about how to use the ``ignore`` argument to ``scan``. Dependencies ------------ - Depend on ``venusian`` >= 1.0a3 to provide scan ``ignore`` support.
2012-02-08prep for 1.3a7Chris McDonough
2012-02-04Merge branch 'pull.421' into 1.3-branchMichael Merickel
2012-01-29Clarify Python 2 and 3 compatibility for tl;dr users.Steve Piercy
2012-01-20prep for 1.3a6Chris McDonough
2012-01-11Updated the changelogs.Michael Merickel
2012-01-05whatsnewChris McDonough
2012-01-02- Use the ``waitress`` WSGI server instead of ``wsgiref`` in scaffolding.Chris McDonough
2011-12-30Updated the changelog for Request.set_property.Michael Merickel
2011-12-16- Removed the "Running Pyramid on Google App Engine" tutorial from the mainChris McDonough
docs. It survives on in the Cookbook (http://docs.pylonsproject.org/projects/pyramid_cookbook/en/latest/gae.html). Rationale: it provides the correct info for the Python 2.5 version of GAE only, and this version of Pyramid does not support Python 2.5.
2011-12-15- Added a section named "Making Your Script into a Console Script" in theChris McDonough
"Command-Line Pyramid" chapter.
2011-12-15finish prequest featureChris McDonough
2011-12-14mention backports and fix incorrect info about being able to use paster ↵Chris McDonough
create for internal pyramid scaffolds
2011-12-14merge goodwill's changes from masterChris McDonough
2011-12-14Added in a warning in whats new 1.3 about wsgiref beign more strict about ↵michr
returning string headers where as paste.httpserver converted them implicitly.
2011-12-14- Changed scaffolding machinery around a bit to make it easier for people whoChris McDonough
want to have extension scaffolds that can work across Pyramid 1.0.X, 1.1.X, 1.2.X and 1.3.X. See the new "Creating Pyramid Scaffolds" chapter in the narrative documentation for more info. - Added an API docs chapter for ``pyramid.scaffolds``. - Added a narrative docs chapter named "Creating Pyramid Scaffolds". - The ``template_renderer`` method of ``pyramid.scaffolds.PyramidScaffold`` was renamed to ``render_template``. If you were overriding it, you're a bad person, because it wasn't an API before now. But we're nice so we're letting you know.
2011-12-14Flesh out new view_defaults feature and add docs, change notes, and add to ↵Chris McDonough
whatsnew.
2011-12-10remove double wordChris McDonough
2011-12-09Fixed typos & minor edits.Ronan Amicel
2011-12-09be more specificChris McDonough
2011-12-09mention setup.py develop failure on py32Chris McDonough
2011-12-09bumped toolbar versionChris McDonough
2011-12-09typoMichael Merickel
2011-12-09typoChris McDonough
2011-12-09gardenChris McDonough
2011-12-08- New APIs: ``pyramid.path.AssetResolver`` andChris McDonough
``pyramid.path.DottedNameResolver``. The former can be used to resolve asset specifications, the latter can be used to resolve dotted names to modules or packages.
2011-12-06gardenChris McDonough
2011-12-05- Removed the ``pyramid.renderers.renderer_from_name`` function. It has beenChris McDonough
deprecated since Pyramid 1.0, and was never an API.
2011-12-05add whatsnew-1.3; gardenChris McDonough
2010-10-25convert remainder of docs to use pyramid instead of repoze.bfgChris McDonough
2010-09-30work upChris McDonough
2010-09-15prep for 1.3a14Chris McDonough
2010-09-14gardeningChris McDonough
2010-09-14prep for 1.3a13Chris McDonough
2010-09-08prep for 1.3a12Chris McDonough
2010-09-06renderingsChris McDonough
2010-08-29Remove double entryWichert Akkerman
2010-08-23docs renderingsChris McDonough
2010-08-13- The newChris McDonough
:meth"`repoze.bfg.configuration.Configurator.absolute_resource_spec` method resolves a potentially relative :term:`resource specification` string into an absolute version.
2010-08-13- The Configurator now accepts a dotted name *string* to a package asChris McDonough
a ``package`` constructor argument. The ``package`` argument was previously required to be a package *object* (not a dotted name string). - The ``repoze.bfg.configuration.Configurator.with_package`` method was added. This method returns a new Configurator using the same application registry as the configurator object it is called upon. The new configurator is created afresh with its ``package`` constructor argument set to the value passed to ``with_package``. This feature will make it easier for future BFG versions to allow dotted names as arguments in places where currently only object references are allowed (the work to allow dotted names isntead of object references everywhere has not yet been done, however). - The ``repoze.bfg.configuration.Configurator.maybe_dotted`` method resolves a Python dotted name string supplied as its ``dotted`` argument to a global Python object. If the value cannot be resolved, a ``repoze.bfg.configuration.ConfigurationError`` is raised. If the value supplied as ``dotted`` is not a string, the value is returned unconditionally without any resolution attempted.
2010-08-08- New public interface: ``repoze.bfg.exceptions.IExceptionResponse``.Chris McDonough
This interface is provided by all internal exception classes (such as ``repoze.bfg.exceptions.NotFound`` and ``repoze.bfg.exceptions.Forbidden``), instances of which are both exception objects and can behave as WSGI response objects. This interface is made public so that exception classes which are also valid WSGI response factories can be configured to implement them or exception instances which are also or response instances can be configured to provide them. - New API class: ``repoze.bfg.view.AppendSlashNotFoundViewFactory`` (undoes previous custom_notfound_view on request passsed to append_slash_notfound_view). - Previously, two default view functions were registered at Configurator setup (one for ``repoze.bfg.exceptions.NotFound`` named ``default_notfound_view`` and one for ``repoze.bfg.exceptions.Forbidden`` named ``default_forbidden_view``) to render internal exception responses. Those default view functions have been removed, replaced with a generic default view function which is registered at Configurator setup for the ``repoze.bfg.interfaces.IExceptionResponse`` interface that simply returns the exception instance; the ``NotFound` and ``Forbidden`` classes are now still exception factories but they are also response factories which generate instances that implement the new ``repoze.bfg.interfaces.IExceptionResponse`` interface.
2010-08-07fix whatsnewChris McDonough
2010-08-01prep for 1.3a7Chris McDonough