And your question is?
--
Psss, psss, put it down! - http://www.cafepress.com/putitdown
MySQLdb or something else for python3.0 ?
gert> MySQLdb or something else for python3.0 ?
Given that Python 3.0 is so new and so few packages have been ported to it
yet, it might be helpful if you explained why Python 2.6 + MySQLdb isn't
sufficient for your needs.
--
Skip Montanaro - sk...@pobox.com - http://smontanaro.dyndns.org/
For postgres, psycopg2 works with Python 3 (if you use my patch).
Regards,
Martin
regards
Steve
--
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/
Interestingly enough, the question was slightly (but importantly)
different, though: the question really was "Does anybody has a patch for
MySQLdb?"; as my reference to the existing interface to PostgreSQL
was not sufficient for the OP.
Regards,
Martin
Exactly. One could think about 3-4 different potentially useful
answers to the OP but when one sees 3-4 immediately right after
reading the post then probably there are a couple more still after
some thinking. So if the OP specifies exactly what he/she wants,
he/she will get more signal than noise.
Cheers,
Daniel
Yes it was enough, but I can not imagine it has not been done yet for
MySql either :)
It was a open statement where I expected like 10 different databases
responses. For example if you go to a dinner place you have never been
gone before and want to try something new and there is no menu
available. What do you ask ? You just say something similar. "I would
like to order a salet please with some red wine." I don't think any
one of you would expect the waiter to answer,"And your question is?" I
also think the waiter does not expect me to ask 10 similar questions
like "red wine 1991? red wine 1992? red wine 1993? until i hit
something that is on the menu"
So the final questions was, is there anything els on the menu besides
PostgreSQL, like MySql for example ? If not I will take PostgreSQL
please.
There is sqlite3 also; it is included in Python 3. Otherwise, I don't
think any other DB-API compliant database connectors have been ported
to Python 3 yet; it may take many months until somebody volunteers to
port a MySQL driver.
The difference to your restaurant example is that the market for red
wine is many hundred years old. The market for Python 3 modules is
just a month old. Hence, you have different offers for red wine, but
nearly none for Python 3 modules.
Regards,
Martin
Well, this actually is the case: MySql has not been ported. As far as
I can see the mysql python module in general (meaning for the 2.x
branch) is not as well maintained as some others and questions about
windows vs. linux issues periodically come up on the mailing list. So
I would not be surprised if porting mysql to the 3.x branch will take
longer and will be less well-maintained than other database bindings.
> It was a open statement where I expected like 10 different databases
> responses. For example if you go to a dinner place you have never been
> gone before and want to try something new and there is no menu
> available. What do you ask ? You just say something similar. "I would
> like to order a salet please with some red wine." I don't think any
> one of you would expect the waiter to answer,"And your question is?" I
> also think the waiter does not expect me to ask 10 similar questions
> like "red wine 1991? red wine 1992? red wine 1993? until i hit
> something that is on the menu"
>
> So the final questions was, is there anything els on the menu besides
> PostgreSQL, like MySql for example ? If not I will take PostgreSQL
> please.
The 3.x branch just as the 2.x branch contains bindings to sqlite.
This you can use from day 1, the 3.0 release contains it.
Unless you have direct evidence to the contrary people should take what you
wrote with a grain of salt. In my experience Andy Dustman has been quite
responsive to inputs about MySQLdb, when those inputs happen in the forum he
inhabits. That forum is the MySQL forum tool on SourceForge:
http://sourceforge.net/forum/?group_id=22307
If you're curious about MySQLdb on Python 3.0 that is the place to ask. Of
course, like all open source software if you provide a patch in the project
tracker things will happen faster.
What I wrote is of course solely my own experience. When I needed to
use a database with python I looked around and tried to guess which db
binding is the most mature, stable, well-maintained, etc. Meaning, I'd
like to have the least amount of compilation/linking problems for both
windows and linux and I'd like to have the least amount of runtime
problems. I did what I guess anybody would have done: a google search
on the main database bindings. From this rather ad hoc research I
concluded that mysqldb has more problems than the other major
databases.
> In my experience Andy Dustman has been quite
> responsive to inputs about MySQLdb, when those inputs happen in the forum he
> inhabits.
I agree with you and I didn't say anything which contradicts your
statement. Being very responsive to problems is absolutely compatible
with having some problems.
> That forum is the MySQL forum tool on SourceForge:
>
> http://sourceforge.net/forum/?group_id=22307
>
> If you're curious about MySQLdb on Python 3.0 that is the place to ask. Of
> course, like all open source software if you provide a patch in the project
> tracker things will happen faster.
Sure, we agree again. But since my impression about the OP's question
was that his/her main intention is not really code contribution but
rather a solution to use, I'd say this is pretty much irrelevant for
the OP.
But yes, we agree on how development of open source projects go :)