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.22:00:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As a follow-up of the issue #22591, I propose to drop support of the Borland C compiler.

In 2000, it was nice to support Visual Studio and Borland C++ Builder, because they were the two most popular compilers on Windows. Borland C compiler could also be used on MS-DOS.

But Borland stopped the development of its C compiler, it looks like the last release is Borland C++ Builder, which was released in 2000 (I'm not sure). So this proprietary compiler is now 14 years old.

Python now focus on Visual Studio support. Microsoft gives us free licenses and a developer of Microsoft will probably build our binaries for Python 3.5. So Borland C++ Builder support is now almost useless.

On Windows, I would prefer to focus our effort on open source compilers like GCC or OpenWatcom(v2). See for example the issue #22579.
Date User Action Args
2014-10-09 22:00:53vstinnersetrecipients: + vstinner
2014-10-09 22:00:53vstinnersetmessageid: <>
2014-10-09 22:00:53vstinnerlinkissue22592 messages
2014-10-09 22:00:52vstinnercreate