You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Strip out the last lingering vestiges of Windows CE support #71542
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/larryhastings'closed_at=<Date2016-09-05.22:12:16.270>created_at=<Date2016-06-20.07:36:20.196>labels= ['interpreter-core', 'tests', 'type-feature', 'library']
title='Strip out the last lingering vestiges of Windows CE support'updated_at=<Date2016-09-06.02:20:11.866>user='https://github.com/larryhastings'
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.
Doesn't break anything in a x64 build for me. Modules/_ctypes/libffi_arm_wince/ should also be removed, though (it's a private, ancient copy of libffi that has never actually been used as far as I can tell).
Nosying two people who I know worked on the port originally, just in case they have an opinion about removing WinCE.
(Remind me. Why is our private copy of libffi a divergent unmaintained fork? libffi still gets updates; last update was two years ago. Why can't we just... update ours?)
Activity
larryhastings commentedon Jun 20, 2016
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?
zware commentedon Jun 20, 2016
+1
Doesn't break anything in a x64 build for me. Modules/_ctypes/libffi_arm_wince/ should also be removed, though (it's a private, ancient copy of libffi that has never actually been used as far as I can tell).
larryhastings commentedon Jun 20, 2016
Nosying two people who I know worked on the port originally, just in case they have an opinion about removing WinCE.
(Remind me. Why is our private copy of libffi a divergent unmaintained fork? libffi still gets updates; last update was two years ago. Why can't we just... update ours?)
zware commentedon Jul 29, 2016
See bpo-23085 for more about our libffi situation.
For this issue, with silence from Tim and Mark I say commit at will (and kill Modules/_ctypes/libffi_arm_wince/ as well).
larryhastings commentedon Sep 5, 2016
Refreshed the patch. With a Misc/NEWS entry I think it's ready for checkin. WFM on Linux 64-bit with gcc; can I get people to try other platforms?
zooba commentedon Sep 5, 2016
I'm building on Windows now.
zware commentedon Sep 5, 2016
LGTM on Win32, Win64, and OSX.
python-dev commentedon Sep 5, 2016
New changeset 7a2eccee823b by Larry Hastings in branch 'default':
Issue bpo-27355: Removed support for Windows CE. It was never finished,
https://hg.python.org/cpython/rev/7a2eccee823b
larryhastings commentedon Sep 5, 2016
Committed. Bye bye Windows CE!
python-dev commentedon Sep 6, 2016
New changeset 0ce745bb7717 by Martin Panter in branch 'default':
Issue bpo-27355: Import no longer needed
https://hg.python.org/cpython/rev/0ce745bb7717