Skip to content

Installation of python standard library modules despite disabled components. #112

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
adrianbroher opened this issue Feb 28, 2016 · 1 comment

Comments

@adrianbroher
Copy link
Contributor

This is not an issue, but rather a request for enhancement or general question.

When disabling a specific component, e.g. ENABLE_SQLITE3=OFF the coresponding .pyd file is not build. However the installation of the python standard library still contains the sqlite3 module. My naive assumption would be that in this case there would be no sqlite3 module available, because all of the sqlite3 just assumes that there is a _sqlite3 module available, which isn't the case when disabling the module. This isn't limited to the sqlite3 component but for various other components too.

Is this intended behavior? How does upstream handle this?

@jcfr
Copy link
Contributor

jcfr commented Mar 25, 2016

How does upstream handle this?

Upstream systematically install all modules: https://github.com/python/cpython/blob/1cf866a6569d492a94ce0f7dca26a82c0e755b0c/Makefile.pre.in#L1236-L1281

The add_python_extension CMake function could probably be extended to list subdirectory that should be installed.

@jcfr jcfr added the Type: Bug Something's not working correctly. label Feb 15, 2017
@jcfr jcfr removed the Type: Bug Something's not working correctly. label Jun 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants