John Nagle wrote:
> On 7/4/2010 6:36 PM, Philip Semanchuk wrote:
>> hi Tim,
>> This seems more likely to be a MySQLdb problem than a Python one.
Have
>> you considered asking in the MySQLdb forums?
>>
>> On Jul 4, 2010, at 7:46 PM, Tim Johnson wrote:
>>
>>> Using python 2.6.4 on slackware 13.1
>>
* Philip Semanchuk [100704 18:13]:
> hi Tim,
> This seems more likely to be a MySQLdb problem than a Python one.
You are correct
> Have you considered asking in the MySQLdb forums?
Didn't know there was one!
where is it?
I will join
thanks
tim
> On Jul 4, 2010, at 7:46 PM, Tim J
On 7/4/2010 6:36 PM, Philip Semanchuk wrote:
hi Tim,
This seems more likely to be a MySQLdb problem than a Python one. Have
you considered asking in the MySQLdb forums?
On Jul 4, 2010, at 7:46 PM, Tim Johnson wrote:
Using python 2.6.4 on slackware 13.1
I have MySQLdb 'by hand', that is: by
1)d
hi Tim,
This seems more likely to be a MySQLdb problem than a Python one. Have
you considered asking in the MySQLdb forums?
On Jul 4, 2010, at 7:46 PM, Tim Johnson wrote:
Using python 2.6.4 on slackware 13.1
I have MySQLdb 'by hand', that is: by
1)downloading MySQL-python-1.2.3c1.tar.gz
2)un
Using python 2.6.4 on slackware 13.1
I have MySQLdb 'by hand', that is: by
1)downloading MySQL-python-1.2.3c1.tar.gz
2)unzipping tarfile
3)running python setup.py build
4)running python setup.py install
The build and install seemed to proceded without error,
but upon invoking the interpreter and r
