I'm with Massimo and Yarko on this one. A big part of what makes web2py great is the fact that you can just download it and run it, with no dependencies. This was the #1 feature that got me to use web2py. I took a look at Django and saw how much effort it would be to set it up on my home computer (which uses Windows). Instead, I downloaded web2py and ran it, and it worked. It was an easy decision.
Every dependancy we add to web2py makes this feature harder to maintain. Any platform-dependant (i.e. not pure Python) dependancy puts this feature at serious risk. I don't think it's very onerous to expect the app developer to find and include all of the additional dependencies in their package. (1) They need to find the dependencies anyway to do their development work, (2) they know which platforms they're targeting, which may be a small subset of all of the platforms supported by web2py. As a community, we can help out in our FAQ and help documentation by listing all of the common external packages, and how to find them and package them with web2py. --Jonathan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
