I agree. Think about when you sign up for a website, at the very least. Usually that involves an email confirmation. This is one of the most common things, so I think it should be included. On May 21, 2013 4:03 AM, "Dragan Espenschied" <[email protected]> wrote:
> > > Am 19.05.2013 14:25, schrieb W. Martin Borgert: > > On 2013-05-19 14:07, Dragan Espenschied wrote: > >> I haven't been able to send UTF8 encoded emails with webpy. That would > be great, > >> just to call the method and not having to care about the encoding. > > > > I wonder, why web.py does have an e-mail API anyway. This is > > sth. that could be separated. Python already has an e-mail API > > and if there is the need for something more advanced, it could > > be another framework, not web.py. > > > > From my experience the great thing about webpy is that it includes all the > basics one might want from a web application, and is still super-simple. > > Python has APIs for almost anything, so consequently webpy could be > reduced to > its URL mapper probably. :) A web framework needs sessions, templates, > database, > email, otherwise it is useless. > > -- > 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.
