On 03/22/10 11:42, Shawn Walker wrote:
> On 03/22/10 12:10 PM, Virginia Wray wrote:
>> On 03/19/10 21:54, Shawn Walker wrote:
>>> On 03/12/10 06:39 PM, Virginia Wray wrote:
>>>> Hi -
>>>>
>>>> I've posted the second draft of the Logging design doc at:
>>>>
>>>> http://hub.opensolaris.org/bin/view/Project+caiman/Logging
>>>>
>>>> Select Loggingv1.2.pdf
>>>
>>> Overall, this is looking excellent. The level of detail is appreciated.
>>>
>>> I would note that one downside to using a C bridge to your python
>>> library is that it will create a Python runtime dependency for the
>>> application in question. However, I'd venture to guess that the
>>> majority of the consumers for this API will use Python and not C, so
>>> this may not matter.
>>>
>>> Others seemed to have covered the other things I saw, so I won't
>>> repeat what they've already said.
>>>
>>> Cheers,
>> Thanks for the feedback Shawn. The C bridges are necessary for a small
>> number of components that are written in C, but you are correct. The
>> majority are written in Python.
>> Do you foresee any issues because of the runtime dependencies ?
>
> One thing did just occur to me, and that would be that in the case of
> a C to Python bridge as you've mentioned here, any programs using that
> bridge will have an indirect dependency on the same version of python
> that the bridge is using.
>
> That also means that if the bridge changes what version of Python it's
> based on, it's possible the application will need to be recompiled
> against the new bridge.
>
> However, I suspect that python2.6 is going to have a relatively long
> life and since that's the version of Python you're starting on, this
> is probably a moot concern.
>
> Cheers,
ok. Thanks. I can make a note of that dependency in the design doc in
order to be complete.
--
Ginnie
