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.

classification
Title: distutils should support a custom list of exported symbols for Windows dlls.
Type: enhancement Stage:
Components: Distutils2 Versions: Python 3.3
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: tarek Nosy List: alexis, dholth, eric.araujo, tarek
Priority: normal Keywords:

Created on 2011-03-21 17:31 by dholth, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (3)
msg131677 - (view) Author: Daniel Holth (dholth) * Date: 2011-03-21 17:31
I would like to be able to use distutils to compile a shared library with a different set of exported symbols than the default.

In Windows, distutils only exports certain symbols needed for the Python module initialization API when it compiles a shared module. It does this by passing a file to the C compiler that lists those symbols. In Linux all symbols are exported/visible by default because that's just how the linker has traditionally worked.

I would like to be able to override or augment this list of symbols. Probably by just providing my own 'symbols to export' file.

distutils is definitely the poor man's compiler frontend but this feature would make it easier for me to support Windows (Python's secret shame.)
msg131700 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2011-03-21 22:53
Would you like to work on a patch?
msg165375 - (view) Author: Daniel Holth (dholth) * Date: 2012-07-13 12:33
I must have missed the export_symbols keyword argument to Extension(), or it was added.
History
Date User Action Args
2022-04-11 14:57:15adminsetgithub: 55833
2012-07-13 12:33:57dholthsetstatus: open -> closed
resolution: not a bug
messages: + msg165375
2011-03-21 22:53:01eric.araujosetnosy: tarek, eric.araujo, dholth, alexis
messages: + msg131700
2011-03-21 17:31:46dholthcreate