Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.freenet.ag!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
Date: Sun, 21 Apr 2013 23:46:27 +1000
Subject: Porting 2.x to 3.3: BaseHTTPServer
From: Chris Angelico <rosuav@gmail.com>
To: python-list@python.org
Content-Type: text/plain; charset=ISO-8859-1
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.879.1366551990.3114.python-list@python.org>
Lines: 25
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:44004

I'm porting an old project to Python 3, with the intention of making
one codebase that will still run on 2.6/2.7 as well as 3.2+ (or 3.3+,
if 3.2 is in any way annoying). My first step was to run the code
through 2to3, and the basics are already sorted out by that. Got one
question though, and it's more of an advice one.

In the current version of the code, I use BaseHTTPServer as the main
structure of the request handler. 2to3 translated this into
http.server, which seems to be the nearest direct translation. But is
that the best way to go about making a simple HTTP server?

Also, it's expecting bytes everywhere, and I can't find a simple way
to declare an encoding and let self.wfile.write() accept str. Do I
have to explicitly encode everything that I write, or is there a
cleaner way? (I could always make my own helper function, but would
prefer something standard if there's a way.)

The current version of the code is at: https://github.com/Rosuav/Yosemite

It's ugly in quite a few places; when I wrote most of that, I was
fairly new to Python, so I made a lot of naughty mistakes (bare except
clauses all over the place, ugh!). Adding support for Python 3 seems
like a good excuse to clean all that up, too :)

ChrisA