Bump libsqlite3-sys from 0.28 to 0.36#6472
Conversation
Update libsqlite3-sys to version 0.36 and adapt to API changes by replacing sqlite3_close_v2 with sqlite3_close. The v2 variant is no longer directly exported in the newer version. Fixes RustPython#6471
📝 WalkthroughWalkthroughUpdated libsqlite3-sys dependency from 0.28 to 0.36 and adjusted SQLite API usage to maintain compatibility: replaced Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Suggested reviewers
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Sorry, something went wrong.
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: Path: .coderabbit.yml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (2)
crates/stdlib/Cargo.tomlcrates/stdlib/src/sqlite.rs
🧰 Additional context used
📓 Path-based instructions (1)
**/*.rs
📄 CodeRabbit inference engine (.github/copilot-instructions.md)
**/*.rs: Follow the default rustfmt code style by runningcargo fmtto format Rust code
Always run clippy to lint Rust code (cargo clippy) before completing tasks and fix any warnings or lints introduced by changes
Follow Rust best practices for error handling and memory management
Use the macro system (pyclass,pymodule,pyfunction, etc.) when implementing Python functionality in Rust
Files:
crates/stdlib/src/sqlite.rs
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (11)
- GitHub Check: Run rust tests (ubuntu-latest)
- GitHub Check: Run snippets and cpython tests (ubuntu-latest)
- GitHub Check: Run snippets and cpython tests (macos-latest)
- GitHub Check: Run snippets and cpython tests (windows-latest)
- GitHub Check: Run rust tests (windows-latest)
- GitHub Check: Run rust tests (macos-latest)
- GitHub Check: Check the WASM package and demo
- GitHub Check: Run snippets and cpython tests on wasm-wasi
- GitHub Check: Ensure compilation on various targets
- GitHub Check: Check Rust code with clippy
- GitHub Check: Run tests under miri
🔇 Additional comments (3)
crates/stdlib/src/sqlite.rs (2)
33-33: LGTM! Import updated to match libsqlite3-sys v0.36 API.The import correctly switches from
sqlite3_close_v2tosqlite3_closeto align with the new library version's exported symbols.
1352-1359: LGTM! Type casts removed as SQLITE_TRACE_STMT now has the correct type.The explicit
as u32casts are no longer needed becauseSQLITE_TRACE_STMTis now properly typed asc_uintin libsqlite3-sys v0.36. This improves type safety.crates/stdlib/Cargo.toml (1)
135-135: The review comment's primary concern is incorrect. Web search confirms thatsqlite3_close_v2was not removed in libsqlite3-sys 0.36.0; the function remains available from the underlying SQLite library (added in SQLite 3.7.14). The code change to usesqlite3_closeis a deliberate API choice, not an adaptation to removal.The version bump from 0.28 to 0.36 is a standard update to the current stable release. v0.36.0 release notes document only additive changes: new bindings, hook-related code improvements, and a bump of the bundled SQLite to version 3.49.2—no breaking API removals.
Likely an incorrect or invalid review comment.
Sorry, something went wrong.
00205aa
into
RustPython:main
Dec 24, 2025
Fixes #6471
close #6467
close #6368
Update libsqlite3-sys to version 0.36 and adapt to API changes by
replacing sqlite3_close_v2 with sqlite3_close. The v2 variant is no
longer directly exported in the newer version.
ref
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.