On Wed, Apr 9, 2008 at 11:50 AM, Mike Orr <[EMAIL PROTECTED]> wrote: > > The problem with C libraries is a lot bigger than just Google. It > frustrates users on Windows and Macintosh to no end, and many of them > give up trying to install Pylons/lxml/ToscaWidgets/wxPython and go on > to something else. Precompiled binaries don't always exist, are too > old, hard to find, or built with the wrong C compiler or Unicode > width. > Please do not dismiss this as a non-issue. Half the replies in this thread are in the from "for me it's not a problem" or "only newbies can't compile modules", C code in python frameworks is a *big* issue for end users. Both the people that program in the framework and the people that use the programs those people have coded. C extensions are great for performance but some times performance isn't the most important thing. I agree with Bob Ippolito as the best way to solve this is to have two libraries and fallback to the python version, but as you all know this isn't always possible.
> But > appengine has shown us there's a few other C dependencies to be worked > around if possible (without killing the performance). Because these > same problems presumably come up when porting Pylons to Jython, > IronPython, PyPy, etc. And if Django can do it and Pylons can't... :( this is entirely true. we shouldn't aim for cpython, we should aim for python the language. Most of fixing google apps engine will solve most of the issue for running pylons/TG on jython. > > -- > > 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 -~----------~----~----~----~------~----~------~--~---
