> One specific Python/APR divide I'm looking at is the APR "pool"
> mechanism. Passing pools about is very tedious and verbose. I
> understand the logic behind it, though! One possible API simplification
> that might help would be to have all pool parameters passed by keyword
> in Python, and then make a Python function decorator that adds a pool=
> keyword argument to a function, and automatically pulls its value from
> the caller's namespace if it isn't provided explicitly. Then, you could
> have the desired semantics for regular usage "by default", and
> explicitly create and manage loop subpools where necessary. Thoughts?
>
While it's early, and I haven't thought of all possible problems in this
approach (noting at the same time that it is more or less what we do
right now in C explicitly), the main one that pops out to me is the
python version requirement (IE decorators are 2.4+).
I'm sure you can work around this with explicit proxying or something.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 2 14:26:37 2006