On 9 Apr 2010, at 18:13 , UnclaimedBaggage wrote: > > Ooops - forgot one other thing: > > I'm a little concerned by django error handling. The tracer stack > seems to miss the relevant file a lot of the time, and I often find > little help from the error pages even when it does get the right page > (eg an error comes up with a useful file/line # in the debug page, but > the cause is on another page and I'm struggling for indications as to > where the bad code actually came from). This could, of course, just be > my inexperience with the language, but do more experienced developers > regularly find themselves having to "guess and hunt" exceptions/ > errors? > > Secondly, typoed template variables don't seem to throw exceptions. Is > there a way of changing this? I haven't seen much in the way of > getters/setters in example code, and I'm concerned that may make > typoed variable/list/dictionary declarations more difficult to hunt > down. > > Cheers again. ;-)
You seem to know (and prefer) Ruby more than Python. I'd suggest that you go with Rails for now (or some other Ruby framework), you can always revisit your choice later if you need to, or keep checking Django or other Python web frameworks on the side while you work with Rails (or whatever you end up picking) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
