Structuring Python Projects
Hey, there's already a Hitchhiker's Guide to Python! This is quite comprehensive on the Python development basics.
GIL required to run bytecode, but not when waiting on I/O - can switch to different thread. CPython has macros to release and re-aquire GIL which can be used if extension does not need to run python bytecode/do any kind of ref-count changes (e.g. sleep, read/write files, network socket, numpy, image processing(?)). Cannot share GIL in CPU-bound code. CPU-bound "check" every 100 ticks to allow switching. Note: I/O doesn't often block unless you are flushing - OS buffers. Note: Threads/Processes result in CPU context switches, while async does not.
Pure CPU: Process <---> Threads <---> Async: Pure I/O (Many "Connections"/Slow I/O).
Async I/O clearly delineates the context switch locations.
|No CPU Context Switches|
|Shared memory can result in race conditions.||No race conditions.. usually.|
|No dead locks.. usually.|
|Costly.||Each thread has its own stack.||Shared Stack. Uses an executor pool to run sync tasks in a background thread (this uses additional resources)|
Python 2 -> 3: Strings/Bytes, Print, Super() - new style classes, division.
- pycodestyle (formerly pep8)
- Layer Linter (not tried)
- pyroma for libraries (setup.py)
- Dataclasses TBD: talk link.
- Postponed evaluation of type annotations
- dicts officially respect insertion-order
- time - nanosecond resolution functions
- f-string literals
- underscores in numeric literals
- extended variable annotations
- (async generators & comprehensions)
- Local Time Disambiguation
- secrets module
- unicode vs bytes
- print() vs print
- division float vs int
- new-style vs classic classes
- relative imports (?)
- views and iterators vs lists (e.g. dict.items() == dict.iteritems())
- extended iterable unpacking
- set literals
- removed tuple parameter unpacking
- Remember to index on ForeignKeys. Postgres does not do this automatically. MySQL always does this.
- Remember to set
ondeletecascades on ForeignKeys.