On 03/17/10 03:51 PM, Suresh Chandrasekharan wrote:
> Hi Garret,
>
> The requirement for the library came from installer group. Originally
> we are planning to deliver the library in C, since the text/auto
> installers currently are getting re-written in Python, as per their
> request, we changed the implementation to python. (Sure writing it in
> C and provide python bindings is a possibility, but compared to
> python, the development time will be much more in C, and we were not
> aware of C requirements for a CLDR interface library)
>
> What we can realistically do is to work on a C implementation after
> this python library is integrated (and installers can use it), and at
> that point replace the existing library with python bindings to that C
> library.
That would be a reasonable compromise.
- Garrett
>
> regards,
> Suresh
>>
>> 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
>>
