[issue21718] sqlite3 cursor.description seems to rely on incomplete statement parsing for detection
Tom Tanner added the comment: will the fix be backported to 2.7? -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue21718> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21718] sqlite3 cursor.description seems to rely on incomplete statement parsing for detection
Tom Tanner added the comment: is this going to be fixed in 2.7.10? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21718 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21114] wsgiref.simple_server doesn't handle multi-line headers correctly
Tom Tanner added the comment: The patch is waiting for inclusion in 2.7.10 :/ -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21114 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21114] wsgiref.simple_server doesn't handle multi-line headers correctly
Tom Tanner added the comment: Any chance to get this into 2.7.10? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21114 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21718] sqlite3 cursor.description seems to rely on incomplete statement parsing for detection
Tom Tanner added the comment: Are you going to merge it into 2.7.10? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21718 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21114] wsgiref.simple_server doesn't handle multi-line headers correctly
Tom Tanner added the comment: ping -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21114 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21114] wsgiref.simple_server doesn't handle multi-line headers correctly
Tom Tanner added the comment: attached is the updated patch, which unfolds multiline headers but not validate them (tests included). -- Added file: http://bugs.python.org/file37409/wsgi2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21114 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21114] wsgiref.simple_server doesn't handle multi-line headers correctly
Tom Tanner added the comment: This is actually more complicated than I initially thought. According to https://www.python.org/dev/peps/pep-/#the-start-response-callable Each header_value must not include any control characters, including carriage returns or linefeeds, either embedded or at the end. (These requirements are to minimize the complexity of any parsing that must be performed by servers, gateways, and intermediate response processors that need to inspect or modify response headers.) There's a discussion at https://mail.python.org/pipermail/web-sig/2006-September/002244.html It think the spec should be changed as parsing multi-line headers is really simple and sometimes necessary (e.g., when passing the X.509 client certificate). Anyway, attached you find a patch for Python 2.7.8 which includes a test and allows CR/LF in header values. -- Added file: http://bugs.python.org/file37401/wsgi.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21114 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21114] wsgiref.simple_server doesn't handle multi-line headers correctly
Tom Tanner added the comment: I confirm this fixes a bug. To reproduce it just add, e.g. X-Multline-Header: foo bar to your request. It has been fixed in Python 3 with https://github.com/python/cpython/commit/67dcb80f6e102622e4aa888930d3017fed9834de -- nosy: +tanner ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21114 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21718] sqlite3 cursor.description seems to rely on incomplete statement parsing for detection
Tom Tanner added the comment: ping I'd appreciate a review of my patch. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21718 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21718] sqlite3 cursor.description seems to rely on incomplete statement parsing for detection
Tom Tanner added the comment: this patch fixes the bug. It parses the with WITH statement. -- keywords: +patch nosy: +tanner Added file: http://bugs.python.org/file36950/with.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21718 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21718] sqlite3 cursor.description seems to rely on incomplete statement parsing for detection
Changes by Tom Tanner pyt...@tannerlab.com: Removed file: http://bugs.python.org/file36950/with.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21718 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21718] sqlite3 cursor.description seems to rely on incomplete statement parsing for detection
Changes by Tom Tanner pyt...@tannerlab.com: Added file: http://bugs.python.org/file36952/with2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21718 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue602345] option for not writing .py[co] files
Tom Tanner added the comment: Is there likely to be any action on this. We can get issues with the creation of .pyc files due to our build setup. We can get situations where we run builds in parallel on 2 different architectures. Our build is set up so that anything generated by compilers end up in individual architecture specific directories, but we cannot do this with python. We are also using clearmae, which has its own build avoidance features, which get thoroughly confused by the generation of these files) End result is one of 1) We get corrupt .pyc files 2) The build breaks 3) We rebuild things we don't need to. We'd be very grateful for a way of suppressing the generation of .pyc files completely. -- nosy: +thosrtanner Tracker [EMAIL PROTECTED] http://bugs.python.org/issue602345 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
