We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Code reloading techniques in Python

Formal Metadata

Title
Code reloading techniques in Python
Subtitle
Cold and hot code reloading, the different options, how they work and when to use them.
Title of Series
Number of Parts
542
Author
Contributors
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
While iterating rapidly on Python code, we want to see the result of our changes rapidly. In this talk, we will review the different techniques available to reload Python code. We will see how they work and when each is the best fit. Please note that this talk replaces one titled "The future of Python's asyncio" that was due to have been given by Jonathan Slenders, who has sent his apologies but is now unable to attend as he has fallen ill. We wish him a speedy recovery. The talk will cover both cold and hot reload techniques: Cold reload techniques reset the application state between each reload. Examples include Django and Flask's autoreload tools. Hot reload techniques keep the application state despite the code changing. These include Jupyter kernels and 'reloadr' [1], an open-source module developed by the speaker to allow stateful hot code reloading. AMENDMENT: Please note that this talk replaces one titled "The future of Python's asyncio" that was due to have been given by Jonathan Slenders, who has sent his apologies but is now unable to attend as he has fallen ill. We wish him a speedy recovery.