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 terry.reedy
Recipients eric.fahlgren, miss-islington, paul.moore, ronaldoussoren, serhiy.storchaka, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2018-06-12.21:32:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1528839150.84.0.947875510639.issue33656@psf.upfronthosting.co.za>
In-reply-to
Content
I confirmed that IDLE did not import ctypes before this issue.  Serhiy, I presume that the new code can be skipped, you are suggesting replacing

import ctypes
<use ctypes....>

with

try:
    import ctypes
except ImportError:
    pass  # The ctypes-using fix is not essential.
else:
    <use ctypes...>

But, in what sense is ctypes optional *on Windows* more than most other modules?  I don't see anything in the ctypes doc.  It is normal to depend on stdlib modules being present and not wrap imports.

Steve: does the Windows installer have an option to omit ctypes?  I don't remember one.  

Anyone: do you know of any CPython Windows distributions that we care about that omit ctypes?

Which of the following best describes the situation?
1. This is a theoretical concern that does not justify adding noise to the code.
2. This is a real concern, but so rare that the fix can be deferred to 3.6.7 and 3.7.1.
3. This is likely common enough that we should ask Ned to cherry-pick the patch into 3.6.6 and 3.7.1.
History
Date User Action Args
2018-06-12 21:32:30terry.reedysetrecipients: + terry.reedy, paul.moore, ronaldoussoren, tim.golden, zach.ware, serhiy.storchaka, steve.dower, eric.fahlgren, miss-islington
2018-06-12 21:32:30terry.reedysetmessageid: <1528839150.84.0.947875510639.issue33656@psf.upfronthosting.co.za>
2018-06-12 21:32:30terry.reedylinkissue33656 messages
2018-06-12 21:32:30terry.reedycreate