Porting Python

deckerben bdeck at lycos.co.uk
Wed Jun 11 00:18:20 CEST 2003


"DB_RobertP" <member31018 at dbforums.com> wrote in message
news:2986845.1055280214 at dbforums.com...
> Does anyone know if there are any useful links to places that document
> the porting process of Python to other platforms? If anyone is
> familiar with
> python porting, any pointers would be helpful. I'm new to python and

Hello Robert,

I came to this site about a year ago 'looking for a scripting language' to
replace my slow-moving batchfiles. I still wanted a DOS based solution, so
using DJGPP, I did several quick and dirty ports... one of which was Python.
I was not familiar with Python at all, then. After having recieved a lot of
good advice here and from the DJGPP folks, the port grew and became
successful. Thousands of people have since visited
http://members.lycos.co.uk/bdeck to read about and download PythonD (I'm not
kidding).

The policy I recommend is:
1. Start with a good development platform and C compiler. This was the most
critical descision for the DOS port.
2. Know exaclty which posix functions your platform supports, and which ones
they don't. Understand how the python source code works.
3. Offer features. If you don't have them, find them. Example: PythonD's
popularity rocketed when we made the first release that supported dynamic
linking and the building of distutils scripts.
4. Port a clean package. Identify bugs ASAP and move quick to fix them. Run
the test suite (regrtest.py).
5. Use your own software. I myself do all my python programming with
PythonD, and all scripts I write were tested  using PythonD.
6. Let others know. Even the best port won't do anyone any good, if they
don't know it's out there for them. Set up a website, or at least use
someone else's (that's what I first did, too).


Hope this helps a bit. Best wishes.
Ben










More information about the Python-list mailing list