Guido van Rossum <guido@python.org> writes: > I never have to do that; the dependencies in the project file make > sure that the extensions are all built when you build the 'python' > project. Are you sure? If the python target is up-to-date (i.e. nothing has to be done for python_d.exe), and I delete all generated _sre files (i.e. sre_d.pyd, and the object files), and then ask VC++ 6 to build the python target, nothing is done. Indeed, I cannot find any place where it says that the python target is related to _sre. I can only see dependencies with pythoncore. Can you (or any other regular pcbuild.dsp user) please guess what I'm doing wrong? > Maybe _sre is used by most apps (though I doubt even that). But > _socket, select, winreg, mmap and the others are definitely not. On > Unix, all extensions are built as shared libraries, except the ones > that are needed by setup.py to be able to build extensions; it looks > like only posix, errno, _sre and symtable are built statically. I do believe that is a mistake, as it will increase startup time of applications that need them; applications that don't need them would not be hurt if they were in the python binary. > I'd say that making more extensions static on Windows would increase > start time of modules that don't use those extensions. I guess I have to measure these things. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4