Just search the web for
"Client does not support authentication protocol" to see what I mean.
How hard would it be to create a cgi like this:
1) Choose your OS;
2) Choose your MySQL version;
3) Choose your Python version;
4) Download
-- instead of
1) I am feeling lucky
?
Would save tons of pain and misery for 1000s of developers I am sure.
Otherwise, if stuff doesn't work, -- how much does this whole effort worth?
I, for example, just cant' make it work, so I have to use Perl (!!! -- which I hate) to talk to my database, and then use pipe to exchange information with my Python app-n.
Someone would say: "Hey, man, it's open source, people spend a lot of time to make free software for you", -- True. And thanks. But isn't it worth it to put some effort in making it easier, so more people would actually use and appreciate it?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"Client does not support authentication protocol" generally seems to occur when you use a MySQL-4.0 client against a 4.1 server. This has nothing in particular to do with MySQLdb.
Also, I don't build binary packages for any OS any more, so the OS selection thing is pointless.
MySQLdb-1.0.x works with MySQL-3.22.x (x>19), 3.23, and 4.0 but not 4.1 and newer, and works with Python 1.5.2 and newer (but maybe not 2.4; not tested).
MySQLdb-1.1.x (and upcoming 1.2) works with MySQL-3.23, 4.0, and 4.1 (not all new features supported). 5.0 and newer are not yet supported. It works with Python 2.3 and newer, including 2.4. 1.1.x is the recommended version for Python 2.3 and newer, and it will be released in the very near future as 1.2.
Compile it against a client library that is compatible with the server you have to talk to, with the Python version you want to use, and you should be fine.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
...protocol", or:
"Definite guide regarding Python / OS / mysqldb versions badly needed".
Just search the web for
"Client does not support authentication protocol" to see what I mean.
How hard would it be to create a cgi like this:
1) Choose your OS;
2) Choose your MySQL version;
3) Choose your Python version;
4) Download
-- instead of
1) I am feeling lucky
?
Would save tons of pain and misery for 1000s of developers I am sure.
Otherwise, if stuff doesn't work, -- how much does this whole effort worth?
I, for example, just cant' make it work, so I have to use Perl (!!! -- which I hate) to talk to my database, and then use pipe to exchange information with my Python app-n.
Someone would say: "Hey, man, it's open source, people spend a lot of time to make free software for you", -- True. And thanks. But isn't it worth it to put some effort in making it easier, so more people would actually use and appreciate it?
Feel free to write one.
"Client does not support authentication protocol" generally seems to occur when you use a MySQL-4.0 client against a 4.1 server. This has nothing in particular to do with MySQLdb.
Also, I don't build binary packages for any OS any more, so the OS selection thing is pointless.
MySQLdb-1.0.x works with MySQL-3.22.x (x>19), 3.23, and 4.0 but not 4.1 and newer, and works with Python 1.5.2 and newer (but maybe not 2.4; not tested).
MySQLdb-1.1.x (and upcoming 1.2) works with MySQL-3.23, 4.0, and 4.1 (not all new features supported). 5.0 and newer are not yet supported. It works with Python 2.3 and newer, including 2.4. 1.1.x is the recommended version for Python 2.3 and newer, and it will be released in the very near future as 1.2.
Compile it against a client library that is compatible with the server you have to talk to, with the Python version you want to use, and you should be fine.