string.
How about to re expose ``pyramid.traversal.model_path`` as
``pyramid.url.model_path``? I think it is less confusing to find out
all URL generation functions in one scope, isn't it?
--
Andrey Popp
phone: +7 911 740 24 91
e-mail: 8may...@gmail.com
--
You received this message because y
Hello,
it's looking just great!
How do you think, can this behavior be extracted into some pattern for
imperative configuration? I would like to have this in my toolchain in addition
to zope.configuration.
--
Andrey Popp
On Thursday, December 9, 2010 at 11:19 AM, Chris McDonough
ation nor to resource, nor to model, but can provide
good examples as mapping from application locations to domain models.
--
Andrey Popp
phone: +7 911 740 24 91
e-mail: 8may...@gmail.com
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" grou
rce. For example one can make one
resource available via different URLs (read locations) with different
views.
--
Andrey Popp
phone: +7 911 740 24 91
e-mail: 8may...@gmail.com
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post t
Hello,
I've just noticed[1] the adding of 'add_directive' method to 'Configurator'
which is allow to extend it with configuration methods. But I have some
questions:
1. Isn't this way is not very documentable? I mean, how would framework
extenders document methods, they've added to 'Config
On Feb 22, 2011, at 12:12 PM, Chris Withers wrote:
> If, say, I instantiate this user in the authentication middlewear, where's
> there "right" place to put this user object so that I don't have to
> instantiate it again when I need it for the authentication and authorization
> policies?
You c
Hello,
On Feb 27, 2011, at 10:40 PM, Chris Withers wrote:
> I'm writing a SQLAlchemy SessionExtension based on this pattern:
>
> http://www.sqlalchemy.org/trac/browser/examples/versioning/history_meta.py?rev=7253:3ef75b251d06#L171
>
> So, in the listener, I want to record the user that made the
Another approach is using separate repositories for storing data and revision
history, it can be implemented as events, I think Tres Seaver was talking about
that in this thread:
some_obj = some_objects.get(123)
user = request.user
# mutate some_obj
event = SomeObjectChanged(some_obj, u
> The event_manager could be ZCA event API. You could also move event-firing
> logic inside subclass of class of some_objects repository:
Oh, sorry, I was thought of wrapping repository inside versioning repository
proxy, not subclassing. :-)
--
You received this message because you are subsc
Hello Tres,
> FWIW, repoze.who 2.0 explicitly works to enable / ease using the
> machinery where needed in the app by exposing the configured plugins via
> an API (the login and logout views are the obvious consumers). It also
> retainis the flexibility of middleware for enforcing policies.
sorr
Hello,
On Mar 13, 2011, at 3:29 PM, Mike Orr wrote:
> - Replace the INI file with an YAML file?
YAML is not as good as it can be for config file format:
* It has slow parsers.
* There's risk of bloating YAML file with Python type annotations (tags),
e.g. !!bool, !!python/tuple when deali
> Added to the list, but can you specify what exactly you want this
> admin interface to do? What does "persistent" and "agnostic" mean in
> an admin interface?
Sorry, I mean persistence-agnostic -- interface should not be targeted to
specific relational databases (like django.contrib.admin do), i
12 matches
Mail list logo
