On Tue, May 21, 2013 at 6:45 PM, Tae Sandoval Murgan <[email protected]> wrote: > Maybe web.py should be considered as a "Python package" composed of > several "Python modules" which objective is web development, like > session.py, templetor.py, etc., more than a "web framework". If > Python has a module to send emails, I don't see the need for a new > one, unless that module doesn't fit with "the ideal way to write a web > app". >
I like the idea of keeping in the framework only the necessary modules, however I see a potential issue in _blindly_ following this strategy. Let's take the email api as an example: it is just a tiny wrapper around the Python api, nothing more, so why should it be kept in the framework? In my opinion (please correct me if wrong), that module is there (and hope will last) to create a common interface handy to create pluggable extensions: do you want to create and share an extension which at some point needs to send an email? Easy, use ``web.sendmail`` and you are done. Without that common interface this would not be possible. Cheers, Matteo > -- > You received this message because you are subscribed to the Google Groups > "web.py" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/webpy?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "web.py" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/webpy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
