from django.conf.urls import patterns, url from django_view_dispatch import dispatch, dispatch_strict from . import views urlpatterns = patterns('', url(r'^some_url/$', dispatch(get=views.my_view, post=views.my_view_for_post), name='events_json'), # you can get any keyword argument you want to specify any http verb url(r'^some_url/$', dispatch(get=views.my_view, put=views.create, foo=views.another_view, bar=views.baz), name='events_json'), # by default, if a request has an HTTP verb that hasn't been specified in # the dispatch() function, it will be redirected to the GET view if present url(r'^some_url/$', dispatch(get=views.will_get_everything_thats_not_put, put=views.stuff), name='events_json'), # you can change this behavior this way url(r'^some_url/$', dispatch(get=views.stuff, put=views.will_get_everything_thats_not_get, default="put"), name='events_json'), # if "default" is set to None, this behavior is disabled and and # HttpResponseNotAllowed will be returned url(r'^input/$', dispatch(post=views.my_view_for_post, default=None), name='events_json'), # behave like @require_POST # a more explicit way to do that is provided with "dispatch_strict" which behave exactly like dispatch with default set to None url(r'^input/$', dispatch_strict(post=views.my_view_for_post), name='events_json'), )
pip install django_view_dispatch
Something that you learn as you progress in programming is that conditional are “bad” (as in “should be avoided”) because they increase the complexity of your code and are a potential source of bugs.
For example, mixing POST and GET handling in the same view can be a good terrain for bug and for a more complex code while spliting it gives a KISS situation where you have two views that do only one thing and do it well.
Django doesn’t provide an easy nor standard way to do this so this library is trying to address that.
No, since django 1.8, using string to target views in patterns is depreciated, therefor there is no point in supporting this feature.
Also, to be honest, I have not idea on how to do that and haven’t really made any research about it. That would also make the code way more complex.
pip install pytest py.test test.py
TODO: Figure out how to actually get changelog content.
Changelog content for this version goes here.
TODO: Brief introduction on what you do with files - including link to relevant help section.
|File Name & Checksum SHA256 Checksum Help||Version||File Type||Upload Date|
|django_view_dispatch-0.1-py2.7.egg (2.8 kB) Copy SHA256 Checksum SHA256||2.7||Egg||Apr 9, 2015|
|django_view_dispatch-0.1-py2.py3-none-any.whl (4.9 kB) Copy SHA256 Checksum SHA256||2.7||Wheel||Apr 9, 2015|
|django_view_dispatch-0.1.tar.gz (2.6 kB) Copy SHA256 Checksum SHA256||–||Source||Apr 9, 2015|