Outer Web | Explore

Explore >> Select a destination

You are here		doughellmann.com The Performance Impact of Using dict() Instead of {} in CPython 2.7 · Doug Hellmann
\|	\|	pymotw.com dis - Python Bytecode Disassembler - Python Module of the Week	4.4 parsecs away Travel
\|	\|	[AI summary] This technical guide explains how Python's dis module works to disassemble Python bytecode for purposes such as debugging errors and optimizing code performance through detailed stack analysis.	4.4 parsecs away Travel
\|	\|	blog.quarkslab.com Building an obfuscated Python interpreter: we need more opcodes - Quarkslab's blog	3.8 parsecs away Travel
\|	\|	Where building a custom obfuscated Python interpreter for a Python packer turned into an optimized Python interpreter.	3.8 parsecs away Travel
\|	\|	ashvardanian.com Our CPython bindings got 5x faster without PyBind11 ?? \| Ash's Blog	4.0 parsecs away Travel
\|	\|	Python's not the fastest language out there. Developers often use tools like Boost.Python and SWIG to wrap faster native C/C++ code for Python. PyBind11 is the most popular tool for the job not the quickest. NanoBind offers improvements, but when speed really matters, we turn to pure CPython C API bindings. With StringZilla, I started with PyBind11 but switched to CPython to reduce latency. The switch did demand more coding effort, moving from modern C++17 to more basic C99, but the result is a 5x lower ...	4.0 parsecs away Travel
\|	\|	gist.github.com pair_init.h · GitHub	13.2 parsecs away Travel
\|		GitHub Gist: instantly share code, notes, and snippets.	13.2 parsecs away Travel