[issue1745722] please add wsgi to SimpleXMLRPCServer
Changes by Sanjeev Paskaradevan : -- nosy: +Sanjeev ___ Python tracker <http://bugs.python.org/issue1745722> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1745722] please add wsgi to SimpleXMLRPCServer
Changes by Sanjeev Paskaradevan : -- keywords: +patch Added file: http://bugs.python.org/file29464/wsgi_xml_rpc.patch ___ Python tracker <http://bugs.python.org/issue1745722> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1745722] please add wsgi to SimpleXMLRPCServer
Changes by Sanjeev Paskaradevan : -- versions: +Python 3.4 -Python 3.2 ___ Python tracker <http://bugs.python.org/issue1745722> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9350] add remove_argument_group to argparse
Changes by Sanjeev Paskaradevan : -- nosy: +Sanjeev ___ Python tracker <http://bugs.python.org/issue9350> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9350] add remove_argument_group to argparse
Changes by Sanjeev Paskaradevan : -- keywords: +patch Added file: http://bugs.python.org/file29489/remove_argument_group.patch ___ Python tracker <http://bugs.python.org/issue9350> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9350] add remove_argument_group to argparse
Changes by Sanjeev Paskaradevan : -- versions: +Python 3.4 ___ Python tracker <http://bugs.python.org/issue9350> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9506] sqlite3 mogrify - return query string
Sanjeev Paskaradevan added the comment: An implementation of mogrify for pysqlite will necessarily be different from the Psycopg2 implementation because of the way queries are executed in Psycopg2 vs. pysqlite. In Pyscopg2 the arguments are bound into the query using mogrify and then executed using PQExec or PQsendQuery. Whereas the pysqlite implementation uses sqlite3 prepared statements to bind the parameters using the interfaces defined here: http://www.sqlite.org/c3ref/bind_blob.html As such, the pysqlite implementation never holds a "complete" sql statement with substituted parameters, as well, the sqlite3 C interfaces do not provide a way to retrive the complete statement. We can implement a 'mogrify' method for pysqlite but by necessity it would not be "exactly" the same as the psycopg2 implementation. For one thing the string thus generated would not be the statement that is sent to sqlite3. Should we implement a mogrify anyway? -- nosy: +Sanjeev ___ Python tracker <http://bugs.python.org/issue9506> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
