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. That happened a couple weeks ago when Pylons-dev changed its dependency to the new version of simplejson. It wouldn't install on Windows, and the only binary eggs were for the older version. After I said, "Does Pylons really need the newest version?", we downgraded the dependency to allow the older version. Since Pylons doesn't use simplejson for anything except optional features anyway (@json). -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
