Hi, thanks for your feedback.
It's just a matter of the separation of concerns. The code I need it in
is confined to the model, defined in a "pluggable" model module. It's
not that I can't redesign the chain of calls in order to pass the
request object around, I was just looking at feasible alternatives to
the required refactoring if the request object was to be passed around.
.oO V Oo.
On 12/01/2011 06:31 PM, Iain Duncan wrote:
BTW, pyramid is pretty much designed so that you can eliminate all
magic globals and thread locals by keeping a locally passed reference
to request everywhere. I'm curious where you are finding it not
accessible? For us, we pass it into formencode validators as part of
the state variable, it's already in the root factories, available to
templates, and in any views. Where else do you have code that needs
the registry? ( curious, not saying you've necessarily done something
wrong )
thanks
Iain
--
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.
