On 03/17/10 14:43, Garrett D'Amore wrote:
> On 03/17/10 02:15 PM, Suresh Chandrasekharan wrote:
>> Thanks for the comments.
>>
>> If requirements exist, we can look into how to provide C bindings for
>> this python library later.
>
> I think you're probably approaching this backwards. With most other
> languages (not sure about Python), its usually easier to provide the
> underlying implementation in C, and add language bindings on top.
>
> In particular, I'd be really unhappy if accessing g11n services required
> a program written in C to bring in a Python runtime.
>
> - Garrett
>
> _______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc at opensolaris.org
The team proposed the following:
This library will be partly based on an opensource python package,
which's BSD licensed, named Babel (http://babel.edgewall.org/). Some
of APIs from Babel are used as the building block of a number of
locale services APIs. Others APIs are coded from scratch.
This library is targeted at the installer and system maintenance
utilities. What applications are you proposing to be written in C
that would also perform these functions?
What you're asking is that the project team abandon attempts to leverage
Babel, and code everything from scratch in C in case someone wants to
write an application or utility that needs such functionality in C later
on. In addition, you're mandating that the team (or the
original requesters) also develop python bindings to the new
C library.
What value does this extra work add to the system?
=- Bart
--
Bart Smaalders Solaris Kernel Performance
bart.smaalders at oracle.com http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
