| Server IP : 101.53.144.229 / Your IP : 216.73.216.149 Web Server : Apache System : Linux host.gdigitalindia.in 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 User : digitalshiksha ( 1179) PHP Version : 5.6.40 Disable Function : eval,show_source,system,shell_exec,escapeshellarg,escapeshellcmd,proc_close,proc_open,ini_alter,dl,show_source,curl_multi_exechellcmd, ini_restore,apache_get_modules,get_cfg_var,passthru, exec ,proc_get_status,fpassthru,c999_buff_prepare,c999_sess_put,c99_buff_prepare,c99_sess_put,proc_close,ini_alter,dl,symlink,link,proc_close,ini_alter,dl,symlink,link,mail MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /proc/self/cwd/c1/1/proc/self/root/proc/self/root/usr/share/doc/python-pycurl-7.19.0/ |
Upload File : |
If you want to hack on pycurl, here's our list of unresolved issues:
NEW FEATURES/IMPROVEMENTS:
* Callback handling for stream seek.
* Add docs to the high-level interface.
DEFICIENICES:
* Using certain invalid options, it may be possible to cause a crash.
This is un-Pythonic behaviour, but you somewhere have to draw a
line between efficiency (and feature completeness) and safety.
There _are_ quite a number of internal error checks, but tracking
and catching all possible (deliberate) misuses is not a goal
(and probably impossible anyway, due to the complexity of libcurl).