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 larry
Recipients larry, lemburg, steve.dower, tim.golden, zach.ware
Date 2016-06-20.07:36:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1466408180.27.0.0873204690606.issue27355@psf.upfronthosting.co.za>
In-reply-to
Content
I can't tell if CPython ever really officially supported Windows CE or not.  There are some checkins around 2.5 that suggest there was at least partial support.  However posixmodule was supposed to be renamed "ce" on Windows CE, and that was never checked in.  (There was an external fork called "Python CE" for a while which *did* make this change.)

In any case, Windows CE support never survived the transition to Python 3.  It has clearly never even been compiled since Python 3.0 shipped.  In addition, the external "Python CE" project is dead; their last supported Python version was 2.5, back in 2007.  Windows CE appears to still be around as an embedded OS, but I don't think it's a user-visible OS.  The days of Windows CE palmtops is long gone.  And it's incontrevertably true: Python is no longer supported on Windows CE--if indeed it ever was.

So it's time for some late-spring cleaning!  The attached patch removes all remaining vestiges of Python's support for Windows CE.

A couple of minor questions/notes:

* I did a search-and-destroy for "ce", which lead me to _WIN32_WCE and MS_WINCE.

* I wasn't sure if I should touch Lib/platform.py.  (MAL?)

* I'm pretty sure I shouldn't touch config.sub, zlib, or ctypes.

Could one of you Windows guys apply the patch and tell me if anything blows up?
History
Date User Action Args
2016-06-20 07:36:23larrysetrecipients: + larry, lemburg, tim.golden, zach.ware, steve.dower
2016-06-20 07:36:20larrysetmessageid: <1466408180.27.0.0873204690606.issue27355@psf.upfronthosting.co.za>
2016-06-20 07:36:19larrylinkissue27355 messages
2016-06-20 07:36:19larrycreate