pyramid - Pyramid web framework (fork of https://github.com/Pylons/pyramid).

Age	Commit message (Collapse)	Author
2013-01-29	Merge pull request #820 from tshepang/master	Tres Seaver
	some renderers and view API doc improvements
2013-01-29	Merge pull request #821 from tshepang/path	Tres Seaver
	some pyramid.path API doc improvements
2013-01-29	Merge pull request #822 from tshepang/session	Tres Seaver
	some pyramid.session API doc improvements
2013-01-29	replace 'note' with the more correct 'versionadded' directive	Tshepang Lekhonkhobe

2013-01-27	avoid needless repetition	Tshepang Lekhonkhobe
	These are already stated on the function definition.
2013-01-27	capitalize	Tshepang Lekhonkhobe

2013-01-27	add missing markup	Tshepang Lekhonkhobe

2013-01-27	capitalize	Tshepang Lekhonkhobe

2013-01-27	make use of 'versionadded' and 'deprecated' directives in pyramid.view	Tshepang Lekhonkhobe

2013-01-25	make path API docs a bit more concise	Tshepang Lekhonkhobe

2013-01-25	replace 'note' with 'versionadded'	Tshepang Lekhonkhobe

2013-01-25	be a little more concise	Tshepang Lekhonkhobe

2013-01-25	typo	Tshepang Lekhonkhobe

2013-01-19	user newer API in the example	Tshepang Lekhonkhobe

2013-01-16	add missing comma	Tshepang Lekhonkhobe

2013-01-14	Merge pull request #793 from ronnix/patch-4	Chris McDonough
	Fix forbidden_view_config docstring
2013-01-14	Merge pull request #794 from tshepang/flow	Chris McDonough
	improve flow
2013-01-14	Merge pull request #796 from tshepang/typos	Chris McDonough
	typo
2013-01-15	yet another grammar fix	Tshepang Lekhonkhobe

2013-01-15	improve flow	Tshepang Lekhonkhobe

2013-01-14	grammar	Tshepang Lekhonkhobe

2013-01-14	typo	Tshepang Lekhonkhobe

2013-01-14	Update pyramid/view.py	Ronan Amicel
	Fix example function name in forbidden_view_config docstring
2013-01-06	grammar	Tshepang Lekhonkhobe

2013-01-02	eliminate other repeated words	Tshepang Lekhonkhobe

2013-01-01	eliminate repeated "the" words	Tshepang Lekhonkhobe

2012-12-10	Merge pull request #738 from ppaez/pep8_scaffolds	Chris McDonough
	Improve pep8 compliance of scaffolds
2012-12-06	make _backframes work like _depth (but still leave undocumented)	Chris McDonough

2012-12-06	note custom_predicates deprecation	Chris McDonough

2012-12-06	Merge branch '1.4-branch' of github.com:Pylons/pyramid into 1.4-branch	Chris McDonough

2012-12-06	_depth argument to view_config is now relative to view_config	Michael Merickel
	This hides an implementation detail that view_config is at least 1 level away from user code.
2012-12-01	unused import	Chris McDonough

2012-11-29	make scaffolds pep8 compliant	Gael Pasgrimaud
	Conflicts: pyramid/scaffolds/alchemy/+package+/views.py_tmpl pyramid/scaffolds/alchemy/setup.py_tmpl Solved the two conflicts
2012-11-27	Merge pull request #732 from ppaez/transaction-dependency	Chris McDonough
	Transaction dependency in ZODB tutorial
2012-11-21	missed adding this file	Chris McDonough

2012-11-21	fix for py3	Chris McDonough

2012-11-21	add an integration test for the eventonly behavior	Chris McDonough

2012-11-21	- In order to normalize the relationship between event subscribers and	Chris McDonough
	subscriber predicates, we now allow both subscribers and subscriber predicates to accept only a single ``event`` argument even if they've been subscribed for notifications that involve multiple interfaces. Subscribers and subscriber predicates that accept only one argument will receive the first object passed to ``notify``; this is typically (but not always) the event object. The other objects involved in the subscription lookup will be discarded. For instance, if an event is sent by code like this:: registry.notify(event, context) In the past, in order to catch such an event, you were obligated to write and register an event subscriber that mentioned both the event and the context in its argument list:: @subscriber([SomeEvent, SomeContextType]) def subscriber(event, context): pass With the event-only feature you can now write an event subscriber that accepts only ``event`` even if it subscribes to multiple interfaces:: @subscriber([SomeEvent, SomeContextType]) def subscriber(event): # this will work! Note, however, that if the event object is not the first object in the call to ``notify``, you'll run into trouble. For example, if notify is called with the context argument first:: registry.notify(context, event) You won't be able to take advantage of the feature. It will "work", but the object received by your event handler won't be the event object, it will be the context object, which won't be very useful:: @subscriber([SomeContextType, SomeEvent]) def subscriber(event): # bzzt! you'll be getting the context here as ``event``, and it'll # be useless Existing multiple-argument subscribers continue to work without issue, so you should continue use those if your system notifies using multiple interfaces and the first interface is not the event interface. For example:: @subscriber([SomeContextType, SomeEvent]) def subscriber(context, event): # this will still work! The event-only feature makes it possible to use a subscriber predicate that accepts only a request argument within both multiple-interface subscriber registrations and single-interface subscriber registrations. In the past, if you had a subscriber predicate like this:: class RequestPathStartsWith(object): def __init__(self, val, config): self.val = val def text(self): return 'path_startswith = %s' % (self.val,) phash = text def __call__(self, event): return event.request.path.startswith(self.val) If you attempted to use the above predicate to condition a subscription that involved multiple interfaces, it would not work. You had to change it to accept the same arguments as the subscription itself. For example, you might have had to change its ``__call__`` method like so, adding a ``context`` argument:: def __call__(self, event, context): return event.request.path.startswith(self.val) With the event-only feature, you needn't make the change. Instead, you can write all predicates so they only accept ``event`` in their ``__call__`` and they'll be useful across all registrations for subscriptions that use an event as their first argument, even ones which accept more than just ``event``. However, the same caveat applies to predicates as to subscriptions: if you're subscribing to a multi-interface event, and the first interface is not the event interface, the predicate won't work properly. In such a case, you'll need to match the predicate ``__call__`` argument ordering and composition to the ordering of the interfaces. For example:: def __call__(self, context, event): return event.request.path.startswith(self.val) tl;dr: 1) Always use the event as the first argument to a multi-interface subscription and 2) Use only ``event`` in your subscriber and subscriber predicate parameter lists, no matter how many interfaces the subscriber is notified with, as long as the event object is the first argument passed to ``registry.notify``. This will result in the maximum amount of reusability of subscriber predicates.
