Issue 1351020: PythonD DJGPP-specific patch set for porting to DOS. (original) (raw)

Created on 2005-11-08 08:08 by bdeck, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (8)
msg48990 - (view)	Author: Ben Decker (bdeck) *	Date: 2005-11-08 08:08
This is our initial recommendation for PythonD specific patch set running in DOS. Build requires at least DJGPP 2.04 32-bit DOS compiler (see http://www.delorie.com/djgpp/) and Watt-32 tcp/ip stack for DJGPP (see http://www.bgnett.no/~giva/). Operates under MSDOS, FreeDOS, Win32 and NT. Requires DOS mode long filename driver/TSR. See http://www.caddit.net/pythond.htm for details concerning the PythonD project. Diffed against 2.4.2 Final distribution. Diff script used: #! /usr/bin/bash for file in `find . -name *.orig -print` do export filename=`echo -n file∥sed−e′s/.origfile | sed -e 's/\.origfile∥sed−e′s/.orig//'` diff -c filefile filefilename >> pythond.diff done
msg48991 - (view)	Author: Martin v. Löwis (loewis) *	Date: 2006-11-08 06:32
Logged In: YES user_id=21627 Can you please update the patch to the current subversion trunk? Please integrate 1351036 also, providing only a single patch. There are a number of problems with that patch: - what is the purpose of the site.py changes? Some parts (like a plain print statement) certainly have no place, other parts (like readline history support) traditionally belong to the user's PYTHONSTARTUP. Integrating them into Python might be an option, but that is independent of the patch. - please make the C block structure "work" even in presence of ifdefs. I.e. when you change the condition of a while loop, duplicate the entire while loop (which is just --i in one case), or introduce a macro to compute the condition. In several cases of posixmodule.c, introducing IS_SEP might be useful. - remove debugging code, even if commented out - why do you put the thread module into config.c.in? It's normally included through Setup.config - Don't use C++ comments
msg83883 - (view)	Author: Daniel Diniz (ajaksu2) *	Date: 2009-03-20 23:12
Any news on this?
msg83886 - (view)	Author: Ben Decker (bdeck) *	Date: 2009-03-20 23:30
Our next target will probably be somewhere with Python 3
msg84455 - (view)	Author: Daniel Diniz (ajaksu2) *	Date: 2009-03-30 01:56
Leaving open, then :)
msg115228 - (view)	Author: Mark Lawrence (BreamoreBoy) *	Date: 2010-08-30 16:43
@Ben are you still interested in this or can it be closed?
msg115234 - (view)	Author: Antoine Pitrou (pitrou) *	Date: 2010-08-30 17:34
I don't think there's any point in including DJGPP support in the Python tree (DJGPP targets MS-DOS, which is completely marginal today). Furthermore, the patch has no chance of applying cleanly on the current source tree. I would suggest that people interested in a DJGPP port of Python mantain their patches themselves instead, it will be far easier and more efficient.
msg115251 - (view)	Author: Ben Decker (bdeck) *	Date: 2010-08-31 04:32
Closed then. The next patch will posted at http://www.caddit.net/pythond/when we get around to doing a version 3 port. Frankly, as the current v2 binary meets most remaining requirements on this legacy platform, we are left with modern syntax compatibility as primary (only) impetus for further patches.