Friday, August 31, 2018

creating virtualenv for django but i get import zlib module error what could be the problem

raceback (most recent call last):
  File "/usr/local/bin/virtualenv", line 9, in <module>
    load_entry_point('virtualenv==15.0.1', 'console_scripts', 'virtualenv')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 542, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2569, in load_entry_point
    return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2229, in load
    return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2235, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 1993, in <module>
    """)
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 1848, in convert
    return zlib.decompress(b).decode('utf-8')
NameError: name 'zlib' is not defined

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/44266161-c188-45e9-9b91-94901b7d8232%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Cannot find static files when using mod_wsgi and apache

I'm having trouble getting serving static files.

My project is at /home/joel/myappointments
The app is at /home/joel/myappointments/appointments

An example template contains:
<link rel="stylesheet" href="{% static
'appointments/css/bootstrap.4.1.3.min.css' %}">

myappointments/myappointments/settings.py contains:
# Static files (CSS, JavaScript, Images)
# https://docs.djangoproject.com/en/2.0/howto/static-files/
STATICFILES_DIRS = [
os.path.join(BASE_DIR, "static/")

]
STATIC_URL = '/static/'
STATIC_ROOT = '/home/joel/myappointments/static/'
#'/home/joel/myappointments/appointments/static/'

I've tried different options. The present option is after creating
/home/joel/myappointments/static/ and running
python3 manage.py collectstatic

While running the application with:
(venv) root@localhost:/home/joel/myappointments# mod_wsgi-express
start-server wsgi.py --host myopip.com --user www-data --group
www-data --port 80

I get links like:
http://mysite.com/static/appointments/propellor/typography.css
which are broken.
If I use the development server, it all works.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/CAA%3Diw_8tMZw51trC6W8MbnY5BTxqcHqZFvmwq-pFZ3yrurG4kw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

System check Framework error checking Admin Fieldsets in 2.1

This Field set definition:

    fieldsets = (
       
('Job Work Sheet', {
           
'fields': (
                   
('number', 'job_history', 'hw_customer',),
                   
('status', 'contracted_out',),
                   
('adn_parts_required', 'atn_required', 'atn_tech', 'cancel_job',),
                   
('date_quoted', 'po_number', 'tag',),
                   
('date_in', 'priority',),
                   
('hw_description', 'hw_make', 'hw_model', 'hw_serial', ),
                   
('technician', 'bin', ),
                   
('assessment_time', 'hours_worked',),
                   
('parts_cost', 'parts_shipping',),
                   
('problem',),
               
)
       
}),
       
('Hardware Details', {
           
'classes': ('grp-collapse grp-closed',),
           
'fields': (('hw_customer', 'hardware', ), ('hw_description', 'hw_make', 'hw_model', 'hw_serial',), ('hw_comments',),)
       
}),
       
('Repair Details', {
           
'fields': (('work_done',), ('comments',),)
       
}),
   
)

Gets no errors with Django 2.0.6, but with 2.1 I get:

(dj21py37) $ ./manage.py check
SystemCheckError: System check identified some issues:

ERRORS:
<class 'repair.admin.JobAdmin'>: (admin.E012) There are duplicate field(s) in 'fieldsets[1][1]'.
<class 'repair.admin.JobAdmin'>: (admin.E012) There are duplicate field(s) in 'fieldsets[2][1]'.

System check identified 2 issues (0 silenced).



I presume its complaining about the field 'hw_customer', but since it is in readonly_fields this should not be an error, correct?

Rich.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/5c78dd4e-d86a-4367-8c09-de2c34773f69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Django Channels - core.py error

I have the latest Django (2x), channels (2x), and redis/docker as of Aug 31st, 2018 installed. I am encountering a django channels error and have no idea why this is happening...has anyone seen this output? What is the potential cause? Feeling pretty stuck with the error below...happens when refreshing the site and an attempt is made to connect from js Websocket to the python/channels backend.


2018-08-31 15:13:04,623 - ERROR - server - Exception inside application:
  File "/.../tests/lib/python3.6/site-packages/channels/sessions.py", line 175, in __call__
    return await self.inner(receive, self.send)
  File "/.../tests/lib/python3.6/site-packages/channels/middleware.py", line 41, in coroutine_call
    await inner_instance(receive, send)
  File "/.../tests/lib/python3.6/site-packages/channels/consumer.py", line 54, in __call__
    await await_many_dispatch([receive, self.channel_receive], self.dispatch)
  File "/.../tests/lib/python3.6/site-packages/channels/utils.py", line 57, in await_many_dispatch
    await task
  File "/.../tests/lib/python3.6/site-packages/channels_redis/core.py", line 400, in receive
    assert not self.receive_lock.locked()
 
[2018/08/31 15:13:04] WebSocket DISCONNECT /ws/dashboard/ [127.0.0.1:56102]

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/dc2a8aa4-ba28-4e90-b66a-8721f5573abf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ldap for django

Wow Vineet Kothari very insightful, why do you have to be a dick?

On Aug 31, 2018 9:57 PM, "Vineet Kothari" <me.vineetkothari@gmail.com> wrote:
It is not lodap is ldap

Sent from my Huawei Mobile


-------- Original Message --------
Subject: Ldap for django
From: soumyajit banerjee
To: Django users
CC:


Hi,

I am new in django python. I want to set up lodap authentication for my django app. Could you please help me. I am using python 3.6 with django 2.1

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/73bd4a1c-86d8-4763-90d7-b7415fec992c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/-nsggnw31f0154qz1l9-p4sxo1jkikmy-gx1x3hec6xce-9rcgqo-axqdp5y85rvjsfpr41jveqvhp3fxin-of4z78-w3oew795cdywcydz51tim2qu-c546dg-vr5rvajbx5e5gavqmax8lpqg-vxozcx.1535732867097%40email.android.com.
For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/CAMMZq8MfGQiBdEpN005uEEf%3D58p5YuASLWtKX5CuW3JuqohFmA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re:

Please read the footer of every message for instructions regarding how to unsubscribe. You have to do it yourself.

Mark

On Fri, Aug 31, 2018, 9:36 AM Nitesh Chaudhary <neetyes2@gmail.com> wrote:
Please unsubscribe my account neetyes2@gmail.com. I got unnecessary mail.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/CAOa_WrL90%3DZkaKLNWaAz96rsJ8H%2BJzhSdZ-EBh%3D7SsMKEVO1%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/CAEqej2OPVJoRWvg4ePbqrP9dbDQPoJ_hqFf0TNmOGJMpYr3D0w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django

Thank you, Mike Dewhirst.


On Fri, Aug 31, 2018 at 3:52 AM Mike Dewhirst <miked@dewhirst.com.au> wrote:
On 30/08/2018 2:57 PM, Sai Pavan Kumar wrote:
> Hi Friends,
>        This is pavan working as a python developer. Is there any tool
> for reports generation in django admin or in templates(dynamic filters).

Try this ...

https://www.google.com.au/search?q=django-report-generator

I will be looking for one myself in the future so it would be good to
hear what you think.




>
>
> --
> 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 django-users+unsubscribe@googlegroups.com
> <mailto:django-users+unsubscribe@googlegroups.com>.
> To post to this group, send email to django-users@googlegroups.com
> <mailto:django-users@googlegroups.com>.
> 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/317d153c-6a0f-4acd-aa27-5adcfa797219%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/317d153c-6a0f-4acd-aa27-5adcfa797219%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/fe81068a-c997-8561-e3eb-e28c967979d6%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.


--
Regards,

SaiPavan Thirupathi

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/CAFJPbobEqx9F%3DygQ_Mm0d7vacK%3DpsdMJrTT4iucSgBK%3DjEHcJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Please unsubscribe my account neetyes2@gmail.com. I got unnecessary mail.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/CAOa_WrL90%3DZkaKLNWaAz96rsJ8H%2BJzhSdZ-EBh%3D7SsMKEVO1%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ldap for django

It is not lodap is ldap

Sent from my Huawei Mobile


-------- Original Message --------
Subject: Ldap for django
From: soumyajit banerjee
To: Django users
CC:


Hi,

I am new in django python. I want to set up lodap authentication for my django app. Could you please help me. I am using python 3.6 with django 2.1

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/73bd4a1c-86d8-4763-90d7-b7415fec992c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/-nsggnw31f0154qz1l9-p4sxo1jkikmy-gx1x3hec6xce-9rcgqo-axqdp5y85rvjsfpr41jveqvhp3fxin-of4z78-w3oew795cdywcydz51tim2qu-c546dg-vr5rvajbx5e5gavqmax8lpqg-vxozcx.1535732867097%40email.android.com.
For more options, visit https://groups.google.com/d/optout.

Re: Language code twice in url

I think it has something to do with phusion passenger. It's skipping the first path item and merge it with the url.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/fe2c26e1-04ea-42fa-9389-126dc1ed1965%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Django bugfix release: 2.1.1

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE/l+2OHah1xioxnVW4X31yCtPnQAFAluJAb4ACgkQ4X31yCtP
nQCOCBAAkw8F+KMlaTl+f6RP97GDDIhlbiDESb4d1U87fLsPRvsHwwt7xhZqWioz
9IHQW5udvAR7J8QAnK2upyd+3JvoSsv5fAbasGvaOrNarDxTuOmlWOZfaBcvTL7E
Tu+b71IigqaP/uyw8BwatDliUQ+uFteQvBTxsIi0dcunXZohvyOWGBpaVeAbjCye
HnEydVmpXjP+i3LfuuEfeHctJaVSQARXqdG/4cWt0n7dv47kUCoTffqda7Rbrzlb
t7yb2wIhbv8YhYTHSaPvapHjJKZZ0bsug/E4CEo3bJNe1pV3GcVbteqxgf6hqTIT
bFasI2OL79/YF1XXKXrFjdxpWb8X/I+UtWOmx8Cw371gt4pnxtLmyBCJ6PUKt+KO
TNkwwCKKDVoTs/7KVVFH76RP4SOwVX1Jm8O1P2lvvmk4WX/xL+pl4feJONauYArF
+NgPZqDmZCmA9cxq/lREZb9gDrf/AkS4r5i629Uc0gYae+uERAMJfVYP14EcFQV0
aVXJzADyN4wE9ylm5cQhZdJxeyKDrqNYOITFowcKSL/Q5kw2mGgVq/0zlTzrlsDO
GIk1O6FyVZKCk2+gQJ5TG4kjb238hIXi/6DK9psRlgizpJttxabb7psgknKBlCDC
fJo2+j4kDGYAWqf14hFSBHuvX2FU6Ma71Lb1FKngj2ydVoKS2nw=
=Ufa+
-----END PGP SIGNATURE-----
Details are available on the Django project weblog:

https://www.djangoproject.com/weblog/2018/aug/31/bugfix-release/

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/127D72C0-2CE8-45C2-A7FD-8E9A50BC7DB8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Thursday, August 30, 2018

Re: New language adding error('Unknown language code si.')

Hello Bazan

you can be fixed this issue this override Django locale file. setting up your settings.py file like the below.

EXTRA_LANG_INFO = {
    'si': {
        'bidi': False,
        'code': 'si',
        'name': 'Sinhala',
        'name_local': 'සිංහල',
    },
    'en': {
        'bidi': False,
        'code': 'en',
        'name': 'English',
        'name_local': 'English',
    },
}
LANG_INFO = dict(EXTRA_LANG_INFO.items())
django.conf.locale.LANG_INFO = LANG_INFO

LANGUAGE_CODE = 'en'
LANGUAGES = [
    ('en', _('English')),
    ('si', _('Sinhala')),
]

This one fixed the issue. should remember to add all language details your using to EXTRA_LANG_INFO variable 

Thanks

On Thursday, August 9, 2018 at 9:01:58 PM UTC+5:30, Deniz Bazan wrote:
Hi Kumara, did you  find a solution for your question, because i have same problem. 

Am Montag, 30. April 2018 14:04:01 UTC+2 schrieb lakshitha kumara:
Hello Jason,

Thanks you for your reply but unfortunately that example not working any more with django 2 and python 3 .

Thanks

On Monday, April 30, 2018 at 7:47:45 AM UTC+5:30, lakshitha kumara wrote:
Hello Guys 

I added new language to django . language called Sinhala. My code is look like this.

On settings page 

LANGUAGE_CODE = 'en'
LANGUAGES = [
    ('si', _('Sinhala')),
    ('en', _('English')),
]
TIME_ZONE = 'UTC'

USE_I18N = True

USE_L10N = True

USE_TZ = True

LOCALE_PATHS = (
    os.path.join(os.path.dirname(__file__), "../locale"),
)

On locale folder 

__init__.py

LANG_INFO = {
    'si': {
        'bidi': False,
        'code': 'si',
        'name': 'Sinhala',
        'name_local': 'Sinhala',
    },
}
I ran this command after that 
manage.py makemessages -l si  manage.py compilemessages

When i goes to admin URL with sinhala language its working fine i try get all supported language give this error 
<form action="{% url 'set_language' %}" method="post">{% csrf_token %}      <input name="next" type="hidden" value="{{ redirect_to }}" />      <select name="language">          {% get_current_language as LANGUAGE_CODE %}          {% get_available_languages as LANGUAGES %}          {% get_language_info_list for LANGUAGES as languages %}          {% for language in languages %}              <option value="{{ language.code }}"{% if language.code == LANGUAGE_CODE %} selected{% endif %}>                  {{ language.name_local }} ({{ language.code }})              </option>          {% endfor %}      </select>      <input type="submit" value="Go" />  </form>

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/81891d8c-aec9-427f-8bc8-3cb35e387153%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New language adding error('Unknown language code si.')

Hello Deniz Bazan

I fixed that issue with override Django locale file. you can try to setting up file this your setting.py file 

EXTRA_LANG_INFO = {
    'si': {
        'bidi': False,
        'code': 'si',
        'name': 'Sinhala',
        'name_local': 'සිංහල',
    },
'en': {
        'bidi': False,
        'code': 'en',
        'name': 'English',
        'name_local': 'English',
    },
}

On Thursday, August 9, 2018 at 9:01:58 PM UTC+5:30, Deniz Bazan wrote:
Hi Kumara, did you  find a solution for your question, because i have same problem. 

Am Montag, 30. April 2018 14:04:01 UTC+2 schrieb lakshitha kumara:
Hello Jason,

Thanks you for your reply but unfortunately that example not working any more with django 2 and python 3 .

Thanks

On Monday, April 30, 2018 at 7:47:45 AM UTC+5:30, lakshitha kumara wrote:
Hello Guys 

I added new language to django . language called Sinhala. My code is look like this.

On settings page 

LANGUAGE_CODE = 'en'
LANGUAGES = [
    ('si', _('Sinhala')),
    ('en', _('English')),
]
TIME_ZONE = 'UTC'

USE_I18N = True

USE_L10N = True

USE_TZ = True

LOCALE_PATHS = (
    os.path.join(os.path.dirname(__file__), "../locale"),
)

On locale folder 

__init__.py

LANG_INFO = {
    'si': {
        'bidi': False,
        'code': 'si',
        'name': 'Sinhala',
        'name_local': 'Sinhala',
    },
}
I ran this command after that 
manage.py makemessages -l si  manage.py compilemessages

When i goes to admin URL with sinhala language its working fine i try get all supported language give this error 
<form action="{% url 'set_language' %}" method="post">{% csrf_token %}      <input name="next" type="hidden" value="{{ redirect_to }}" />      <select name="language">          {% get_current_language as LANGUAGE_CODE %}          {% get_available_languages as LANGUAGES %}          {% get_language_info_list for LANGUAGES as languages %}          {% for language in languages %}              <option value="{{ language.code }}"{% if language.code == LANGUAGE_CODE %} selected{% endif %}>                  {{ language.name_local }} ({{ language.code }})              </option>          {% endfor %}      </select>      <input type="submit" value="Go" />  </form>

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/7175788d-456f-4535-b8b6-ab63839a1005%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django

On 30/08/2018 2:57 PM, Sai Pavan Kumar wrote:
> Hi Friends,
>        This is pavan working as a python developer. Is there any tool
> for reports generation in django admin or in templates(dynamic filters).

Try this ...

https://www.google.com.au/search?q=django-report-generator

I will be looking for one myself in the future so it would be good to
hear what you think.




>
>
> --
> 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 django-users+unsubscribe@googlegroups.com
> <mailto:django-users+unsubscribe@googlegroups.com>.
> To post to this group, send email to django-users@googlegroups.com
> <mailto:django-users@googlegroups.com>.
> 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/317d153c-6a0f-4acd-aa27-5adcfa797219%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/317d153c-6a0f-4acd-aa27-5adcfa797219%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/fe81068a-c997-8561-e3eb-e28c967979d6%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.

Re: Ldap for django

On 30/08/2018 10:28 PM, soumyajit banerjee wrote:
> Hi,
>
> I am new in django python. I want to set up lodap authentication for
> my django app. Could you please help me. I am using python 3.6 with
> django 2.1
Try this ...

https://www.google.com/search?q=django-ldap&ie=utf-8&oe=utf-8&client=firefox-b-ab

I haven't looked at LDAP in ten years so I'm not able to recommend anything.


> --
> 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 django-users+unsubscribe@googlegroups.com
> <mailto:django-users+unsubscribe@googlegroups.com>.
> To post to this group, send email to django-users@googlegroups.com
> <mailto:django-users@googlegroups.com>.
> 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/73bd4a1c-86d8-4763-90d7-b7415fec992c%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/73bd4a1c-86d8-4763-90d7-b7415fec992c%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/6fd8f195-ae1b-0db1-6d6c-53aa73c5fbbd%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.

Re: Doubts on One-To-One Field

Actually we would be needing that information most of the time, I will have to see the which would be favourable and also of course django  has documented  a doubt I have. I guess I have to rtfd more carefully. Thank you for the information. You are a savior.



On Thu, Aug 30, 2018 at 10:54 PM Michael MacIntosh <mmacintosh@linear-systems.com> wrote:

Hello,

You are correct, creating a one-to-one relationship can potentially create more queries and hurt performance if you are not careful.  However it can also speed up certain queries if you don't need that information all of the time.

If you are worried about the performance, I would suggest looking into select_related and prefetch_related.  Select related will grab your Users and user profiles in one query, which can be faster.  Prefetch related will fire off a query for each prefetched item, so one for users and one for user profiles, which isn't useful here.

https://docs.djangoproject.com/en/2.1/ref/models/querysets/#select-related


On 8/30/2018 9:08 AM, vineeth sagar wrote:
def userProfile(models.Model):
      user=models.OneToOneField(User,primary_key=True)
       """
       Other stuff
       """
I can query it like this 
x = userProfile.objects.get(user__id=1)(Assuming this exists)

when I do a connection.queries a single query is executed.When I try to access the username i.e x.user.username a new query is executed again when I see connection.queries? Is this the expected behavior. Wouldn't this be bad if we have huge databases? I have a scenario where some classes have common information and then they have different fields based on their classes. I have tested this OneToOneField by the above example and for some reason reluctant to use this because of the new query? The other approach would be abstract base classes where information stored in the db would be duplicated but the additional query can be saved I think any thoughts?
--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/afb76a5c-30c7-45f0-8f8a-96e1d30e731c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
This message has been scanned for viruses and dangerous content by
E.F.A. Project, and is believed to be clean.
Click here to report this message as spam.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/84470c00-3058-3c5e-d947-1ee6e231f0b6%40linear-systems.com.
For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/CAMMZq8OP6yAoB%3D%2BC%3Dv5bMKZuLDedLs-ORHiTk970G5DTgp9a%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Doubts on One-To-One Field

Hello,

You are correct, creating a one-to-one relationship can potentially create more queries and hurt performance if you are not careful.  However it can also speed up certain queries if you don't need that information all of the time.

If you are worried about the performance, I would suggest looking into select_related and prefetch_related.  Select related will grab your Users and user profiles in one query, which can be faster.  Prefetch related will fire off a query for each prefetched item, so one for users and one for user profiles, which isn't useful here.

https://docs.djangoproject.com/en/2.1/ref/models/querysets/#select-related


On 8/30/2018 9:08 AM, vineeth sagar wrote:
def userProfile(models.Model):
      user=models.OneToOneField(User,primary_key=True)
       """
       Other stuff
       """
I can query it like this 
x = userProfile.objects.get(user__id=1)(Assuming this exists)

when I do a connection.queries a single query is executed.When I try to access the username i.e x.user.username a new query is executed again when I see connection.queries? Is this the expected behavior. Wouldn't this be bad if we have huge databases? I have a scenario where some classes have common information and then they have different fields based on their classes. I have tested this OneToOneField by the above example and for some reason reluctant to use this because of the new query? The other approach would be abstract base classes where information stored in the db would be duplicated but the additional query can be saved I think any thoughts?
--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/afb76a5c-30c7-45f0-8f8a-96e1d30e731c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
This message has been scanned for viruses and dangerous content by
E.F.A. Project, and is believed to be clean.
Click here to report this message as spam.

Doubts on One-To-One Field

def userProfile(models.Model):
      user=models.OneToOneField(User,primary_key=True)
       """
       Other stuff
       """
I can query it like this 
x = userProfile.objects.get(user__id=1)(Assuming this exists)

when I do a connection.queries a single query is executed.When I try to access the username i.e x.user.username a new query is executed again when I see connection.queries? Is this the expected behavior. Wouldn't this be bad if we have huge databases? I have a scenario where some classes have common information and then they have different fields based on their classes. I have tested this OneToOneField by the above example and for some reason reluctant to use this because of the new query? The other approach would be abstract base classes where information stored in the db would be duplicated but the additional query can be saved I think any thoughts?

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/afb76a5c-30c7-45f0-8f8a-96e1d30e731c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: WSGIRequest' object has no attribute 'name'

Hi,

You are probably trying to get a name property from the request object. Like this: request.name. And the request object usually doesn't have that property.

Regards,

Andréas


Den tors 30 aug. 2018 kl 15:50 skrev sankar ardhas <sankarardhas@gmail.com>:
Hi all , 
          I have a error when i submit a form that WSGIRequest' object has no attribute 'name'. what is the solution for that.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/1e650abb-e867-4b7a-86f9-82f5181d93f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/CAK4qSCdy0wSTM%3D-jCt%3DUsU5X4XYOMJg%3D3etJBKOgA_8FQRYEsA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

WSGIRequest' object has no attribute 'name'

Hi all , 
          I have a error when i submit a form that WSGIRequest' object has no attribute 'name'. what is the solution for that.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/1e650abb-e867-4b7a-86f9-82f5181d93f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Customise Session Engine to distribute session data storage

https://github.com/adw0rd/django-multi-sessions

that's a non-working project but might give you some clues how to route sessions to different backends.

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/b67629db-8314-4a3d-accc-22510ab9d6af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Language code twice in url

Hi,

I'm building a multi language website using i18n. I get the language in the url with i18n_patterns :

urlpatterns = i18n_patterns(path('/contact/', views.contact, name='contact'), ...)


So I can access to my page with my-domain.com/en/contact/. But when I submit a form (or just try to acess it with a POST request), the url changes to my-domain.com/en/en/contact/ and then return a 404 error.

Any idea ?

Thanks for your help 
Kaelig

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/bb102058-6c29-4a14-b3f9-d4e699067614%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ldap for django

Hi,

I am new in django python. I want to set up lodap authentication for my django app. Could you please help me. I am using python 3.6 with django 2.1

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/73bd4a1c-86d8-4763-90d7-b7415fec992c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Customise Session Engine to distribute session data storage

We were actually cache_db but the sessions were consuming too much of DB. Hence, we want some sessions to be persistent in DB and some to be volatile and not stored in DB. Hence, I was looking for some way to achieve that. Like I want all login sessions to be stored in DB whereas rest in cache. 

On Tuesday, August 28, 2018 at 4:37:46 PM UTC+5:30, Jason wrote:
Actually, there's nothing stopping you from using redis for cache and session cache.  

SESSION_ENGINE = 'django.contrib.sessions.backends.cache'

will use your cache to store sessions.  and if you use cached_db instead of cache, that data will persist in redis and survive restarts.

On Tuesday, August 28, 2018 at 1:40:38 AM UTC-4, Web Architect wrote:
Hi Jason,

Thanks for the response. Why not use Django's cache backend and setting cache alias to be redis?

Thanks. 

On Monday, August 27, 2018 at 5:01:08 PM UTC+5:30, Jason wrote:
there's an option to use redis as a session backend, which would be faster than using a regular db, even a well tuned mysql/postgres instance

https://github.com/martinrusev/django-redis-sessions

On Monday, August 27, 2018 at 3:52:06 AM UTC-4, Web Architect wrote:
Hi,

Right now we are using the Django cache_db session engine for persistent sessions and also for some speed. Is it possible to customise this where I can store some session data in cache and some in DB? For example, I want to store all login sessions in DB and rest like some user specific data - basket etc in cache .

Looking forward to your support....

Thanks. 

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/86d58e15-ff41-48e3-b534-2bf982d59531%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help.... Django : Change Backend as mysql and create sample example using django ORM

Ensure you are using MySQL 5.6 or higher: https://docs.djangoproject.com/en/2.1/ref/databases/#version-support

To find your version run SELECT VERSION();



On 30 August 2018 at 05:37:52, Sonali Vighne (sonalivighne@gmail.com) wrote:

MySQL  version    -  6.0.8-alpha-community

On Wednesday, August 29, 2018 at 7:26:09 PM UTC+5:30, Tom Forbes wrote:
What version of MySQL are you running?

On Tuesday, 28 August 2018 07:00:52 UTC+1, Sonali Vighne wrote:

I will paste full error and stack trace here.

This is occurred when I am giving "python manage.py migrate" command

 

Operations to perform:

  Apply all migrations: admin, auth, contenttypes, sessions

Running migrations:

Traceback (most recent call last):

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\db\backends\utils.py", line 83, in _execute

    return self.cursor.execute(sql)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\db\backends\mysql\base.py", line 71, in execute

    return self.cursor.execute(query, args)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\MySQLdb\cursors.py", line 250, in execute

    self.errorhandler(self, exc, value)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\MySQLdb\connections.py", line 50, in defaulterrorhandler

    raise errorvalue

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\MySQLdb\cursors.py", line 247, in execute

    res = self._query(query)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\MySQLdb\cursors.py", line 411, in _query

    rowcount = self._do_query(q)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\MySQLdb\cursors.py", line 374, in _do_query

    db.query(q)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\MySQLdb\connections.py", line 277, in query

    _mysql.connection.query(self, query)

_mysql_exceptions.ProgrammingError: (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(6) NOT NULL)' at line 1")

 

The above exception was the direct cause of the following exception:

 

Traceback (most recent call last):

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\db\migrations\recorder.py", line 55, in ensure_schema

    editor.create_model(self.Migration)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\db\backends\base\schema.py", line 312, in create_model

    self.execute(sql, params or None)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\db\backends\base\schema.py", line 133, in execute

    cursor.execute(sql, params)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\db\backends\utils.py", line 100, in execute

    return super().execute(sql, params)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\db\backends\utils.py", line 68, in execute

    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\db\backends\utils.py", line 77, in _execute_with_wrappers

    return executor(sql, params, many, context)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\db\backends\utils.py", line 85, in _execute

    return self.cursor.execute(sql, params)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\db\utils.py", line 89, in __exit__

    raise dj_exc_value.with_traceback(traceback) from exc_value

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\db\backends\utils.py", line 83, in _execute

    return self.cursor.execute(sql)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\db\backends\mysql\base.py", line 71, in execute

    return self.cursor.execute(query, args)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\MySQLdb\cursors.py", line 250, in execute

    self.errorhandler(self, exc, value)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\MySQLdb\connections.py", line 50, in defaulterrorhandler

    raise errorvalue

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\MySQLdb\cursors.py", line 247, in execute

    res = self._query(query)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\MySQLdb\cursors.py", line 411, in _query

    rowcount = self._do_query(q)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\MySQLdb\cursors.py", line 374, in _do_query

    db.query(q)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\MySQLdb\connections.py", line 277, in query

    _mysql.connection.query(self, query)

django.db.utils.ProgrammingError: (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(6) NOT NULL)' at line 1")

 

During handling of the above exception, another exception occurred:

 

Traceback (most recent call last):

  File "D:\EclipsePython\DjangoMysql\manage.py", line 15, in <module>

    execute_from_command_line(sys.argv)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\core\management\__init__.py", line 381, in execute_from_command_line

    utility.execute()

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\core\management\__init__.py", line 375, in execute

    self.fetch_command(subcommand).run_from_argv(self.argv)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\core\management\base.py", line 316, in run_from_argv

    self.execute(*args, **cmd_options)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\core\management\base.py", line 353, in execute

    output = self.handle(*args, **options)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\core\management\base.py", line 83, in wrapped

    res = handle_func(*args, **kwargs)

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\core\management\commands\migrate.py", line 203, in handle

    fake_initial=fake_initial,

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\db\migrations\executor.py", line 91, in migrate

    self.recorder.ensure_schema()

  File "C:\Users\sonali_vighne\AppData\Local\Programs\Python\Python36\lib\site-packages\django\db\migrations\recorder.py", line 57, in ensure_schema

    raise MigrationSchemaMissing("Unable to create the django_migrations table (%s)" % exc)

django.db.migrations.exceptions.MigrationSchemaMissing: Unable to create the django_migrations table ((1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(6) NOT NULL)' at line 1"))

Finished "D:\EclipsePython\DjangoMysql\manage.pymigrate" execution.

 

 

 

 

 

Setting.py

 

 

INSTALLED_APPS = [

    'django.contrib.admin',

    'django.contrib.auth',

    'django.contrib.contenttypes',

    'django.contrib.sessions',

    'django.contrib.messages',

    'django.contrib.staticfiles',

    'mysqlApp' #this is app created

]

 

 

DATABASES = {

    'default': {

        'ENGINE': 'django.db.backends.mysql',

        'NAME': 'hospital',

        'USER': 'root',

        'PASSWORD': '',

        'HOST': 'localhost',

        'PORT': '3306'

    }

}

 





On Monday, August 27, 2018 at 5:38:28 PM UTC+5:30, Sonali Vighne wrote:

Hi,

I have tried a lot to change Django back-end as MySQL but not able to achieve this. 

please help for the same.

 

thanks in advance. :) 

--
You received this message because you are subscribed to a topic in the Google Groups "Django users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-users/iuspogePH3k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
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/1c3e465c-ee14-4113-bbc3-accd2e935b39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.