➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients vstinner
Date 2014-10-09.21:15:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1412889343.74.0.168731015987.issue22591@psf.upfronthosting.co.za>
In-reply-to
Content 
In the C code of Python 3.5, there are still preprocessor commands checking for defines:

- __BORLANDC__: Borland C compiler
- __WATCOMC__: Watcom C compiler
- __DJGPP__: MS-DOS port of GCC

In 2014, it's time to drop this old code. OS/2 support was already removed in Python 3.4 (see the PEP 11).

I'm quite sure that Python 3.5 cannot be compiled on MS-DOS and/or will not work on MS-DOS. I don't think that anyone tried Python 3 on MS-DOS. The MS-DOS support was simply inherited from Python 2, Python 3 source code is based on Python 2.

I don't want to drop support of custom compilers, only removing code specific to MS-DOS, see:
http://bugs.python.org/issue22579#msg228908
History
Date User Action Args
2014-10-09 21:15:43vstinnersetrecipients: + vstinner
2014-10-09 21:15:43vstinnersetmessageid: <1412889343.74.0.168731015987.issue22591@psf.upfronthosting.co.za>
2014-10-09 21:15:43vstinnerlinkissue22591 messages
2014-10-09 21:15:43vstinnercreate