[New-bugs-announce] [issue22579] Posix module init function name should not be compiler-dependent

Jeffrey Armstrong report at bugs.python.org
Wed Oct 8 15:26:55 CEST 2014

New submission from Jeffrey Armstrong:

The determination of the name of the posix module's initialization function (at Modules/posixmodule.c:12055)  is currently dependent on the compiler being used.  For MSVC, Watcom, or Borland, the name is defined as "PyInit_nt."  However, both Open Watcom and Borland have shipped compilers for GNU/Linux (and other platforms), making determining the posix module initialization function based on compiler incorrect.

Most other places in Modules/posixmodule.c correctly use the "MS_WINDOWS" preprocessor definition to determine if Windows routines should be used.  Naming the intialization function for the posix module should be dependent on this as well rather than compiler identifiers.  

Linking the interpreter natively with Open Watcom fails under GNU/Linux due to "PyInit_posix" being undefined.  This occurs because of the reasons described above.  The patch included corrects the issue.

components: Interpreter Core
files: posix_init.patch
keywords: patch
messages: 228789
nosy: Jeffrey.Armstrong
priority: normal
severity: normal
status: open
title: Posix module init function name should not be compiler-dependent
type: compile error
versions: Python 3.4
Added file: http://bugs.python.org/file36835/posix_init.patch

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list