Same problem, your Fix works great!... Thanks, using
MacOS 10.7, Django 1.7, DjanogCMS3, Python 3.4.2
--
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-use
No hablo inglés.
Tenía el mismo problema.
1 - Lo que hice fue actualizar mi versión de Python (Python 2.7.* a Python
3.3.5).
2 - Descargue el driver de MySQL para Python 3.3.* (
mysql-connector-python-2.0.1-py3.3.msi )
desde http://dev.mysql.com/downloads/file.php?id=453803.
3 - Deje los
No hablo inglés.
Tenía el mismo problema.
1 - Lo que hice fue actualizar mi versión de Python (Python 2.7.* a Python
3.3.5).
2 - Descargue el driver de MySQL para Python 3.3.* (
mysql-connector-python-2.0.1-py3.3.msi )
desde http://dev.mysql.com/downloads/file.php?id=453803.
3 - Deje los
And I wish I could upvote your solution to heaven!
Thanks for sharing that, why is it not documented anywhere? Sounds like a
killing feature..
Cheers!
mccc
On Saturday, May 10, 2014 1:00:12 AM UTC+2, Richard Esplin wrote:
>
> Thanks for sharing what you did. I wish PostgreSQL was an option for m
Thanks for sharing what you did. I wish PostgreSQL was an option for me on
this project.
Oracle's answer was pretty generic, but they are right that Django 1.7 is
still in development. It is good to know that they are planning to support it
when it is released. I am glad I don't have to roll-ou
I switched to PostgreSQL when MySQL wasn't working. PostgreSQL worked
without a hitch and the migrations work wonderfully. But since my target
production environment only runs MySQL I will have to make the switch back
at some point.
Thanks for submitting the bug to MySQL. I see they posted a so
In order to move forward with this project, I switched to PyMySQL:
https://github.com/PyMySQL
It appears to work great. In order to use the default Django backend for
MySQL, I put this in my settings.py:
import pymysql
pymysql.install_as_MySQLdb()
DATABASES = {
'default': {
'ENGINE
This is actually a warning, and only halts execution when settings.py has
DEBUG enabled. See mysql/connector/django/base.py line 59.
However when syncdb proceeds past the deprecation warning, it halts on the
error about needing schema_editor implemented.
On Thursday, April 3, 2014 9:09:31 AM UT
I can't find any evidence on the interwebs of someone successfully using
the Mysql-Connector-Python with Django 1.7. So I reported it as an issue in
the MySQL bug database:
http://bugs.mysql.com/bug.php?id=72542
If anyone has a suggestion for using MySQL with Python 3 and Django 1.7, I
would a
I am also trying to use Django 1.7 with the Mysql-Python-Connector 1.1.6. I
am seeing the same behavior for both the migrate NotImplementedError and
the syncdb RemovedInDjango19Warrning.
Were you able to solve these problems?
Richard
On Thursday, April 3, 2014 9:09:31 AM UTC-6, Giovanni wrote:
Documentation states:
-
syncdb has been deprecated and replaced by migrate. Don’t worry - calls
to syncdb will still work as before.
But when I run $ python manage.py syncdb,
it stops with a django.utils.deprecation.RemovedInDjango19Warning.
So I can't seem to use syncdb eithe
I upgraded from django 1.6 to 1.7b1 and now it seems like as soon as I want
to do anything that interacts with mysql, I keep getting this error:
NotImplementedError: subclasses of BaseDatabaseWrapper may require a
schema_editor() method
In Python I can import mysql.connector just fine.
I've rei
12 matches
Mail list logo
