Pyramid 1.2.6 and 1.3a4 have been released.
1.2.6 is a minor release in the 1.2 series. It has bug fixes and some
backwards incompatibilities.
1.3a4 is another alpha in the 1.3 series. It shares many of the same
bugfixes as those released in 1.2.6 and has the same backwards
incompatibilities.
Here's what happened in 1.2.6:
1.2.6 (2012-01-05)
==================
- Literal portions of route patterns were not URL-quoted when
``route_url`` or ``route_path`` was used to generate a URL or
path.
- The result of ``route_path`` or ``route_url`` might have been
``unicode`` or ``str`` depending on the input. It is now
guaranteed to always be ``str``.
- URL matching when the pattern contained non-ASCII characters in
literal parts was indeterminate. Now the pattern supplied to
``add_route`` is assumed to be either: a ``unicode`` value, or a
``str`` value that contains only ASCII characters. If you now
want to match the path info from a URL that contains high order
characters, you can pass the Unicode representation of the
decoded path portion in the pattern.
- When using a ``traverse=`` route predicate, traversal would fail
with a URLDecodeError if there were any high-order characters in
the traversal pattern or in the matched dynamic segments.
- Using a dynamic segment named ``traverse`` in a route pattern
like this::
config.add_route('trav_route', 'traversal/{traverse:.*}')
Would cause a ``UnicodeDecodeError`` when the route was matched
and the matched portion of the URL contained any high-order
characters. See https://github.com/Pylons/pyramid/issues/385 .
- When using a ``*traverse`` stararg in a route pattern, a URL
that matched that possessed a ``@@`` in its name (signifying a
view name) would be inappropriately quoted by the traversal
machinery during traversal, resulting in the view not being
found properly. See https://github.com/Pylons/pyramid/issues/382
and https://github.com/Pylons/pyramid/issues/375 .
Backwards Incompatibilities
---------------------------
- String values passed to ``route_url`` or ``route_path`` that are
meant to replace "remainder" matches will now be URL-quoted
except for embedded slashes. For example::
config.add_route('remain', '/foo*remainder')
request.route_path('remain', remainder='abc / def')
# -> '/foo/abc%20/%20def'
Previously string values passed as remainder replacements were
tacked on untouched, without any URL-quoting. But this doesn't
really work logically if the value passed is Unicode (raw
unicode cannot be placed in a URL or in a path) and it is
inconsistent with the rest of the URL generation machinery if
the value is a string (it won't be quoted unless by the caller).
Some folks will have been relying on the older behavior to tack
on query string elements and anchor portions of the URL; sorry,
you'll need to change your code to use the ``_query`` and/or
``_anchor`` arguments to ``route_path`` or ``route_url`` to do
this now.
- If you pass a bytestring that contains non-ASCII characters to
``add_route`` as a pattern, it will now fail at startup time.
Use Unicode instead.
Here's what happened in 1.3a4:
1.3a4 (2012-01-05)
==================
Features
--------
- New API: ``pyramid.request.Request.set_property``. Add lazy
property descriptors to a request without changing the request
factory. New properties may be reified, effectively caching the
value for the lifetime of the instance. Common use-cases for
this would be to get a database connection for the request or
identify the current user.
- Use the ``waitress`` WSGI server instead of ``wsgiref`` in
scaffolding.
Bug Fixes
---------
- The documentation of ``pyramid.events.subscriber`` indicated
that using it as a decorator with no arguments like this::
@subscriber()
def somefunc(event):
pass
Would register ``somefunc`` to receive all events sent via the
registry, but this was untrue. Instead, it would receive no
events at all. This has now been fixed and the code matches the
documentation. See also
https://github.com/Pylons/pyramid/issues/386
- Literal portions of route patterns were not URL-quoted when
``route_url`` or ``route_path`` was used to generate a URL or
path.
- The result of ``route_path`` or ``route_url`` might have been
``unicode`` or ``str`` depending on the input. It is now
guaranteed to always be ``str``.
- URL matching when the pattern contained non-ASCII characters in
literal parts was indeterminate. Now the pattern supplied to
``add_route`` is assumed to be either: a ``unicode`` value, or a
``str`` value that contains only ASCII characters. If you now
want to match the path info from a URL that contains high order
characters, you can pass the Unicode representation of the
decoded path portion in the pattern.
- When using a ``traverse=`` route predicate, traversal would fail
with a URLDecodeError if there were any high-order characters in
the traversal pattern or in the matched dynamic segments.
- Using a dynamic segment named ``traverse`` in a route pattern
like this::
config.add_route('trav_route', 'traversal/{traverse:.*}')
Would cause a ``UnicodeDecodeError`` when the route was matched
and the matched portion of the URL contained any high-order
characters. See https://github.com/Pylons/pyramid/issues/385 .
- When using a ``*traverse`` stararg in a route pattern, a URL
that matched that possessed a ``@@`` in its name (signifying a
view name) would be inappropriately quoted by the traversal
machinery during traversal, resulting in the view not being
found properly. See https://github.com/Pylons/pyramid/issues/382
and https://github.com/Pylons/pyramid/issues/375 .
Backwards Incompatibilities
---------------------------
- String values passed to ``route_url`` or ``route_path`` that are
meant to replace "remainder" matches will now be URL-quoted
except for embedded slashes. For example::
config.add_route('remain', '/foo*remainder')
request.route_path('remain', remainder='abc / def')
# -> '/foo/abc%20/%20def'
Previously string values passed as remainder replacements were
tacked on untouched, without any URL-quoting. But this doesn't
really work logically if the value passed is Unicode (raw
unicode cannot be placed in a URL or in a path) and it is
inconsistent with the rest of the URL generation machinery if
the value is a string (it won't be quoted unless by the caller).
Some folks will have been relying on the older behavior to tack
on query string elements and anchor portions of the URL; sorry,
you'll need to change your code to use the ``_query`` and/or
``_anchor`` arguments to ``route_path`` or ``route_url`` to do
this now.
- If you pass a bytestring that contains non-ASCII characters to
``add_route`` as a pattern, it will now fail at startup time.
Use Unicode instead.
The documentation for the 1.2.6 release is available at
http://docs.pylonsproject.org/projects/pyramid/en/1.2-branch/
The documentation for the 1.3a4 release is available at
http://docs.pylonsproject.org/projects/pyramid/en/1.3-branch/
A detailed "What's New in Pyramid 1.3" document is available at
http://docs.pylonsproject.org/projects/pyramid/en/1.3-branch/whatsnew-1.3.html
You can install 1.2.6 via PyPI:
easy_install Pyramid==1.2.6
Or 1.3a4:
easy_install Pyramid==1.3a4
Enjoy, and please report any issues you find to the issue tracker at
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 [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.
