Hi, I just started my "academic adventure". The goal is to refactor some of existing contrib and 3rd party apps to CBV to get a better feel of the API in real-world. Don't worry, I'm not going to spam this list with every problem I encountered, but there are two things I stumbled on upon almost instantly:
1) You can't put CBV in your urls.py using a string like you could with function views. This forces you to import every CBV, which is a bit annoying. 2) You can't reverse() an url to a CBV using just it's class name (or any other path, 'cause every closure returned by as_view() is different). This means, you have to name every url that uses a CBV, to be able to access it. This isn't a problem for generic CBV - the reverse on direct_to_template doesn't make sense either. This probably isn't a problem to a reusable app, which probably wants to name every url it provides (is this considered a good practise? are there any conventions to this?). Both things are a consequence of the as_view() approach. It's not clear to me that these are bugs or disadvantages, but it is something that should be mentioned in the docs (in guess the topics section is a good place?). Best regards, Łukasz Rekucki -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
