#25111: Tutorial for 1.8 breaks with recommended mysql settings
--------------------------------------+--------------------
Reporter: JorisBenschop | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+--------------------
The current tutorial mentions it is optimized for python 3.2. However, on
page 1 it recommends using "django.db.backends.mysql" to interact with
mysql. This yields an error because this backend loads the MySQLdb module
which does not exist for python 3.2. Considering this is page 1 of the
basic tutorial such an error should not happen.
Possible solution would be change the docs to specify that django has a
dependncy on mysql.connector.python, and suggest the appropriate backend.
I know this connector is external, but so is MySQLdb.
Personally i would recommend to alter the code that runs "import MySQLdb"
to include an exception that checks if python version is > 3 and return a
message asking the user to install the correct module. Asking to install
MySQLdb from python3 users is confusing.
Apologies if this is a diplicate
--
Ticket URL: <https://code.djangoproject.com/ticket/25111>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/056.31adfff5c5f2866f42bd1dfc2b980267%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
