➜

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 meador.inge
Recipients amaury.forgeotdarc, belopolsky, benjamin.peterson, christian.heimes, dmi.baranov, ezio.melotti, jaraco, meador.inge, techtonik
Date 2013-08-20.01:42:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAK1QoopOr=DLZNEg0g33yy1-B_CSxx58=LdMUJ_K8LCTiuv0Cg@mail.gmail.com>
In-reply-to <1376309480.35.0.803170349404.issue16396@psf.upfronthosting.co.za>
Content 
On Mon, Aug 12, 2013 at 7:11 AM, Ezio Melotti <report@bugs.python.org>wrote:

> Even if the patch is applied only on 3.4, I would still like to see the
> ValueError turned into ImportError for 2.7/3.3.
>

Why not raise an ImportError for all versions?  I don't see how
'ctypes.wintypes' is ever actually useful on anything but Windows.
 Allowing it to successfully import on non-Windows systems seems misleading.
History
Date User Action Args
2013-08-20 01:42:30meador.ingesetrecipients: + meador.inge, amaury.forgeotdarc, jaraco, belopolsky, techtonik, christian.heimes, benjamin.peterson, ezio.melotti, dmi.baranov
2013-08-20 01:42:30meador.ingelinkissue16396 messages
2013-08-20 01:42:29meador.ingecreate