René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"sqlite: Raise ProgrammingError when operating on a closed connection in Blob methods","articleBody":"Currently, the `sqlite3` module does not strictly enforce checks when methods are called on a `Blob` instance if the underlying connection is closed. While the `read()` method includes this check, other methods do not, leading to potential inconsistencies with CPython behavior.\n\n**Expected Behavior**\nTo match CPython's behavior, calling blob methods like `write()`, `tell()`, `seek()`, etc., on a closed database connection should raise a `sqlite3.ProgrammingError`.\n\n**Context**\nThis issue was identified during the review of PR #6286. The following methods in `crates/stdlib/src/sqlite.rs` are missing the `self.connection.is_closed()` check before calling `self.inner(vm)`:\n\n- `write()`\n- `tell()`\n- `seek()`\n- `__enter__()`\n- `__exit__()`\n- `__getitem__` (subscript)\n- `__setitem__` (ass_subscript)\n\n**Reference**\n- PR: https://github.com/RustPython/RustPython/pull/6286\n- Review comment: https://github.com/RustPython/RustPython/pull/6286#discussion_r2549598814","author":{"url":"https://github.com/ever0de","@type":"Person","name":"ever0de"},"datePublished":"2025-11-22T16:11:09.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/6289/RustPython/issues/6289"}