/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 tenthousandmeters.com
Python behind the scenes #3: stepping through the CPython source code
| | dygalo.dev
Rust for a Pythonista #3: Python bindings
5.0 parsecs away

Travel
| | Sometimes we need to extend existing Python projects with other languages to solve performance issues or to include some functionality already written in another language. In this chapter, we will create a full-featured Python integration for a Rust crate we built in the previous article. As the primary goal, I want to focus on a pleasant end-user experience and share tips on improving the usability and debuggability of the resulting library.
| | nikhilism.com
Diving into the Python call stack (PyGotham 2018) - Nikhil's blog
3.2 parsecs away

Travel
| | [AI summary] A technical post explaining how Dropbox engineers reverse-engineered CPython's internal memory structures to implement robust Python stack tracing within their out-of-process crash reporting tool, Crashpad.
| | doughellmann.com
The Performance Impact of Using dict() Instead of {} in CPython 2.7 ยท Doug Hellmann
2.9 parsecs away

Travel
| | [AI summary] A technical analysis reveals that using the dictionary constructor dict() instead of the literal syntax {} in CPython 2.7 results in significantly higher performance costs due to extra function call overhead and intermediate memory allocations.
| | viralinstruction.com
The borrowchecker is what I like the least about Rust
18.8 parsecs away

Travel
| [AI summary] The author argues that Rust's borrowchecker causes serious ergonomic problems and overstates its role in memory safety, suggesting that the effort required to satisfy it often outweighs the benefits compared to garbage-collected languages.