Pyramid

Latest version: v2.0.2

Safety actively analyzes 685838 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 12 of 30

1.2b1

Not secure
==================

Bug Fixes
---------

- In ``bfg_routesalchemy``, ``bfg_alchemy`` paster templates and the
``bfgwiki2`` tutorial, clean up the SQLAlchemy connection by
registering a ``repoze.tm.after_end`` callback instead of relying on
a ``__del__`` method of a ``Cleanup`` class added to the WSGI
environment. The ``__del__`` strategy was fragile and caused
problems in the wild. Thanks to Daniel Holth for testing.

Features
--------

- Read logging configuration from PasteDeploy config file ``loggers``
section (and related) when ``paster bfgshell`` is invoked.

Documentation
-------------

- Major rework in preparation for book publication.

1.2a11

===================

Bug Fixes
---------

- Make ``paster bfgshell`` and ``paster create -t bfg_xxx`` work on
Jython (fix minor incompatibility with treatment of ``__doc__`` at
the class level).

- Updated dependency on ``WebOb`` to require a version which supports
features now used in tests.

Features
--------

- Jython compatibility (at least when repoze.bfg.jinja2 is used as the
templating engine; Chameleon does not work under Jython).

- Show the derived abspath of template resource specifications in the
traceback when a renderer template cannot be found.

- Show the original traceback when a Chameleon template cannot be
rendered due to a platform incompatibility.

1.2a10

===================

Features
--------

- The ``Configurator.add_view`` method now accepts an argument named
``context``. This is an alias for the older argument named
``for_``; it is preferred over ``for_``, but ``for_`` will continue
to be supported "forever".

- The ``view`` ZCML directive now accepts an attribute named
``context``. This is an alias for the older attribute named
``for``; it is preferred over ``for``, but ``for`` will continue to
be supported "forever".

- The ``Configurator.add_route`` method now accepts an argument named
``view_context``. This is an alias for the older argument named
``view_for``; it is preferred over ``view_for``, but ``view_for``
will continue to be supported "forever".

- The ``route`` ZCML directive now accepts an attribute named
``view_context``. This is an alias for the older attribute named
``view_for``; it is preferred over ``view_for``, but ``view_for``
will continue to be supported "forever".

Documentation and Paster Templates
----------------------------------

- LaTeX rendering tweaks.

- All uses of the ``Configurator.add_view`` method that used its
``for_`` argument now use the ``context`` argument instead.

- All uses of the ``Configurator.add_route`` method that used its
``view_for`` argument now use the ``view_context`` argument instead.

- All uses of the ``view`` ZCML directive that used its ``for``
attribute now use the ``context`` attribute instead.

- All uses of the ``route`` ZCML directive that used its ``view_for``
attribute now use the ``view_context`` attribute instead.

- Add a (minimal) tutorial dealing with use of ``repoze.catalog`` in a
``repoze.bfg`` application.

Documentation Licensing
-----------------------

- Loosen the documentation licensing to allow derivative works: it is
now offered under the `Creative Commons
Attribution-Noncommercial-Share Alike 3.0 United States License
<https://creativecommons.org/licenses/by-nc-sa/3.0/us/>`_. This is
only a documentation licensing change; the ``repoze.bfg`` software
continues to be offered under the Repoze Public License at
https://web.archive.org/web/20190401024809/http://repoze.org/license.html (BSD-like).

1.2a9

==================

Documentation Licensing
-----------------------

- The *documentation* (the result of ``make <html|latex|htmlhelp>``
within the ``docs`` directory) in this release is now offered under
the Creative Commons Attribution-Noncommercial-No Derivative Works
3.0 United States License as described by
https://creativecommons.org/licenses/by-nc-nd/3.0/us/ . This is only
a licensing change for the documentation; the ``repoze.bfg``
software continues to be offered under the Repoze Public License
at https://web.archive.org/web/20190401024809/http://repoze.org/license.html (BSD-like).

Documentation
-------------

- Added manual index entries to generated index.

- Document the previously existing (but non-API)
``repoze.bfg.configuration.Configurator.setup_registry`` method as
an official API of a ``Configurator``.