2012-11-20	add transaction dependency to zodb scaffold	ericrasmussen

2012-11-20	Merge branch 'master' into sontek-fix_commands	Chris McDonough

2012-11-20	coverage	Chris McDonough

2012-11-20	Merge branch 'fix_commands' of git://github.com/sontek/pyramid into ↵	Chris McDonough
	sontek-fix_commands
2012-11-20	- Small microspeed enhancement which anticipates that a	Chris McDonough
	``pyramid.response.Response`` object is likely to be returned from a view. Some code is shortcut if the class of the object returned by a view is this class. A similar microoptimization was done to ``pyramid.request.Request.is_response``.
2012-11-18	- A failure when trying to locate the attribute ``__text__`` on route and view	Chris McDonough
	predicates existed when the ``debug_routematch`` setting was true or when the ``pviews`` command was used. See https://github.com/Pylons/pyramid/pull/727 Closes #727.
2012-11-14	Don't use a global mutable and updated the doc string to include options	John Anderson

2012-11-14	make an assertion in this test	Chris McDonough

2012-11-14	Merge branch 'fix_commands' of git://github.com/sontek/pyramid into ↵	Chris McDonough
	sontek-fix_commands
2012-11-14	ref #725; indicate how to join the result of render_view_to_iterable	Chris McDonough

2012-11-13	indicate render_view returns a bytestring (see #725)	Michael Merickel

2012-11-13	simplfied change as response.app_iter must contain bytes per pep 3333	Michael Merickel