Mike Orr wrote: > On Wed, Apr 9, 2008 at 11:08 AM, Lawrence Oluyede <[EMAIL PROTECTED]> wrote: >> On Wed, Apr 9, 2008 at 6:43 PM, Bob Ippolito <[EMAIL PROTECTED]> wrote: >> > You can always take the approach where C modules are used if >> > available, otherwise pure Python code can be used. simplejson does >> > this, for example. >> >> Yes and it's maybe the way to go but requires careful coding at import >> time, something not everyone does. > > It requires careful coding by the package developer, which may not > have been done. So the user knows that some module has a Python > fallback, but easy_install doesn't, and the user doesn't know how to > coax easy_install into bypassing the C module, or how to configure it > manually.
With App Engine, the likely case is that you install the module (which typically includes the C extension directly), then upload it, and (I *think*) in the App Engine environment the C extension just won't be importable, and so the library should fall back to the Python implementation. This is how simplejson should work. But I haven't tried it, and it's hard to know until then. It's possible, for instance, that importing the C extension will not raise an ImportError (maybe instead OSError), and that would mess things up. Ian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
