[Python-Dev] Who understands _ssl.c on Windows? (original) (raw)
Michael Hudson mwh at python.net
Sat Apr 8 10:13:45 CEST 2006
- Previous message: [Python-Dev] Who understands _ssl.c on Windows?
- Next message: [Python-Dev] Who understands _ssl.c on Windows?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
"Tim Peters" <tim.peters at gmail.com> writes:
Perhaps it's the case that doubles are aligned to an 8-byte boundary when socketmodule.c is compiled, but (for some unknown reason) only to a 4-byte boundary when ssl.c is compiled. Although that seems to match the details in the bug report, I have no theory for how that could happen (I don't see any MS packing pragmas anywhere).
Well, poking a bit reveals that _ssl and _socket are built by quite different mechanisms: _socket by a .vcproj but _ssl by "_ssl.mak". I don't see anything overly suspicious in _ssl.mak, but I don't really know much about Windows compiler options...
Cheers, mwh
--
so python will fork if activestate starts polluting it? I find it more relevant to speculate on whether Python would fork if the merpeople start invading our cities riding on the backs of giant king crabs. -- Brian Quinlan, comp.lang.python
- Previous message: [Python-Dev] Who understands _ssl.c on Windows?
- Next message: [Python-Dev] Who understands _ssl.c on Windows?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]