- Fix syntax errors in various documentation code blocks.

- Created new top-level documentation section: "ZCML Directives".
This section contains detailed ZCML directive information, some of
which was removed from various narrative chapters.

- The LaTeX rendering of the documentation has been improved.

- Added a "Fore-Matter" section with author, copyright, and licensing
information.

1.2a8

==================

Features
--------

- Add a ``**kw`` arg to the ``Configurator.add_settings`` API.

- Add ``hook_zca`` and ``unhook_zca`` methods to the ``Configurator``
API.

- The ``repoze.bfg.testing.setUp`` method now returns a
``Configurator`` instance which can be used to do further
configuration during unit tests.

Bug Fixes
---------

- The ``json`` renderer failed to set the response content type to
``application/json``. It now does, by setting
``request.response_content_type`` unless this attribute is already
set.

- The ``string`` renderer failed to set the response content type to
``text/plain``. It now does, by setting
``request.response_content_type`` unless this attribute is already
set.

Documentation
-------------

- General documentation improvements by using better Sphinx roles such
as "class", "func", "meth", and so on. This means that there are
many more hyperlinks pointing to API documentation for API
definitions in all narrative, tutorial, and API documentation
elements.

- Added a description of imperative configuration in various places
which only described ZCML configuration.

- A syntactical refreshing of various tutorials.

- Added the ``repoze.bfg.authentication``,
``repoze.bfg.authorization``, and ``repoze.bfg.interfaces`` modules
to API documentation.

Deprecations
------------

- The ``repoze.bfg.testing.registerRoutesMapper`` API (added in an
early 1.2 alpha) was deprecated. Its import now generates a
deprecation warning.

1.2a7

==================

Features
--------

- Add four new testing-related APIs to the
``repoze.bfg.configuration.Configurator`` class:
``testing_securitypolicy``, ``testing_models``,
``testing_add_subscriber``, and ``testing_add_template``. These
were added in order to provide more direct access to the
functionality of the ``repoze.bfg.testing`` APIs named
``registerDummySecurityPolicy``, ``registerModels``,
``registerEventListener``, and ``registerTemplateRenderer`` when a
configurator is used. The ``testing`` APIs named are nominally
deprecated (although they will likely remain around "forever", as
they are in heavy use in the wild).

- Add a new API to the ``repoze.bfg.configuration.Configurator``
class: ``add_settings``. This API can be used to add "settings"
(information returned within via the
``repoze.bfg.settings.get_settings`` API) after the configurator has
been initially set up. This is most useful for testing purposes.

- Add a ``custom_predicates`` argument to the ``Configurator``
``add_view`` method, the ``bfg_view`` decorator and the attribute
list of the ZCML ``view`` directive. If ``custom_predicates`` is
specified, it must be a sequence of predicate callables (a predicate
callable accepts two arguments: ``context`` and ``request`` and
returns ``True`` or ``False``). The associated view callable will
only be invoked if all custom predicates return ``True``. Use one
or more custom predicates when no existing predefined predicate is
useful. Predefined and custom predicates can be mixed freely.

- Add a ``custom_predicates`` argument to the ``Configurator``
``add_route`` and the attribute list of the ZCML ``route``
directive. If ``custom_predicates`` is specified, it must be a
sequence of predicate callables (a predicate callable accepts two
arguments: ``context`` and ``request`` and returns ``True`` or
``False``). The associated route will match will only be invoked if
all custom predicates return ``True``, else route matching
continues. Note that the value ``context`` will always be ``None``
when passed to a custom route predicate. Use one or more custom
predicates when no existing predefined predicate is useful.
Predefined and custom predicates can be mixed freely.

Internal
--------

- Remove the ``repoze.bfg.testing.registerTraverser`` function. This
function was never an API.

Documentation
-------------

- Doc-deprecated most helper functions in the ``repoze.bfg.testing``
module. These helper functions likely won't be removed any time
soon, nor will they generate a warning any time soon, due to their
heavy use in the wild, but equivalent behavior exists in methods of
a Configurator.

Page 12 of 30

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.