GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — The sqlite3 module should not be built as a core module · Issue #106104 · python/cpython

The sqlite3 module should not be built as a core module #106104

New issue
Copy link
New issue
Copy link
Closed as not planned
Closed as not planned
The sqlite3 module should not be built as a core module#106104
Copy link
Assignees
erlend-aasland
Labels
extension-modulesC modules in the Modules dirC modules in the Modules dirtopic-sqlite3type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error

Description

@erlend-aasland
erlend-aasland
opened on Jun 26, 2023
Issue body actions

The sqlite3 extension module accidentally got upped as a core module (Py_BUILD_CORE_MODULE) in gh-105927. We'd like to keep most extension modules away from the internal API, so I'm reverting this specific change.

cc. @vstinner

Linked PRs

  • gh-106104: Use public weakref APIs in sqlite3 #106105

Activity

  1. erlend-aasland
    added
    type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
    extension-modulesC modules in the Modules dirC modules in the Modules dir
    topic-sqlite3
    on Jun 26, 2023
  2. erlend-aasland
    self-assigned this
    on Jun 26, 2023
  3. erlend-aasland
    added this to sqlite3 issueson Jun 26, 2023
  4. erlend-aasland
    added a commit that references this issue on Jun 26, 2023

    pythongh-106104: Use public weakref APIs in sqlite3

    43cbf83
  5. erlend-aasland
    linked a pull request that will close this issuegh-106104: Use public weakref APIs in sqlite3 #106105on Jun 26, 2023
  6. erlend-aasland
    moved this to In Progress in sqlite3 issueson Jun 26, 2023

  7. erlend-aasland commented on Oct 22, 2023

    @erlend-aasland
    erlend-aasland
    on Oct 22, 2023
    ContributorAuthor
    More actions

    As noted on the issue, I don't plan to follow this up. See #106105 (comment). If we decide to convert the _sqlite3 extension module to use the Limited API in the future, we can revisit this.

    Reacted by Victor Stinner
  8. erlend-aasland
    closed this as not plannedon Oct 22, 2023
  9. github-project-automation
    moved this from In Progress to Done in sqlite3 issueson Oct 22, 2023
  10. erlend-aasland
    moved this from Done to Discarded in sqlite3 issueson Oct 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @erlend-aasland
    erlend-aasland

Labels

extension-modulesC modules in the Modules dirC modules in the Modules dirtopic-sqlite3type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error

Projects

  • sqlite3 issues
    Status
    Discarded
    Show more project fields

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.