First Django Patch: django.contrib.auth 'Specifying a namespace in include() without providing an app_name '

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

First Django Patch: django.contrib.auth 'Specifying a namespace in include() without providing an app_name '

jazure622
Hi, I've recently sprung a bug that seems to be easily fixable. I would like to create my first patch on django with it. I am using Django 2.0.4.

Error code:

 File "/Users/User/PycharmProjects/django 0-1 login test/auth0login/urls.py", line 18, in <module>

    path('', include('django.contrib.auth.urls', 'auth')),

  File "/Users/User/Projects/django-master/django/urls/conf.py", line 39, in include
    'Specifying a namespace in include() without providing an app_name '

The fix is simple. Adding the app_name variable in django.contrib.auth.urls fixes this problem. I was wondering if I'm overlooking something before making a ticket and patching django.

<a imageanchor="1" href="about:invalid#zClosurez" style="clear: left; margin-bottom: 1em; margin-right: 1em; float: left;">

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/2c3065ba-b342-45bc-8ce4-4c8218cc9ac0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: First Django Patch: django.contrib.auth 'Specifying a namespace in include() without providing an app_name '

Tim Graham-2
It can't be changed due to backwards compatibility. See https://github.com/django/django/pull/9527.

On Saturday, April 14, 2018 at 12:29:01 PM UTC-4, [hidden email] wrote:
Hi, I've recently sprung a bug that seems to be easily fixable. I would like to create my first patch on django with it. I am using Django 2.0.4.

Error code:

 File "/Users/User/PycharmProjects/django 0-1 login test/auth0login/urls.py", line 18, in <module>

    path('', include('django.contrib.auth.urls', 'auth')),

  File "/Users/User/Projects/django-master/django/urls/conf.py", line 39, in include
    'Specifying a namespace in include() without providing an app_name '

The fix is simple. Adding the app_name variable in django.contrib.auth.urls fixes this problem. I was wondering if I'm overlooking something before making a ticket and patching django.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/81248364-fde7-471d-893d-293f496c18f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: First Django Patch: django.contrib.auth 'Specifying a namespace in include() without providing an app_name '

tribhuvan kishor
In reply to this post by jazure622
i am new on django ... can any one please guide where should i start .
and any good source for learning ?
thanks 

On Sat, Apr 14, 2018 at 8:48 PM, <[hidden email]> wrote:
Hi, I've recently sprung a bug that seems to be easily fixable. I would like to create my first patch on django with it. I am using Django 2.0.4.

Error code:

 File "/Users/User/PycharmProjects/django 0-1 login test/auth0login/urls.py", line 18, in <module>

    path('', include('django.contrib.auth.urls', 'auth')),

  File "/Users/User/Projects/django-master/django/urls/conf.py", line 39, in include
    'Specifying a namespace in include() without providing an app_name '

The fix is simple. Adding the app_name variable in django.contrib.auth.urls fixes this problem. I was wondering if I'm overlooking something before making a ticket and patching django.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/2c3065ba-b342-45bc-8ce4-4c8218cc9ac0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
regards 
Tribhuvan Kishor Bhaskar

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CACiphSXjq51QV-phGvXHk2%3DN6K%3DBavt2wcVRg6W%2B1At2si6cHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.