--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/92f8aa3d-69da-4be2-af5a-b2a0f55d616b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/WF3My-cZNtY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/cfe3dfff-2099-4715-a04c-f43c3120a6c3%40googlegroups.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/WF3My-cZNtY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/cbb457c7-66cb-4370-99de-c9cfcd2a5622%40googlegroups.com.
There are two technical problems that need to be solved in order to make this happen.
The aim of this project would be to clean up one or more of Django's internal "parts" so that it could be delivered as a standalone package. This may not be something that can be immediately delivered - for example, it may be necessary to move or rename components to enable separate packaging. In this case, the project deliverable would be to document the strategy, and provide whatever initial moves in that direction are possible.
A simpler version of this project would be to enable separate packaging and distribution of Django's contrib apps.
alongside reduce tight coupling how should I approach to following part?
"A simpler version of this project would be to enable separate packaging and distribution of Django's contrib apps."
I am looking for dev teams suggestions
./auvipy
Some ideas. (which still require approval of the core developers):* Improve database backend base API and related features(including introspection feature used by inspectdb), so that it is less complicated to add in the future support the specific features of some backends. eg multiple database schemas (common used in Oracle and PostgreSQL) and/or Oracle synonym tables
Hi Fabio,Thank you for your project ideas. I'm going to follow the ideas from https://code.djangoproject.com/wiki/SummerOfCode2015
--
You received this message because you are subscribed to a topic in the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/WF3My-cZNtY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq849-9bAeo7dfoAk1XdGBFnBkykGVekRbJbs19_5UH3C1Kg%40mail.gmail.com.
Thank you both for the feedback. I will continue my analysis to understand django well and also try to contribute some patch on django if I can.For django URL dispatcher improvement I am also looking for some suggestions. Should I also look to some tool like werkzeug, webob along side django http, url dispatch, middleware and related stuffs. Some guide will help me to dig more and go to proper direction.
--
You received this message because you are subscribed to a topic in the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/WF3My-cZNtY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq84_XbuDCeX5LHgP4%2BuCYdzBAUUMY4EJxYj8WU%3DBP43onXA%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c35b86be-cba9-4d66-8e8b-fb5fcb7cf92a%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq84_tfCxFPG3fTY%2BNWcAcWV1tjv4VwE%2BvmWiKTsnTyPLAcg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAKAqTgrbTn1B77-N7Qf1iya4oX1Btt7u37u5kfyoNQq%2BdW-h2w%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq849jNhnGUyxw5sXoC_MtHpsBC8G9%3DXKogLe2bKomnRT5Ng%40mail.gmail.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/WF3My-cZNtY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/cbcd7c47-efaf-4ec6-a2d5-75f73d60f3a5%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/3b78ee4a-2724-4dcb-9d56-69cee1379f8c%40googlegroups.com.
Over the years, as Django has evolved, the idea of what constitutes "best practice" has also evolved. However, some parts of Django haven't kept up with those best practices. For example, contrib apps do not use class based views.
In short, Django has been bad at eating it's own dogfood. The contents of contrib should be audited and updated to make sure it meets current best practices.
For updating best practices first think to consider is to convert the functional views of django contrib apps to class based views where possible and necessary. To do so first app to consider is django contrib auth.
contrib-auth views.py now have function based views and they are
login logout logout_then_login redirect_to_login password_reset password_reset_done password_reset_confirm password_reset_complete password_change password_change_done
and in urls.py url mapping for function based views as follows
urlpatterns = [ url(r'^login/$', views.login, name='login'), url(r'^logout/$', views.logout, name='logout'), url(r'^password_change/$', views.password_change, name='password_change'), url(r'^password_change/done/$', views.password_change_done, name='password_change_done'), url(r'^password_reset/$', views.password_reset, name='password_reset'), url(r'^password_reset/done/$', views.password_reset_done, name='password_reset_done'), url(r'^reset/(?P[0-9A-Za-z_-]+)/(?P[0-9A-Za-z]{1,13}-[0-9A-Za-z]{1,20})/$', views.password_reset_confirm, name='password_reset_confirm'), url(r'^reset/done/$', views.password_reset_complete, name='password_reset_complete'), ]
and tests for this in tests/auth_tests/test_views.py
the views have to be converted into CBV and also the urls. and this should be done in a backward compatible manner.
as an example password_change_done view is now implemented as below.
@login_required def password_change_done(request, template_name='registration/password_change_done.html', current_app=None, extra_context=None): context = { 'title': _('Password change successful'), } if extra_context is not None: context.update(extra_context)
if current_app is not None:
request.current_app = current_app
return TemplateResponse(request, template_name, context)
this could be changed to cbv like below
class PasswordChangeDoneView(TemplateView): template_name='registration/password_change_done.html' current_app=None extra_context=None
@method_decorator(login_required)
def dispatch(self, request, *args, **kwargs):
return super(Password_Change_Done, self).dispatch(request, *args, **kwargs)
def get_context_data(self, **kwargs):
context = super(Password_Change_Done, self).get_context_data(**kwargs)
context.update({
'title': _('Password change successful'),
'current_app': self.current_app,
})
if self.extra_context is not None:
context.update(self.extra_context)
return context
def password_change_done(request, *args, **kwargs):
return PasswordChangeDoneView.as_view(**kwargs)(request, *args, **kwargs)
--
You received this message because you are subscribed to a topic in the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/WF3My-cZNtY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c26f31b0-a4af-4a0d-818d-d4f62ef430ac%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/d1396618-9c67-4034-be34-66049ef13cbb%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a1a4d8a8-9b46-410c-89f9-171ca135bd6f%40googlegroups.com.