> >Regarding file uploads: you *seem* to be proposing that uploaded files > >should be loaded into memory only. I've got complaints from people > > Mrr...? The only file upload reference simply says you shouldn't have > to subclass in order to use them; it's not implying files have to be > read into memory. (We have to deal with whackingly large mask layout > files at work, after all.) Mrrauw...? Do you really have to subclass? I thought it just says that you can subclass if you're not happy with the given make_file() implementation? > >Regarding templating -- what's wrong with HTMLgen as a starting point? > >Just that it's too big? I've never used it myself, but I've always > >been impressed with its appearance. :-) > > I, personally, am against including templating, but it was suggested. > I'm against it because there are too many solutions with different > tradeoffs. Do you want a simple regex search-and-replace, > constructing HTML pages as Python objects, or a full-blown > minilanguage? HTML/XML-compatibile syntax, ASP-compatible syntax, > Python-compatible syntax? Much better just to move templating into > the "Rejected" category and give the above rationale. Sure -- I'm perfectly happy with ad-hoc templating solutions myself (see my FAQ wizard). I've also heard Tom Christiansen complain that Perl is slower to start up than Python for CGI work -- because the templating classes are so big, and are all loaded at startup! I do see a use for a helper or helpers to creates tables though -- tables are notoriously tag-intensive and hard to get right. --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4