You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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 nosqlite3
module available, because all of thesqlite3
just assumes that there is a_sqlite3
module available, which isn't the case when disabling the module. This isn't limited to thesqlite3
component but for various other components too.Is this intended behavior? How does upstream handle this?
The text was updated successfully, but these errors were encountered: