cgi multipart bugs in py3k

Recently I started to implement a small web app in py3k and wsgi. While none of the major python web frameworks are ready for py3k anytime soon and wsgi for py3k is still under major discussions (see for example this current post by Armin Ronacher), there are already options to actually start working on the subject.

I'm using bottle (dev tree) and the current releases of sqlalchemy, py-postgresql and jinja2 on Python 3.1.2. This actually works sort of. I will likely write some further posts about my progress. However, I quickly found a bug in the cgi multipart input handling, which actually turned out to arise from two different sources. I tried to solve it and just opened issue 8846 on the Python issue tracker showing my findings.


1. organic search engine optimization -- 12 years ago

hey and thank you to your info I have definitely picked up anything new from right here. I did on the other hand experience several technical points the use of this website, since I experienced to reload the site many instances previous to I could get it to load correctly. I were thinking about if your web host is OK?

2. Andre Wobst -- 12 years ago

I observed the layout issue myself very rarely before, but never looked at it as it was really rare and quite bizarre. But trying again now, using the Chrome browser, I got this error quite frequently as well. Looks like it is related to – I got the varying broken content-type headers again and again as described in the bug report. After an update of mod_wsgi is seems to be fixed. Great, thanks for bringing up this issue.

Add New Comment