Thanks again! =) iain
On Thu, Oct 25, 2012 at 10:56 PM, Chris McDonough <[email protected]> wrote: > Pyramid 1.4a3 has been released. Here's what happened since the last > release in the 1.4 series (1.4a2): > > 1.4a3 (2012-10-26) > ================== > > > Bug Fixes > --------- > > - The match_param predicate's text method was fixed to sort its > values. Part of > https://github.com/Pylons/**pyramid/pull/705<https://github.com/Pylons/pyramid/pull/705> > > - 1.4a ``pyramid.scripting.prepare`` behaved differently than 1.3 > series function of same name. In particular, if passed a request, > it would not set the ``registry`` attribute of the request like > 1.3 did. A symptom would be that passing a request to > ``pyramid.paster.bootstrap`` (which uses the function) that did > not have a ``registry`` attribute could assume that the registry > would be attached to the request by Pyramid. This assumption > could be made in 1.3, but not in 1.4. The assumption can now be > made in 1.4 too (a registry is attached to a request passed to > bootstrap or prepare). > > - When registering a view configuration that named a Chameleon ZPT > renderer with a macro name in it > (e.g. ``renderer='some/template#some**macro.pt <http://somemacro.pt>``) > as well as a view > configuration without a macro name it it that pointed to the same > template (e.g. ``renderer='some/template.pt'`**`), internal caching > could confuse the two, and your code might have rendered one > instead of the other. > > Features > -------- > > - Allow multiple values to be specified to the ``request_param`` > view/route predicate as a sequence. Previously only a single > string value was allowed. See > > https://github.com/Pylons/**pyramid/pull/705<https://github.com/Pylons/pyramid/pull/705> > > - Comments with references to documentation sections placed in > scaffold ``.ini`` files. > > - Added an HTTP Basic authentication policy at > ``pyramid.authentication.**BasicAuthAuthenticationPolicy`**`. > > - The Configurator ``testing_securitypolicy`` method now returns the > policy object it creates. > > - The Configurator ``testing_securitypolicy`` method accepts two new > arguments: ``remember_result`` and ``forget_result``. If > supplied, these values influence the result of the policy's > ``remember`` and ``forget`` methods, respectively. > > - The DummySecurityPolicy created by ``testing_securitypolicy`` now > sets a ``forgotten`` value on the policy (the value ``True``) when > its ``forget`` method is called. > > - The DummySecurityPolicy created by ``testing_securitypolicy`` now > sets a ``remembered`` value on the policy, which is the value of > the ``principal`` argument it's called with when its ``remember`` > method is called. > > - New ``physical_path`` view predicate. If specified, this value > should be a string or a tuple representing the physical traversal > path of the context found via traversal for this predicate to > match as true. For example: ``physical_path='/'`` or > ``physical_path='/a/b/c'`` or ``physical_path=('', 'a', 'b', > 'c')``. This is not a path prefix match or a regex, it's a > whole-path match. It's useful when you want to always potentially > show a view when some object is traversed to, but you can't be > sure about what kind of object it will be, so you can't use the > ``context`` predicate. The individual path elements inbetween > slash characters or in tuple elements should be the Unicode > representation of the name of the resource and should not be > encoded in any way. > > A detailed "What's New in Pyramid 1.4" document is available at > > > <http://docs.pylonsproject.**org/projects/pyramid/en/** > master/whatsnew-1.4.html<http://docs.pylonsproject.org/projects/pyramid/en/master/whatsnew-1.4.html> > > > > Pyramid 1.4a3 requires Python 2.6, 2.7, 3.2 or 3.3. > > The documentation for the release is available at > http://docs.pylonsproject.org/**projects/pyramid/en/1.4-**branch/<http://docs.pylonsproject.org/projects/pyramid/en/1.4-branch/>. > > You can install it via PyPI: > > easy_install Pyramid==1.4a3 > > Enjoy, and please report any issues you find to the issue tracker at > https://github.com/Pylons/**pyramid/issues<https://github.com/Pylons/pyramid/issues> > > Thanks! > > - C > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To post to this group, send email to > pylons-discuss@googlegroups.**com<[email protected]> > . > To unsubscribe from this group, send email to pylons-discuss+unsubscribe@* > *googlegroups.com <pylons-discuss%[email protected]>. > For more options, visit this group at http://groups.google.com/** > group/pylons-discuss?hl=en<http://groups.google.com/group/pylons-discuss?hl=en> > . > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
