Stack Bundle · Mid
Python / Django Developer Pack
Django's ORM, views, forms, admin and settings, plus Python language depth.
The Django-specific questions: ORM, migrations, middleware, signals and performance.
- Questions
- 360
- Topics
- 20
- Pages
- 273pages
- 360 questions, every one with a model answer
- Django ORM cheat sheet
- Migrations & signals
- Security defaults
Get the Python / Django Developer Pack — $9
One-off. Delivered as a PDF by email the moment payment clears.
Prices shown are a USD base. Your local-market price is calculated at checkout in your own currency, plus any local sales tax.
What is inside
20 chapters, in the order the interviews tend to ask them:
- The Python object model
- Functions, scopes and comprehensions
- Iterators, generators and coroutines
- Exceptions and context managers
- Type hints, dataclasses and protocols
- itertools, functools and collections
- Project layout, settings and the server stack
- Model fields, options and Meta
- Relations, joins and query counts
- Querysets, filters and expressions
- Migrations and schema history
- Forms, validation and error handling
- Views, URLs and class based views
- Templates, autoescaping and context
- Middleware, requests and responses
- Authentication, permissions and security defaults
- The admin site and contrib apps
- Testing Django applications
- Caching, sessions and performance
- Signals, async and background work
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
- Everything is an object, and attribute lookup consults the instance dictionary, then the type, then the MRO.
- Arguments are passed by object, so rebinding a parameter inside a function never changes the caller's variable.
- An iterator implements __iter__ and __next__, and a generator function gives you both from one body.
- Catching Exception hides programming errors, so catch the narrowest class you can actually handle.
- Annotations are documentation that the checker and some runtime tools read, not enforcement by the interpreter.
- itertools composes lazy iterators, so islice and takewhile avoid materialising the whole input.
Questions this pack covers
- When you read an attribute in Python, where does the interpreter actually look?
- Why do special methods have to be defined on the class rather than on the instance?
- Is Python pass by value or pass by reference?
- Why is a mutable default argument a bug?
- What two methods does a class need in order to be iterable?
- When does the body of a generator function actually run?
- Why is catching Exception usually the wrong choice in application code?
- What does raise ... from actually add to a traceback?
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
About this pack
- How many questions?
- 360, spread across 20 topics, written out in full across 273 pages.
- Do the answers just list keywords?
- No. Each answer is written as prose, because that is what you have to reproduce when someone asks you the question.
- How do I get it?
- Pay once and the PDF arrives by email immediately, with a signed download link.
- Can I get it refunded?
- Yes, if it is not what you expected. See the refund policy.
