Author stutzbach
Recipients amaury.forgeotdarc, benjamin.peterson, brian.curtin, bwalker, rpetrov, stutzbach, tim.golden
Date 2010-08-23.23:58:10
SpamBayes Score 3.36194e-11
Marked as misclassified No
Message-id <1282607892.63.0.623211028076.issue9665@psf.upfronthosting.co.za>
In-reply-to
Content
> Why would this not be required for the standard exceptions then?

It looks like PyAPI_DATA can be defined differently depending on whether we're building code as a built-in or as a loadable module.  If _iomodule.c is really being built as a module, that would explain why there's a difference.  The standard exceptions are always built-in.

In Python 2.7, _io is not the default I/O system for Python, so I could understand why it might be a loadable module there.  Of course, if Amaury is right that it's being built both ways then I assume that could be the underlying problem.

Also, the definition of PyAPI_DATA has a bunch of conditions specifically for Cygwin, which (partially) explains why the behavior is different from a regular Windows build.

I am not an export on the dllimport and dllexport keywords, although I have needed to use them on occasion.  I am speculating.
History
Date User Action Args
2010-08-23 23:58:13stutzbachsetrecipients: + stutzbach, amaury.forgeotdarc, tim.golden, benjamin.peterson, rpetrov, brian.curtin, bwalker
2010-08-23 23:58:12stutzbachsetmessageid: <1282607892.63.0.623211028076.issue9665@psf.upfronthosting.co.za>
2010-08-23 23:58:11stutzbachlinkissue9665 messages
2010-08-23 23:58:10stutzbachcreate