Re: mysqldb error
Hi, SeLinux is not installed. iptables output is : mikropyuvasi:~# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source - i'll commit suicide :) i think it is related with: http://www.modpython.org/FAQ/faqw.py?req=show&file=faq02.013.htp but i didn't understand.
strict_parsing parameter in forms handling.
The util.FieldStorage class, plus parse_qs and parse_qsl functions
take a
parameter called strict_parsing. All the documentation says is:
The \var{strict_parsing} argument is not yet implemented.
Ie., it doesn't even say what it is meant to be for.
Does anyone know what it is meant to be for. The closest I could find as
to what it may be for is from cgi.FieldStorage documentation:
strict_parsing: flag indicating what to do with parsing errors.
If false (the default), errors are silently ignored.
If true, errors raise a ValueError exception.
I don't know though what constitutes an error though.
This argument has been there back from mod_python 2.X. If it is never
going
to be implemented, is there any point really keeping it in the API?
Graham
Re: mysqldb error
On 13/04/2006, at 8:33 PM, Firat KUCUK wrote: i think it is related with: http://www.modpython.org/FAQ/faqw.py?req=show&file=faq02.013.htp but i didn't understand. If that is the case, it is easy to check. This is done by disabling the loading into Apache of PHP support. If after commenting out the PHP lines and doing a "stop/start" of Apache (best not to use "restart" just in case it doesn't unloaded shared libraries properly) your problem doesn't go away, then that FAQ entry is not relevant. Graham
Re: Progressing 3.2.9.
On 12/04/2006, at 10:13 PM, Graham Dumpleton wrote: On 11/04/2006, at 12:47 PM, Jim Gallacher wrote: MODPYTHON-93 Improved FieldStorage Not yet done. Also haven't done logging additions listed under MODPYTHON-158. Now also both done. At this point, if there is anything else that anyone feels should be back ported from the 3.3 development tree to 3.2.x branch, speak now or forever hold your peace. If you are unsure of what work has been done on 3.3 so far, see resolved issues: http://issues.apache.org/jira/secure/IssueNavigator.jspa? reset=true&pid=10640&status=5 At this point, we are probably only after changes which have some impact and would be better addressed now rather than later. Thus, feel free to put your case, but don't get too carried away. I can see maybe a few little things that could also be done, but I'll post about that tomorrow as getting late again and time for me to get some sleep. :-) Graham
Re: mysqldb error [solved]
Hi Guys, php5 uses libmysqlclient12 as default i made symbolic link like this: ln -s libmysqlclient.so.14.0.0 libmysqlclient.so.12 problem fixed. thanks to all. you are wonderful. ;)
Re: mysqldb error [solved]
On 13/04/2006, at 9:30 PM, Firat KUCUK wrote: Hi Guys, php5 uses libmysqlclient12 as default i made symbolic link like this: ln -s libmysqlclient.so.14.0.0 libmysqlclient.so.12 problem fixed. I would strongly recommend against doing this as any difference in the API or object layouts will now possibly cause PHP scripts to crash. You really should rebuild one or the other of Python MySQL module or PHP so they have both been compiled against the same version library. Graham
Re: mysqldb error [solved]
Graham Dumpleton yazmış: On 13/04/2006, at 9:30 PM, Firat KUCUK wrote: Hi Guys, php5 uses libmysqlclient12 as default i made symbolic link like this: ln -s libmysqlclient.so.14.0.0 libmysqlclient.so.12 problem fixed. I would strongly recommend against doing this as any difference in the API or object layouts will now possibly cause PHP scripts to crash. You really should rebuild one or the other of Python MySQL module or PHP so they have both been compiled against the same version library. Graham yes you are right, now php mysql connection failed. thanks.
