Hi Chris,

Thank you very much for the new release!

Is it possible to sync the flash functions to pyramid_beaker? I've
tried to look into pyramid_beaker myself but haven't figured out how
to jam pyramid session.py's @manage_accessed in...

Jerry

On Dec 28, 6:59 am, Chris McDonough <chr...@plope.com> wrote:
> Hi folks,
>
> I've just made a Pyramid 1.0a8 release.  It implements features and
> documentation topics that were previously on the 1.0 "must have" list.
>
> You can install it via:
>
>   easy_install pyramid
>
> Or update an existing installation via:
>
>   easy_install -U pyramid
>
> The docs athttp://docs.pylonshq.com/pyramid/dev/index.htmlwill be
> updated shortly (they may still point at the docs for 1.0a7 when you
> receive this).
>
> The change log follows:
>
> 1.0a8 (2010-12-27)
> ==================
>
> Bug Fixes
> ---------
>
> - The name ``registry`` was not available in the ``paster pshell``
>   environment under IPython.
>
> Features
> --------
>
> - If a resource implements a ``__resource_url__`` method, it will be
>   called as the result of invoking the ``pyramid.url.resource_url``
>   function to generate a URL, overriding the default logic.  See the
>   new "Generating The URL Of A Resource" section within the Resources
>   narrative chapter.
>
> - Added flash messaging, as described in the "Flash Messaging"
>   narrative documentation chapter.
>
> - Added CSRF token generation, as described in the narrative chapter
>   entitled "Preventing Cross-Site Request Forgery Attacks".
>
> - Prevent misunderstanding of how the ``view`` and ``view_permission``
>   arguments to add_route work by raising an exception during
>   configuration if view-related arguments exist but no ``view``
>   argument is passed.
>
> - Add ``paster proute`` command which displays a summary of the
>   routing table.  See the narrative documentation section within the
>   "URL Dispatch" chapter entitled "Displaying All Application Routes".
>
> Paster Templates
> ----------------
>
> - The ``pyramid_zodb`` Paster template no longer employs ZCML.
>   Instead, it is based on scanning.
>
> Documentation
> -------------
>
> - Added "Generating The URL Of A Resource" section to the Resources
>   narrative chapter (includes information about overriding URL
>   generation using ``__resource_url__``).
>
> - Added "Generating the Path To a Resource" section to the Resources
>   narrative chapter.
>
> - Added "Finding a Resource by Path" section to the Resources
>   narrative chapter.
>
> - Added "Obtaining the Lineage of a Resource" to the Resources
>   narrative chapter.
>
> - Added "Determining if a Resource is In The Lineage of Another
>   Resource" to Resources narrative chapter.
>
> - Added "Finding the Root Resource" to Resources narrative chapter.
>
> - Added "Finding a Resource With a Class or Interface in Lineage" to
>   Resources narrative chapter.
>
> - Added a "Flash Messaging" narrative documentation chapter.
>
> - Added a narrative chapter entitled "Preventing Cross-Site Request
>   Forgery Attacks".
>
> - Changed the "ZODB + Traversal Wiki Tutorial" based on changes to
>   ``pyramid_zodb`` Paster template.
>
> - Added "Advanced Configuration" narrative chapter which documents how
>   to deal with configuration conflicts, two-phase configuration,
>   ``include`` and ``commit``.
>
> - Fix API documentation rendering for ``pyramid.view.static``
>
> - Add "Pyramid Provides More Than One Way to Do It" to Design Defense
>   documentation.
>
> - Changed "Static Assets" narrative chapter: clarify that ``name``
>   represents a prefix unless it's a URL, added an example of a
>   root-relative static view fallback for URL dispatch, added an
>   example of creating a simple view that returns the body of a file.
>
> - Move ZCML usage in Hooks chapter to Declarative Configuration
>   chapter.
>
> - Merge "Static Assets" chapter into the "Assets" chapter.
>
> - Added narrative documentation section within the "URL Dispatch"
>   chapter entitled "Displaying All Application Routes" (for ``paster
>   proutes`` command).

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To post to this group, send email to pylons-de...@googlegroups.com.
To unsubscribe from this group, send email to 
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/pylons-devel?hl=en.

Reply via email to