Tuesday, 01 September 2026 – XI CS

Tuesday, 01 September 2026

Lecture 42 of 73 · Unit 2

Unit 2 ⏳ Pending

Unlocks at 05:00 PM, 01 Sep 2026

Data types, mutability and object identity Theory part 2

What We'll Learn

A quick overview of today's lecture

Data types, mutability and object identity Theory part 2 Concept ID: XI_U2_DATA_TYPES_MUTABILITY_IDENTITY. Primary Sub-subtopic: Data types, mutability and object identity. Question-bank grouping: Python Basics and Data Concepts. Use this lecture for theory, examples, misconceptions, and short PYQ checks mapped to this concept ID.

Key things we'll cover

Data types, mutability and object identity

PYQ references used by all prompt types 12 included

Flagged questions are excluded from Study Notes, PPT, and Student Notes references until corrected in Paper Analyzer.

Included ID 1356 · 2025 · 2 mark(s)

Draw a flowchart for a program that accepts an integer input from the user and checks whether the number is even or odd. Display the appropriate message based on the result.

Python Basics and Data Concepts → Data types, mutability and object identity

Included ID 1403 · 2025 · 2 mark(s)

(b) What is None in Python?

Python Basics and Data Concepts → Data types, mutability and object identity

Included ID 1531 · 2025 · 2 mark(s)

What is the purpose of None data type in Python?

Python Basics and Data Concepts → Data types, mutability and object identity

Included ID 1095 · 2025 · 3 mark(s)

Write a Python program that takes an integer input from the user and checks whether the number is prime or not.

Python Basics and Data Concepts → Data types, mutability and object identity

Included ID 1096 · 2025 · 3 mark(s)

Write a Python program that takes an integer n as input from the user and prints the first n terms of the Fibonacci series.
E.g. If the user enters 5, the program should print: 0 1 1 2 3
If the user enters 8, the program should print: 0 1 1 2 3 5 8 13

Python Basics and Data Concepts → Data types, mutability and object identity

Included ID 1215 · 2025 · 3 mark(s)

What are data types? What are Python's built-in core data types?

Python Basics and Data Concepts → Data types, mutability and object identity

Included ID 1324 · 2025 · 4 mark(s)

Write a program to check whether an integer input by the user is a 5-digit number and whether it is prime or composite.

Python Basics and Data Concepts → Data types, mutability and object identity

Included ID 1325 · 2025 · 4 mark(s)

Write a program which accepts a positive integer value and check if it is an Armstrong number or not.

Python Basics and Data Concepts → Data types, mutability and object identity

Included ID 1366 · 2025 · 4 mark(s)

Write a program to accept an integer and check if it is a perfect number or not.
Note:-A perfect number is a positive integer that is equal to the sum of its proper divisors (excluding the number itself).

Python Basics and Data Concepts → Data types, mutability and object identity

Included ID 1367 · 2025 · 4 mark(s)

Write a program to find the GCD and LCM of two positive integers

Python Basics and Data Concepts → Data types, mutability and object identity

Included ID 1106 · 2025 · 5 mark(s)

(i) Write a program in python that accepts two numbers and swap them without using a third variable.
(ii) Write a program in python that accepts a and b two integers and compute the greatest common divisor.

Python Basics and Data Concepts → Data types, mutability and object identity

Included ID 1221 · 2025 · 5 mark(s)

a=int(input("enter an integer"))
b=int(input("enter an integer"))
if a<=0:
    b=b+1
else:
    a=a+1
if a>0 and b>0:
    print("W")
elif a>0:
    print("X")
if b>0:
    print("Y")
else:
    print("Z")
A. What letters will be printed if the user enters 0 for a and 0 for b?
a. Only W
b) . Only X
c) . Only Y
d) W and X e) W,X and Y
B. What letters will be printed if the user enters 1 for a and 1 for b?
a. W and X
b) . W and Y
c) . X and Y
d) . X and Z e). W,X and Y
C. What letters will be printed if the user enters 1 for a and -1 for b?
a. W and X
b) . X and Y
c) . Y and Z
d) . X and Z e). W and Z
D. What letters will be printed if the user enters 1 for a and 0 for b?
a. W and X
b) . X and Y
c) . Y and Z
d) . X andZ e). W and Z
E. What letters will be printed if the user enters -1 for a and -1 for b?
a. Only W
b) Only X
c) Only Y
d) Only Z e) No letters are printed

Python Basics and Data Concepts → Data types, mutability and object identity

Student Notes (Print)

===========================================
SYSTEM ROLE
===========================================
You are an expert CBSE Class XI Computer Science (Code 083) teacher and examiner with 20 years of experience.
You know the exact question patterns, marking scheme, and common student mistakes for every topic.
Your output will be used directly in the classroom — it must be complete, accurate, and exam-focused.

===========================================
SUBJECT CONTEXT — Class XI CS (Code 083):
===========================================
- Theory paper: 70 marks, 3 hours. Practical: 30 marks.
- Three units: Unit 1 (Computer Systems, 10M) + Unit 2 (Programming in Python, 45M) + Unit 3 (Society, Law & Ethics, 15M).
- Question types: MCQ (1M), SA-I (2M), SA-II (3M), LA (4-5M).
- Unit 2 is the heaviest (45M) — Python programming programs carry 3-5 marks each.
- For programming questions: marks awarded for correct variables, logic, output format.
- Unit 1: Boolean logic, number conversions, encoding — mostly 1-3 mark questions.
- Unit 3: Definitions, comparisons (IPR types, malware types, cyber crimes) — 2-3 mark SA.
- Practical: Lab test (12M) + Report file/Viva (10M) + Project (8M).

===========================================
SCOPE — READ BEFORE GENERATING ANYTHING
===========================================
Today's lecture covers ONE topic only: "Data types, mutability and object identity Theory part 2"
Lecture number 42 of 115 | Duration: 35 minutes | Board: CBSE
Chapter: Unit 2: Computational Thinking and Programming – I (Python)

HARD RULE: Every piece of content you generate — notes, examples, questions, tips —
must be directly relevant to "Data types, mutability and object identity Theory part 2" only.
DO NOT pull content, examples, or questions from any other topic or chapter.

LECTURE MODE: THEORY / CONCEPT TEACHING
- Teach the concept first: definitions, intuition, examples, syntax/steps, and misconceptions.
- Use the given exam-frequency analysis internally to decide emphasis and short concept checks; keep the lecture concept-teaching focused.
- Keep content tightly scoped to today's concept list.

===========================================
SECTION 1: LECTURE INFORMATION
===========================================

Class: XI CS | Subject: Computer Science (Code 083) | Board: CBSE
Topic: Data types, mutability and object identity Theory part 2
Subtopics to cover today:
  • Data types, mutability and object identity

Student level: Class XI, CBSE Board, average to above-average students

===========================================
SECTION 2: TEACHER'S REFERENCE NOTES
===========================================

Data types, mutability and object identity Theory part 2

Concept ID: XI_U2_DATA_TYPES_MUTABILITY_IDENTITY.
Primary Sub-subtopic: Data types, mutability and object identity.
Question-bank grouping: Python Basics and Data Concepts.

Use this lecture for theory, examples, misconceptions, and short concept checks mapped to this concept ID.

Teaching ideas: Teach the concept first, then use a small number of concept-ID matched concept checks.

===========================================
SECTION 3: PYQ FREQUENCY DATA (Year-wise)
===========================================

Teaching priority: Not available
High-yield concepts: 

Year | Marks | Type | Concept
------------------------------------------------------------
2025 | 2M | Diagram/Logic Circuit | Data types, mutability and object identity
2025 | 2M | Short Answer | Data types, mutability and object identity
2025 | 2M | Short Answer | Data types, mutability and object identity
2025 | 3M | Programming | Data types, mutability and object identity
2025 | 3M | Programming | Data types, mutability and object identity
2025 | 3M | Short Answer | Data types, mutability and object identity
2025 | 4M | Programming | Data types, mutability and object identity
2025 | 4M | Programming | Data types, mutability and object identity
2025 | 4M | Programming | Data types, mutability and object identity
2025 | 4M | Programming | Data types, mutability and object identity
2025 | 5M | Programming | Data types, mutability and object identity
2025 | 5M | MCQ | Data types, mutability and object identity


===========================================
SECTION 4: ACTUAL PREVIOUS YEAR QUESTIONS
(Scope: "Data types, mutability and object identity Theory part 2" only — 12 questions from board papers)
===========================================

THEORY LECTURE RULE: use these PYQs only as private/internal analysis data.
- Do not print, quote, reproduce, paraphrase, or label actual PYQs in the visible final HTML.
- Do not show board year, section, marks, or real PYQ metadata in student-facing theory notes.
- Use the analysis only for concept priority, examiner traps, common mistakes, marking points, and examples.
- Self-generate concept checks from the current topic only.
- Do not call generated questions PYQ, previous-year, board-style, or PYQ-pattern.


Q1. [Diagram/Logic Circuit] [2M] [Medium] (2025)
Draw a flowchart for a program that accepts an integer input from the user and checks whether the number is even or odd. Display the appropriate message based on the result.

Q2. [Short Answer] [2M] [Medium] (2025)
(b) What is None in Python?

Q3. [Short Answer] [2M] [Medium] (2025)
What is the purpose of None data type in Python?

Q4. [Programming] [3M] [Medium] (2025)
Write a Python program that takes an integer input from the user and checks whether the number is prime or not.

Q5. [Programming] [3M] [Medium] (2025)
Write a Python program that takes an integer n as input from the user and prints the first n terms of the Fibonacci series.
E.g. If the user enters 5, the program should print: 0 1 1 2 3
If the user enters 8, the program should print: 0 1 1 2 3 5 8 13

Q6. [Short Answer] [3M] [Medium] (2025)
What are data types? What are Python's built-in core data types?

Q7. [Programming] [4M] [Hard] (2025)
Write a program to check whether an integer input by the user is a 5-digit number and whether it is prime or composite.

Q8. [Programming] [4M] [Hard] (2025)
Write a program which accepts a positive integer value and check if it is an Armstrong number or not.

Q9. [Programming] [4M] [Hard] (2025)
Write a program to accept an integer and check if it is a perfect number or not.
Note:-A perfect number is a positive integer that is equal to the sum of its proper divisors (excluding the number itself).

Q10. [Programming] [4M] [Hard] (2025)
Write a program to find the GCD and LCM of two positive integers

Q11. [Programming] [5M] [Hard] (2025)
(i) Write a program in python that accepts two numbers and swap them without using a third variable.
(ii) Write a program in python that accepts a and b two integers and compute the greatest common divisor.

Q12. [MCQ] [5M] [Hard] (2025)
a=int(input("enter an integer"))
b=int(input("enter an integer"))
if a<=0:
    b=b+1
else:
    a=a+1
if a>0 and b>0:
    print("W")
elif a>0:
    print("X")
if b>0:
    print("Y")
else:
    print("Z")
A. What letters will be printed if the user enters 0 for a and 0 for b?
a. Only W
b) . Only X
c) . Only Y
d) W and X e) W,X and Y
B. What letters will be printed if the user enters 1 for a and 1 for b?
a. W and X
b) . W and Y
c) . X and Y
d) . X and Z e). W,X and Y
C. What letters will be printed if the user enters 1 for a and -1 for b?
a. W and X
b) . X and Y
c) . Y and Z
d) . X and Z e). W and Z
D. What letters will be printed if the user enters 1 for a and 0 for b?
a. W and X
b) . X and Y
c) . Y and Z
d) . X andZ e). W and Z
E. What letters will be printed if the user enters -1 for a and -1 for b?
a. Only W
b) Only X
c) Only Y
d) Only Z e) No letters are printed

===========================================
===========================================
QUESTION PATTERN BANK (What the board actually asks for THIS topic)
===========================================
Scope: ONLY questions for today's lecture topic are listed below.
DO NOT import questions from other topics or chapters.
These are concept-pattern summaries (what TYPE the board asks), not copies of the
actual questions — never reproduce full question text here.

### Concept: Data types, mutability and object identity
  Pattern: Diagram/Logic Circuit=1, MCQ=1, Programming=7, Short Answer=3 | Marks: 2M=3, 3M=3, 4M=4, 5M=2 | Total: 12 questions
  [Diagram/Logic Circuit] [2M] [Medium]
    → Core concept of Data types, mutability and object identity
  [Short Answer] [2M] [Medium] × 2
    → Core concept of Data types, mutability and object identity
  [Programming] [3M] [Medium] × 2
    → Core concept of Data types, mutability and object identity
  [Short Answer] [3M] [Medium]
    → Core concept of Data types, mutability and object identity
  [Programming] [4M] [Hard] × 4
    → Core concept of Data types, mutability and object identity
  [Programming] [5M] [Hard]
    → Core concept of Data types, mutability and object identity
  [MCQ] [5M] [Hard]
    → Core concept of Data types, mutability and object identity


===========================================
===========================================
IMPORTANCE ANALYSIS (allocate teaching time by this ranking)
===========================================
| Rank | Concept | Score | Times Tested | Total Marks | Recent Years | Priority |
|------|---------|-------|-------------|-------------|--------------|----------|
| 1 | Data types, mutability and object identity | 99 | 12 | 41M | 2025 | CRITICAL |

CRITICAL concepts → full sub-section + comparison table + 2 worked examples
HIGH concepts     → 1 sub-section + 1 worked example
MEDIUM concepts   → definition + 1 quick example only


===========================================
YOUR TASK — Generate a complete classroom-ready teaching package
===========================================

Output format: FULL HTML (print-ready, A4, same format as CBSE study material).
Use the CSS classes below. NO plain Markdown — use HTML elements only.

HTML STRUCTURE TO GENERATE:

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<title>Data types, mutability and object identity Theory part 2 — Lecture 42</title>
<style>
/* ── PRINT SETUP ── */
@page { size: A4; margin: 12mm 14mm 12mm 14mm; }
* { box-sizing: border-box; }

/* ── BASE ── */
body { font-family: 'Segoe UI', Arial, sans-serif; font-size: 9.5pt; color: #1a1a2e; line-height: 1.4; background: #fff; margin: 0; padding: 0; }

/* ── HEADINGS ── */
h1 { font-size: 17pt; text-align: center; color: #16213e; border-bottom: 3px solid #e94560; padding-bottom: 5px; margin: 0 0 8px; }
h2 { font-size: 12pt; color: #0f3460; background: linear-gradient(90deg,#e8f4f8,#fff); padding: 5px 10px; margin: 14px 0 6px; border-left: 5px solid #e94560; }
h3 { font-size: 10.5pt; color: #16213e; border-bottom: 1.5px dashed #ccc; padding-bottom: 3px; margin: 10px 0 4px; }

/* ── CONTENT BOXES ── */
.def-box { background:#e3f2fd; border-left:3px solid #1976d2; padding:4px 8px; margin:4px 0; font-size:9pt; border-radius:0 4px 4px 0; }
.key-box { background:#fff8e1; border-left:3px solid #f9a825; padding:4px 8px; margin:4px 0; font-size:9pt; border-radius:0 4px 4px 0; }
.key-box ul { margin:3px 0 0 12px; padding:0; }
.key-box li { margin:2px 0; }
.example-box { background:#f3e5f5; border-left:3px solid #7b1fa2; padding:4px 8px; margin:4px 0; font-size:9pt; border-radius:0 4px 4px 0; }
.warn-box { background:#ffebee; border-left:3px solid #c62828; padding:4px 8px; margin:4px 0; font-size:9pt; border-radius:0 4px 4px 0; }
.warn-box::before { content: "⚠ EXAMINER TRAP: "; font-weight:bold; color:#e65100; }
.tip-box { background:#e8f5e9; border-left:3px solid #2e7d32; padding:4px 8px; margin:4px 0; font-size:9pt; border-radius:0 4px 4px 0; }
.recall-box { background:#e8f5e9; border-left:3px solid #2e7d32; padding:4px 8px; margin:4px 0; font-size:9pt; font-weight:bold; border-radius:0 4px 4px 0; }

.mcq-box { background:#f8f9fa; border:1px solid #dee2e6; padding:6px 10px; margin:5px 0; border-radius:4px; font-size:9pt; }
.options { list-style:none; margin:4px 0 0 0; padding:0; }
.options li { padding:2px 0; }
.options li.wrong { color:#c62828; }
.options li.correct { color:#2e7d32; font-weight:bold; }
.options .why { font-size:8pt; color:#555; margin-left:8px; font-style:italic; }
.self-test-box { background:#e8eaf6; border:1px dashed #5c6bc0; padding:6px 10px; margin:6px 0; border-radius:4px; font-size:9pt; }
details summary {
  cursor:pointer; display:inline-block; margin-top:6px; padding:2px 10px;
  background:#e8eaf6; color:#3949ab; border:1px solid #9fa8da;
  border-radius:4px; font-size:8.5pt; font-weight:600; user-select:none;
  list-style:none;
}
details summary::-webkit-details-marker { display:none; }
details[open] > summary { background:#c5cae9; }
details > *:not(summary) { margin-top:6px; }

/* ── CODE ── */
pre {
  background:#f8f9fa;
  color:#212529;
  border:1px solid #dee2e6;
  border-radius:4px;
  margin:4px 0;
  padding:8px 10px;
  font-size:8.5pt;
  line-height:1.5;
  white-space:pre-wrap;
  word-break:break-word;
}
pre code {
  white-space:pre;
  word-break:normal;
  display:block;
  overflow-x:auto;
  font-size:inherit;
}
code {
  font-family:'Courier New', monospace;
  font-size:0.95em;
}
.kw { color:#0000ff; } .bi { color:#267f99; } .st { color:#a31515; }
.cm { color:#008000; } .nm { color:#098658; } .fn { color:#795e26; }
.va { color:#001080; }

/* ── TABLES ── */
table { border-collapse:collapse; width:100%; margin:5px 0; font-size:8.5pt; }
th, td { border:1px solid #bbb; padding:3px 6px; text-align:left; }
th { background:#eeeeee; font-weight:bold; color:#333; }
tr:nth-child(even) { background:#fafafa; }
.highlight-row { background:#fff9c4 !important; font-weight:bold; }

/* ── CARDS ── */
.card-grid { display:grid; grid-template-columns:repeat(auto-fit,minmax(200px,1fr)); gap:6px; margin:8px 0; }
.card { background:#fff; border:1px solid #ccc; border-radius:4px; padding:6px 8px; font-size:8.5pt; }
.card .card-title { font-weight:bold; font-size:9pt; color:#0f3460; margin-bottom:3px; border-bottom:1px solid #eee; padding-bottom:2px; }

/* ── PRIORITY TAGS ── */
.priority-tag { font-size:7.5pt; padding:1px 6px; border-radius:10px; font-weight:bold; white-space:nowrap; }
.critical { background:#fce4ec; color:#ad1457; }
.high { background:#fff3e0; color:#e65100; }
.medium { background:#fff8e1; color:#f57f17; }
.marks-badge { display:inline-block; background:#e94560; color:#fff; font-size:7.5pt; padding:1px 5px; border-radius:10px; font-weight:bold; margin-left:5px; }

/* ── TOC STICKY SIDEBAR (screen only) ── */
@media screen {
  body { display:grid; grid-template-columns:165px 1fr; gap:0; }
  .toc-sidebar { position:sticky; top:0; height:100vh; overflow-y:auto; background:#f8f9fa; padding:10px 6px; font-size:8pt; color:#333; border-right:1px solid #ddd; }
  .toc-sidebar h4 { font-size:8.5pt; color:#16213e; margin:0 0 8px; padding-bottom:4px; border-bottom:1px solid #ddd; }
  .toc-sidebar a { display:block; color:#0f3460; text-decoration:none; padding:2px 4px; border-radius:3px; margin-bottom:1px; }
  .toc-sidebar a:hover { background:#e8f4f8; }
  .toc-sidebar .toc-h3 { padding-left:10px; font-size:7.5pt; color:#555; }
  .main-content { padding:10px 14px; min-width:0; }
}
@media screen and (max-width:640px) {
  body { grid-template-columns:1fr; }
  .toc-sidebar { display:none; }
  .main-content { grid-column:1 / -1; padding:8px; }
}
@media print {
  .toc-sidebar { display:none; }
  .main-content { grid-column:1 / -1; padding:0; }
  body { display:block; }
  .print-bar { display:none; }
  .collapse-btn { display:none !important; }
  .section-body { display:block !important; }
  details { display:block !important; }
  details > *:not(summary) { display:block !important; visibility:visible !important; }
  details > summary { display:none !important; }
}

/* ── PRINT BUTTONS ── */
.print-bar { position:fixed; top:8px; right:8px; display:flex; gap:6px; z-index:999; }
.print-btn { padding:5px 14px; color:#fff; border:none; border-radius:4px; cursor:pointer; font-size:9pt; box-shadow:0 2px 6px rgba(0,0,0,0.3); }
.print-btn.color-btn { background:#e94560; }
.print-btn.bw-btn { background:#333; }
.print-btn.back-btn { background:#1976d2; display:none; }
.print-btn.read-btn { background:#2e7d32; }

/* ── READ MODE ── */
@media screen {
  body.read-mode .print-bar { display:none !important; }
  body.read-mode .toc-sidebar { display:none !important; }
  body.read-mode .main-content {
    grid-column:1 / -1; max-width:860px; margin:0 auto;
    padding:24px 32px; font-size:11pt; line-height:1.75;
  }
}
#btnExitRead {
  display:none; position:fixed; bottom:16px; right:16px;
  background:rgba(0,0,0,0.55); color:#fff; border:none; border-radius:20px;
  padding:6px 14px; font-size:9pt; cursor:pointer; z-index:9999;
}
body.read-mode #btnExitRead { display:block; }
@media print { #btnExitRead { display:none !important; } }

/* ── B&W MODE OVERRIDES ── */
body.bw-mode { background:#fff !important; color:#000 !important; }
body.bw-mode .def-box, body.bw-mode .key-box, body.bw-mode .example-box,
body.bw-mode .warn-box, body.bw-mode .tip-box, body.bw-mode .recall-box,
body.bw-mode .pyq-box, body.bw-mode .mcq-box, body.bw-mode .self-test-box {
  background:#fff !important; border:1px solid #ccc !important; border-left:none !important;
}
body.bw-mode h1 { color:#000 !important; border-bottom:2px solid #000 !important; }
body.bw-mode h2 { background:#fff !important; border-left:2px solid #000 !important; color:#000 !important; }
body.bw-mode h3 { color:#000 !important; border-bottom:1px solid #000 !important; }
body.bw-mode pre { background:#fff !important; color:#000 !important; border:1px solid #ccc !important; }
body.bw-mode .kw, body.bw-mode .bi, body.bw-mode .st, body.bw-mode .cm,
body.bw-mode .nm, body.bw-mode .fn, body.bw-mode .va { color:#000 !important; }
body.bw-mode table th { background:#eee !important; color:#000 !important; }
</style>
</head>
<body>

<div class="print-bar">
  <button class="print-btn read-btn" id="btnReadMode" onclick="document.body.classList.toggle('read-mode')">📖 Read Mode</button>
  <button class="print-btn color-btn" onclick="window.print()">🖨 Print (Colour)</button>
  <button class="print-btn bw-btn" onclick="document.body.classList.add('bw-mode');window.print();setTimeout(()=>document.body.classList.remove('bw-mode'),1000)">🖨 Print (B&W)</button>
  <button class="print-btn back-btn" onclick="history.back()">← Back</button>
</div>
<button id="btnExitRead" onclick="document.body.classList.remove('read-mode')">✕ Exit Read Mode</button>

<script>
// Auto-build TOC from h2/h3 headings
(function(){
  function setup(){
    var sidebar=document.querySelector('.toc-sidebar');
    if(!sidebar)return;
    var headings=document.querySelectorAll('.main-content h2, .main-content h3');
    headings.forEach(function(h,i){
      if(!h.id){h.id='toc-'+i;}
      var a=document.createElement('a');
      a.href='#'+h.id;
      a.textContent=h.textContent;
      if(h.tagName==='H3'){a.className='toc-h3';}
      sidebar.appendChild(a);
    });
  }
  if(document.readyState==='loading'){document.addEventListener('DOMContentLoaded',setup);}else{setup();}
})();

(function(){
  function openDetails(){
    document.querySelectorAll('details').forEach(function(d){
      if(!d.hasAttribute('open')){d.setAttribute('data-was-closed','');d.setAttribute('open','');}
    });
    document.querySelectorAll('.section-body').forEach(function(w){
      if(w.style.display==='none'){w.setAttribute('data-was-hidden','');w.style.display='';}
    });
  }
  function restoreDetails(){
    document.querySelectorAll('[data-was-closed]').forEach(function(d){d.removeAttribute('open');d.removeAttribute('data-was-closed');});
    document.querySelectorAll('[data-was-hidden]').forEach(function(w){w.style.display='none';w.removeAttribute('data-was-hidden');});
  }
  window.addEventListener('beforeprint',openDetails);
  window.addEventListener('afterprint',restoreDetails);
})();
</script>

<!-- TOC SIDEBAR -->
<nav class="toc-sidebar" aria-label="Table of Contents">
  <h4>&#128214; Contents</h4>
</nav>

<!-- MAIN CONTENT -->
<div class="main-content">

Generate these sections in order (all inside the main-content div):

<h1 id="top">Data types, mutability and object identity Theory part 2 — Lecture 42</h1>
<p style="text-align:center;color:#555;font-size:8.5pt;">CBSE | XI CS | Unit 2: Computational Thinking and Programming – I (Python) | 35 min</p>

<h2 id="s1">1. Learning Objectives</h2>
[3–5 objectives derived from the private exam analysis above without naming or reproducing PYQs — use &lt;ul&gt;&lt;li&gt;]

<h2 id="s2">2. 35-Minute Lecture Flow</h2>
[HTML table: Time | Activity | Teacher Action — include concept teaching, misconception correction, and a self-generated Quick Concept Check; no PYQ discussion]

<h2 id="s3">3. Concept Notes</h2>
[For EVERY in-scope concept identified from private exam analysis, without showing actual PYQs:
  - .def-box for definition (with "In exam language: ..." line)
  - .key-box with syntax/rules as &lt;ul&gt;&lt;li&gt;
  - .example-box for worked examples
  - &lt;pre&gt;&lt;code&gt; for code with .kw/.bi/.st/.cm/.nm token spans (Python topics)
  - .recall-box for Output / Expected result
  After each concept, add 1–2 self-generated concept checks; do not use .pyq-box, years, marks, or PYQ labels]

<h2 id="s4">4. Examiner Tricks &amp; Common Mistakes</h2>
[One .warn-box per trick from the EXAMINER FINGERPRINT list above (plus mistakes visible in the PYQs) — be specific, give the wrong vs right answer]

<h2 id="s5">5. Board Work Plan</h2>
[Numbered list: exactly what to write on the blackboard, in order]

<h2 id="s6">6. Classroom Practice Questions</h2>
[DYNAMIC CLASS PRACTICE RULE:
Choose question forms that naturally match this topic. Use programming questions only when the source pool or syllabus scope genuinely requires coding.
- Every question must stay inside "Data types, mutability and object identity Theory part 2".
- Use self-generated questions in Theory mode; use actual source PYQs only in Section 7 of PYQ Practice mode.
- Every answer must be hidden inside &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;...&lt;/details&gt;.
- Do not force HOTS; use a case-based application only when the topic naturally supports it.]

<h2 id="s7">7. Quick Concept Check</h2>
[Create 5–8 original, topic-scoped checks. Use a suitable mix of MCQ,
fill-in-the-blank, True/False, one-line answer, short answer, comparison, diagram/flow,
or case-based questions. Do not reproduce or paraphrase actual PYQs. Do not show real
year, section, marks, or PYQ metadata. Hide every answer inside
&lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;...&lt;/details&gt;.]

<h2 id="s8">8. Student Notes (Copy-ready)</h2>
[Concise notes — every in-scope concept identified privately from exam analysis, with no PYQ wording — in .key-box and .def-box]

<h2 id="s9">9. Homework</h2>
[DYNAMIC HOMEWORK RULE:
- Generate homework according to the current topic and supported syllabus question forms.
- Choose question forms that naturally match this topic. Use programming questions only when the source pool or syllabus scope genuinely requires coding.
- Do not force 5M, HOTS, or programming merely because Unit 2 carries more marks overall.
- Prefer 1M–3M questions unless this topic's syllabus mapping genuinely supports a higher mark task.
- Hide every answer inside &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;...&lt;/details&gt;.]

<h2 id="s10">10. Exam Tips</h2>
[5 specific tips as .tip-box — derived from PYQ patterns for THIS topic only]

<h2 id="s11">11. Last-Minute Revision Cards</h2>
&lt;div class="card-grid"&gt;
[One .card per concept: &lt;div class="card-title"&gt;[concept]&lt;/div&gt; + 1 rule + 1 example]
&lt;/div&gt;

</div><!-- end .main-content -->
</body>
</html>

HARD OUTPUT RULES:
- Output ONLY the HTML document starting with &lt;!DOCTYPE html&gt;
- Do NOT wrap in markdown code fences
- Do NOT add explanatory text outside the HTML
- Use ONLY content from "Data types, mutability and object identity Theory part 2" — zero content from other topics
- Theory mode: actual PYQs in Section 4 are private analysis only; do not reproduce them in visible HTML
- Always finish the document completely through &lt;/html&gt;. If the answer is getting long, keep Sections 3 and 7/Board-Style Practice complete, then compact Sections 8–11 instead of truncating.
- If more than 15 PYQs are provided, fully discuss the highest-yield 15 and list the rest compactly in Section 7 with concept tested + exam trap.
- ANSWER HIDING: every answer inside &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;
- INLINE CODE SIZE RULE:
    * Inline code such as read(), write(), writelines(), tell(), seek(), open(), readline(), readlines() must appear almost the same size as surrounding normal text.
    * Do NOT use fixed 8.5pt size for all &lt;code&gt; elements.
    * Use code { font-size:0.95em; } for inline code.
    * Use pre { font-size:8.5pt; } for block code.
    * Use pre code { font-size:inherit; } so code blocks remain compact.
    * Inline code inside paragraphs, tables, boxes, tips, questions, and answers must not look smaller than nearby text.
- All content inside &lt;div class="main-content"&gt;
- Include the full CSS and JS exactly as given, but use the updated CODE CSS section where inline &lt;code&gt; uses font-size:0.95em and block code uses pre { font-size:8.5pt; } with pre code { font-size:inherit; }.

================================================
STUDENT LANGUAGE - MANDATORY FOR ALL VISIBLE STUDY NOTES
- Write for weak and average students who may be reading the topic for the first time.
- Use very simple English, short sentences, and one idea per bullet. Keep the academic content correct, but make the wording easy.
- Start every concept with an "In simple words" explanation. Give the exact CBSE/exam definition only after the easy explanation.
- Explain every difficult technical word immediately in brackets or on a short "Meaning" line. Never assume the student already understands subject jargon.
- Split long or compressed sentences into two or three easy bullets. Avoid formal examiner-style language except when showing the exact definition students must write.
- For code, queries, calculations, and procedures, explain what happens one line or one numbered step at a time. Show the result/output clearly.
- Add one tiny familiar example immediately after each new rule. Do not introduce extra unrelated theory.
- Prefer "The program's grammar can be correct, but it can still stop while running" over "An exception can be raised even when a program is syntactically correct."
- Prefer "The finally block always runs. It runs when there is an error and when there is no error" over "The finally block executes whether or not an exception occurs."
- Do not remove correct subject terminology. Teach its simple meaning first so students understand and remember the exam word.
- Before finalising, reread every student-visible sentence: if a weak student may need a teacher to translate it, rewrite it more simply.
================================================

# ENHANCED PPT GENERATION PROMPT
## Topic: Data types, mutability and object identity Theory part 2 | CBSE XI CS Computer Science

================================================
SECTION A -- VISUAL IDENTITY (READ FIRST, APPLY TO EVERY SLIDE)
================================================

COLOUR PALETTE -- "Deep Code" Theme
  Role              Hex        Name             Where Used
  Primary (dark)    #0D1B2A    Midnight Navy    Title bg, conclusion bg
  Secondary         #1B4F72    Ocean Blue       Section header cards, accent shapes
  Accent            #00D4FF    Cyan Electric    Keywords, callout borders, badges
  Neutral light     #F0F4F8    Ice White        All content slide backgrounds
  Warning/Error     #E74C3C    Alert Red        Common mistakes slide, warnings
  Success/Tip       #27AE60    Emerald Green    Tips, correct syntax, exam tips
  Text primary      #1A1A2E    Near Black       Body text on light slides
  Text on dark      #FFFFFF    Pure White       All text on dark background slides
  Text muted (dark) #C9D4E0    Slate Mist       Sub-lines / captions on navy slides

ON-LIGHT VARIANTS (use for ANY text, keyword, icon, or thin border on Ice White):
  Cyan  -> Accent-Deep  #0077A3      Emerald -> #1E8449      Red -> #C0392B
CONTRAST RULE: bright Cyan #00D4FF / Emerald #27AE60 / Red #E74C3C are for DARK
backgrounds or thick (>=4 pt) shape fills ONLY -- never for thin text, borders, or
badges on a light slide (bright cyan on Ice White is ~1.6:1 contrast = invisible
from the back row). On light slides always use the deep variants above.
ACCESSIBILITY RULE: never use colour as the only meaning. Pair warnings, tips,
correct answers, and definitions with a clear text label or simple symbol.

COLOUR DISCIPLINE -- 60 / 30 / 10 (a colour balance, not a rigid space quota)
  * Roughly 60% is the neutral Ice White base/background.
  * Roughly 30% is neutral structure -- cards, panels, diagrams, and readable text.
  * 10% -- and NO MORE -- is the accent (Cyan Electric or one status colour). One
    accent MOMENT per slide: the focal chip, the keyword, the one arrow that
    matters. A slide where every box is coloured has NO accent -- it is noise.
  * Keep useful breathing space around the focal content (aim for about 30-40%
    when practical), but NEVER squeeze content into a small area merely to meet a
    percentage. Code, question, table, and diagram slides may use more of the canvas.
  * Build depth with TINTS of one hue, never many saturated hues. A card fill is a
    6-8% tint of its header colour (pale-blue body under an Ocean Blue header),
    never a strong fill behind text. Status tints: blue 6% = definition,
    green 6% = correct/tip, red 6% = wrong/trap. Borders are 1 pt in the deep
    variant -- not thick coloured frames.
  * Navy dominates ONLY the Title and Key Takeaways slides. Never split a content
    slide 50/50 navy-vs-white -- it destroys hierarchy.

GRID & COMPOSITION (the missing rule that makes slides look intentional)
  * Lay every content slide on a 12-column grid inside the safe area with a
    consistent ~0.2 inch gutter. Snap every card, text block, icon and diagram
    edge to a column line -- never free-float objects at arbitrary x positions.
  * ONE alignment spine per slide: a single left text column (Left Visual+Text),
    two balanced 6-column halves (Two Column), or one centred focal object
    (Callout / Exam Spotlight). Do not mix three alignments on one slide.
  * Align tops and left edges across objects. Ragged, slightly-off edges are the
    #1 reason a slide reads as amateur even when nothing technically overlaps.

VISUAL HIERARCHY -- ONE FOCAL POINT PER SLIDE
  * Every slide answers "what is the ONE thing the eye lands on first?" Make that
    element the largest / boldest / the only accent-coloured object; everything
    else is visibly secondary (smaller, neutral, lighter).
  * Hierarchy comes from SCALE CONTRAST and SPACE, not from boxing everything. A
    big number, one code line, or a single diagram surrounded by white beats
    three equal-weight bordered boxes every time.
  * Reserve bold + accent colour for the focal point ONLY. If three things are
    bold and coloured, nothing is emphasised.

INFORMATION-CARRYING VISUALS (the default -- not decorative chrome)
  * The visual must MEAN something: it carries the concept, it is not an ornament
    around text. Prefer, in order: a labelled code-breakdown (one code line on a
    dark card with arrows naming each part's role), a before/after, a flow
    (input -> process -> output), a comparison table, a decision tree.
  * A rounded box with a clip-art icon beside a bullet is chrome -- it explains
    nothing and should be cut. One strong visual that teaches the idea beats four
    small decorative ones.
  * Icons: line-style, ONE consistent family, used to label SECTIONS only -- not
    one circle per bullet. An icon on every line is clutter, not design.

TYPOGRAPHY -- CLASSROOM-OPTIMISED (NON-NEGOTIABLE)
  Element             Font              Size   Weight    Notes
  Slide title         Montserrat        44 pt  Bold      Visible from back row (Arial Bold if Montserrat unavailable)
  Focal number/word   Montserrat        60+ pt Bold      The one hero element may go large for scale contrast
  Section header      Arial             32 pt  Bold      Sub-headings inside slides
  Body bullets        Calibri           28 pt  Regular   MAX 3 bullets -- min 28 pt
  Code text           Courier New       24 pt  Regular   On dark card only
  Captions/labels     Calibri           20 pt  Regular   Metadata/footer only; never instructional content

  NEVER go below 24 pt for instructional content.
  Non-instructional metadata only (footer, source, year/marks badge) may be 18-20 pt.
  NEVER use Aptos, Thin fonts, or Calibri Light.
  Line spacing 1.15+. Title case for titles; sentence case for body.

VISUAL MOTIF -- "Bracket Accent" (restrained signature, not the main visual)
  * Use the small { } mark on the Title, section-transition, and Key Takeaways
    slides only. Do not stamp it on every content slide. It is a signature, never
    a required decoration or the slide's main visual.
  * Definitions: a single rounded callout with a 4 pt Cyan-Electric LEFT border
    only (no full frame). Code: dark #0D1B2A card, #00D4FF keywords, white rest.

MOTION & TRANSITIONS
  * Build a static classroom deck by default. Use no decorative animation,
    bouncing objects, sound, auto-advance, or random transitions.
  * If a reveal is pedagogically necessary, use one simple Appear/Fade sequence
    on that slide only. The slide must remain understandable when printed.

DESIGN NEVER-DO LIST
  NO accent lines below titles
  NO colour bars or stripes spanning full slide width
  NO vertical sidebar stripes
  NO cream/beige backgrounds
  NO saturated colour fills behind body text (use 6-8% tints instead)
  NO icon-circle on every bullet, no clip-art decoration
  NO three competing focal points -- exactly one hero element per slide
  NO evenly-tiled grid of identical boxes whose only job is to fill the slide
  NO forced decoration. Instructional slides should use ONE information-carrying
     visual when it improves understanding; Agenda and question-only slides may
     rely on strong typography and spacing instead.
  NO centred body text -- left-align all bullets
  NO more than 3 bullets per slide
  TARGET 12 words per bullet; HARD MAX 14 words and one idea per bullet
  NO instructional font below 24 pt; metadata may be 18-20 pt

LAYOUT VARIETY -- ROTATE WHEN IT HELPS CLARITY
  Layout Name         When to Use
  Full-bleed Dark     Title slide, Key Takeaways slide
  Left Visual+Text    Theory slides -- one meaningful line icon/diagram left, bullets right
  Two Column          Comparisons (two closely related ideas from this lecture, etc.)
  Code Card           All code examples -- dark card on light background
  Callout Box         Definitions -- rounded rect, Cyan Electric border
  Exam Spotlight      Concept Practice slides -- large question centred on card
  3-Icon Grid         Key Takeaways -- 3 icons in equal columns
  Warning Banner      Common Mistakes -- red accent, alert icon

================================================
SECTION A1 -- LAYOUT SAFETY & OVERLAP PREVENTION
================================================

NON-NEGOTIABLE SAFE ZONE RULES:
  * Every slide must use a fixed 16:9 widescreen canvas.
  * Keep a minimum 0.35 inch margin from all slide edges.
  * No text box, badge, icon, card, or diagram may overlap another object.
  * Title area must be reserved separately from body area.
  * Body content must start only after the title area ends.

TITLE SAFE AREA:
  * Single-line title box: y=0.35-1.05 inch. Two-line title box: y=0.25-1.40 inch.
  * If a top-right badge is present, keep the title inside x=0.65-9.55 inch and
    reserve x>=10.0 inch for the badge. Otherwise the title may use the safe width.
  * No icon, card, or body text may enter the active title zone.
  * If a title is long, wrap into maximum 2 lines; never squeeze or overlap it.
  * Never allow title text to touch badges or cards.

BADGE PLACEMENT RULE:
  * Badges such as "Quick Recap", "Practice Question", "1M", "60 seconds" must be placed
    in a fixed safe badge zone.
  * Badge zone: top-right corner, x >= 10.0 inch, y between 0.35 and 0.85 inch.
  * Badge must never be placed near the centre title area.
  * Badge text must stay inside the badge shape with 0.08 inch internal padding.

BODY SAFE AREA:
  * Body content begins at y >= 1.45 inch after a one-line title and y >= 1.70
    inch after a two-line title.
  * Large cards/callouts begin at y >= 1.55 inch (one-line title) or y >= 1.80
    inch (two-line title).
  * Main content must finish by y=6.70 inch. Footer/metadata uses y=6.90-7.10 inch.
  * Do not place main content in the footer zone.

TEXT FITTING RULE:
  * Do NOT shrink font below the required size.
  * If content does not fit, split into a continuation slide.
  * Use "(contd...)" in the title for continuation slides.
  * Never use PowerPoint auto-fit that reduces font size.
  * Never compress line spacing below 1.05.

OBJECT COLLISION CHECK -- before finalising each slide, verify:
  [ ] Title does not overlap badge.
  [ ] Badge does not overlap title or body.
  [ ] Body text does not overlap cards or icons.
  [ ] Code card has enough internal padding.
  [ ] No object is outside slide boundary.
  [ ] All text is fully visible after rendering.

RENDER QUALITY CHECK:
  After creating the PPT, render every slide as an image and inspect all
  rendered slides visually. If any slide has overlapping, clipped, hidden, or
  tiny text: fix the layout, split the slide if needed, render again, and only
  then provide the final PPT.

STRICT FAILURE RULE:
  A slide with overlapping text, clipped title, hidden badge, or unreadable
  content is considered FAILED and must be rebuilt before delivery.

================================================
SECTION B -- CONTENT SPECIFICATION
================================================

Topic     : Data types, mutability and object identity Theory part 2
Lecture   : #42 | Target duration: 35 min | Board: CBSE
Chapter   : Unit 2: Computational Thinking and Programming – I (Python)
Class     : XI CS | Subject: Computer Science
Audience  : Class XI, CBSE Board, average to above-average students

STRICT RULE: Every slide must be about "Data types, mutability and object identity Theory part 2" ONLY.

GENERATED STUDY NOTES HTML INPUT (OPTIONAL BUT PREFERRED):
  If the user provides/pastes the generated HTML study notes file for this lecture,
  treat that HTML as the AUTHORITATIVE theory source for the deck.
  Summarise all concepts from the HTML into slide-friendly bullets, examples,
  diagrams, tables, and speaker notes. Do NOT copy long HTML paragraphs verbatim.
  Theory/content slides come from the HTML study notes.
  Concept Practice slides are self-generated using Section F's Concept Practice Rule.

DECK GOAL: This deck is the polished, exam-focused version of the study notes —
NOT a list of definitions. Teach what the examiner actually tests. Lead with the
CRITICAL & CONFUSING concepts flagged in Section F (EXAM FOCUS -- private analysis input,
never printed), give them the most slide time, disambiguate every look-alike pair, and
surface self-generated practice questions inspired by that analysis (never the real
previous-year questions themselves). Cover every concept the analysis names — drop none
to save slides.

SLIDE COUNT -- DETERMINE BY CONTENT, NOT A FIXED NUMBER:
  Do not compress or stretch the topic to hit a fixed slide count.
  For a single-concept theory lecture, typical deck size is 11-16 slides.
  For multi-concept lectures, typical deck size is 18-30 slides.
  The actual count depends on concept density, examples, traps, and practice needs.
  Never stretch a small topic only to reach 18 slides.
  Never cram a large topic into fewer slides by shrinking fonts or overcrowding.
    * CRITICAL/HIGH subtopics listed in Section D get dedicated slides.
    * MEDIUM subtopics may share a slide unless they have multiple distinct cases.
    * If a subtopic has MULTIPLE DISTINCT CASES (e.g. several topic-specific cases with different behaviour),
      give EACH case its own slide or clearly separated section — never
      compress distinct cases into one bullet list just to save slides.
    * CRITICAL-priority subtopics (Section F) --> 2 slides: theory + worked example.
    * HIGH-priority subtopics --> 1 dedicated slide.
    * MEDIUM-priority subtopics --> 1 bullet on a shared slide, UNLESS that
      subtopic has multiple distinct cases (above), then give it its own slide too.
    * CONTINUATION (encouraged — do NOT cram): when one concept needs more room
      than a single slide allows (more than 3 bullets, or theory + worked example
      + an exam trap), SPLIT it across consecutive slides. Title the overflow slide
      "<SAME TOPIC> (contd...)" and add a small "...continue ->" marker bottom-right
      of the first slide so the flow is obvious. Two clean slides always beat one
      crowded slide — never shrink the font or exceed 3 bullets just to make it fit.
  Fixed-position slides (always present, regardless of total count):
    Title, Agenda, Prior Knowledge Check        -- start of deck
    Common Mistakes                         -- immediately after content slides
    Concept Practice (4 self-generated questions, EASY to TOUGH) -- after Common Mistakes
    Key Takeaways, Exit Ticket              -- final two slides, in that order

EXAMPLE SINGLE-CONCEPT DECK SHAPE (illustrative only -- adapt slide count and
content-slide breakdown to THIS lecture's actual concept, not to this example):
    1. Title
    2. Agenda
    3. Prior Knowledge Check
    4. Concept overview
    5-8. Concept-specific flow/example slides (split the concept into its natural
         sub-steps or look-alike comparisons -- do not force exactly 4)
    9. Common Mistakes
    10-13. Four Concept Practice slides
    14. Key Takeaways
    15. Exit Ticket


EXPLAIN FOR UNDERSTANDING, NOT JUST RECALL (the most important rule here):
  A student must understand the concept by reading the slide ONCE, without
  the teacher's voice filling gaps. For every theory/definition slide:
    * Start with a one-line plain-English restatement ("In simple words: ...")
      -- not just the textbook/jargon definition.
    * Follow with ONE tiny concrete example showing the concept in action
      (a concrete example from this lecture topic, a real value, a real before/after) -- never leave
      a definition abstract with no example near it.
    * If two things are easily confused, show them side by side on a Two Column slide -- never describe
      look-alike concepts on separate, disconnected slides.

================================================
SECTION C -- SLIDE OUTPUT FORMAT (USE EXACTLY)
================================================

+=======================================================+
SLIDE [n]: [SLIDE TITLE IN CAPS]
Layout     : [Full-bleed Dark / Left Visual+Text / Two Column /
              Code Card / Callout Box / Exam Spotlight /
              3-Icon Grid / Warning Banner]
Background : [#0D1B2A or #F0F4F8]
Title font : Montserrat Bold -- 44 pt on body slides / 54 pt on the Title slide
Body font  : Calibri 28 pt Regular
-------------------------------------------------------
VISUAL ELEMENT: [icon/shape/code card/diagram on this slide]

[Bullet 1 -- target <=12 words; hard max 14]
[Bullet 2 -- target <=12 words; hard max 14]
[Bullet 3 -- target <=12 words; hard max 14]

Do not add a coloured circle to every bullet. Use status colour only when a
bullet genuinely represents a definition, correct/tip, or warning.

TOPIC EXAMPLE SLIDE:
  Use a labelled visual, comparison, flow, or short code card drawn only from
  the current lecture topic. Never insert a file-handling example by default.

DIAGRAM SLIDES: describe shapes, arrows, labels, layout
-------------------------------------------------------
SPEAKER NOTES: [2-3 sentences for teacher -- NOT on slide.
Real-life analogy / Did You Know fact / exam tip / story.
EXCEPTION -- on Concept Practice and Exit Ticket slides the notes instead carry the COMPLETE step-by-step solution / answer + explanation (code may span many lines).]
+=======================================================+

================================================
SECTION D -- MANDATORY SLIDE SPECIFICATIONS
================================================

TITLE SLIDE (slide 1)
  Layout     : Full-bleed Dark (#0D1B2A background)
  Topic name : "Data types, mutability and object identity Theory part 2" -- 54 pt Bold Cyan Electric (#00D4FF)
  Sub-line 1 : "XI CS Computer Science" -- 32 pt White
  Sub-line 2 : "CBSE Board | Lecture 42" -- 24 pt Slate Mist (#C9D4E0)
  Motif      : semi-transparent { } bracket centred background (15% opacity)

AGENDA (slide 2)
  Layout     : Left Visual+Text
  Show at most 6 readable agenda rows. Group closely related subtopics under one
  short row; if grouping would hide meaning, use an Agenda (contd...) slide.
  Use one small section icon per row only when it adds meaning; no icon circles.

PRIOR KNOWLEDGE CHECK (slide 3)
  Layout     : Callout Box centred
  Single question in large rounded rectangle
  Badge      : "Think -> Pair -> Share" top-right
  Speaker notes: real-life analogy (NOT on slide)

CONTENT SLIDES (as many as the SLIDE COUNT rules in Section B require)
  Subtopics to cover (allocate slide count by EXAM FOCUS priority in Section F):
  * Data types, mutability and object identity

  Layout rules:
  * Avoid repeating the same layout twice in a row unless the second slide is a continuation, paired worked example, or necessary code-tracing slide. Clarity is more important than artificial layout rotation.
  * Theory    --> Callout Box for definition + Left Visual+Text for bullets
  * Examples  --> Code Card (dark card, Courier New 24 pt, keywords Cyan Electric)
  * Comparisons / look-alike concepts --> Two Column layout
  * Apply the EXPLAIN FOR UNDERSTANDING rule (Section B) to every theory slide
  * CRITICAL priority subtopics --> 2 slides (theory + worked example)
  * HIGH priority subtopics     --> 1 dedicated slide
  * MEDIUM priority subtopics   --> 1 bullet on a shared slide, UNLESS it has
    multiple distinct cases (Section B), then give it its own slide too

COMMON MISTAKES & EXAMINER TRAPS (right after all content slides)
  Layout     : Warning Banner
  Accent     : left thick border #E74C3C (4 pt) on each bullet card
  Title      : "DON'T MAKE THESE MISTAKES" -- 44 pt Bold Deep Red #C0392B
  EXACTLY 3 bullets -- specific examiner traps with red alert icon

CONCEPT PRACTICE -- THIS IS A THEORY LECTURE: no PYQ wording anywhere on these slides
  (4 slides, 1 self-generated question each, EASY -> TOUGH)
  Layout     : Exam Spotlight (large card, question text centred)
  Show ONLY  : question text (32 pt) + pedagogical marks badge such as '1M', '2M', or '3M' (Ocean Blue) + "Practice Question" badge
  The marks badge is for classroom practice only, not copied from any previous question.
  NEVER show : a real year badge, the "Representative PYQ-pattern question" label, or the
               word "PYQ"/"previous year question" anywhere on the slide
  Content    : every question must be SELF-GENERATED and worded purely about the concept
               itself -- informed by the private exam-importance analysis in Section F, but
               never reproducing, paraphrasing, or labelling an actual board question
  ANSWER ONLY IN SPEAKER NOTES -- NEVER ON SLIDE
  Order      : Easy -> Medium -> Hard; within each difficulty, 1M -> 2M -> 3M -> higher
               (see CONCEPT PRACTICE RULE in Section F)
  Placement  : after Common Mistakes and before Key Takeaways
  Students solve in ~90 seconds, then teacher reveals from notes

KEY TAKEAWAYS (second-to-last slide)
  Layout     : 3-Icon Grid (dark #0D1B2A background -- matches title)
  3 equal columns: large icon + 1-line heading (28 pt Bold) + 1-line summary (24 pt)
  EXACTLY 3 takeaways

EXIT TICKET (last slide)
  Layout     : Callout Box centred
  EXACTLY 1 MCQ or fill-in-the-blank -- question 32 pt, options 28 pt
  Timer badge: "60 seconds" top-right (Cyan Electric)
  ANSWER + EXPLANATION ONLY IN SPEAKER NOTES

================================================
SECTION E -- ENGAGEMENT RULES (MIN 2 IN SPEAKER NOTES)
================================================

1. Prior Knowledge Check slide: real-life analogy -- NOT textbook language
2. One slide: "Did You Know?" fun fact in speaker notes
3. One code slide: "Guess the Output?" -- ask class before revealing
4. Semantic colour only when useful: deep red = warning, deep green = tip,
   deep blue = definition. Ordinary bullets remain Near Black; never colour every bullet.
5. Common Mistakes slide: one "Examiner Trap" with specific wrong answer students typically write

================================================
SECTION F -- EXAM FOCUS (WEIGHT SLIDES BY EXAM IMPORTANCE)
================================================

Board exam appearances: 12 times (2025-2025) | Total marks tested: 41M

DECK INTENT: build this as the POLISHED, EXAM-FOCUSED version of the study
notes — cover EVERY examiner-tested concept below (not just definitions),
and lead with the CRITICAL + CONFUSING concepts, giving them the most slide time.

TOP PRIORITY -- CRITICAL & CONFUSING CONCEPTS (open the content with these):
  ! Data types, mutability and object identity — asked as Diagram/Logic Circuit/MCQ/Programming/Short Answer; at 2,3,4,5M; 12x repeated --> own theory + worked-example slide; if it has a look-alike, use a Two-Column 'X vs Y' compare slide.

SUBTOPIC PRIORITY (allocate slide count by this ranking — see SLIDE COUNT rules in Section B):
  CRITICAL --> 2 slides: theory + worked example
    * Data types, mutability and object identity — 12x in exams, 41M total (years: 2025)

===========================================
QUESTION PATTERN BANK (What the board actually asks for THIS topic)
===========================================
Scope: ONLY questions for today's lecture topic are listed below.
DO NOT import questions from other topics or chapters.
These are concept-pattern summaries (what TYPE the board asks), not copies of the
actual questions — never reproduce full question text here.

### Concept: Data types, mutability and object identity
  Pattern: Diagram/Logic Circuit=1, MCQ=1, Programming=7, Short Answer=3 | Marks: 2M=3, 3M=3, 4M=4, 5M=2 | Total: 12 questions
  [Diagram/Logic Circuit] [2M] [Medium]
    → Core concept of Data types, mutability and object identity
  [Short Answer] [2M] [Medium] × 2
    → Core concept of Data types, mutability and object identity
  [Programming] [3M] [Medium] × 2
    → Core concept of Data types, mutability and object identity
  [Short Answer] [3M] [Medium]
    → Core concept of Data types, mutability and object identity
  [Programming] [4M] [Hard] × 4
    → Core concept of Data types, mutability and object identity
  [Programming] [5M] [Hard]
    → Core concept of Data types, mutability and object identity
  [MCQ] [5M] [Hard]
    → Core concept of Data types, mutability and object identity


===========================================
IMPORTANCE ANALYSIS (allocate teaching time by this ranking)
===========================================
| Rank | Concept | Score | Times Tested | Total Marks | Recent Years | Priority |
|------|---------|-------|-------------|-------------|--------------|----------|
| 1 | Data types, mutability and object identity | 99 | 12 | 41M | 2025 | CRITICAL |

EXAMINER FINGERPRINT -- TRAPS TO COVER INTERNALLY

Use this section only for internal slide planning. Do not print this
heading or these internal labels on slides.

For this lecture, the deck must strongly cover these traps:

No static trap list was supplied for this lecture -- self-generate 4-7 traps from:
  * actual question patterns
  * common wrong assumptions
  * output-tracing traps
  * syntax-vs-runtime traps
  * comparison traps
  * order/sequence traps
  * look-alike concept traps

* Common Mistakes slide must select the top 3 traps from this Examiner
  Fingerprint list.
* Concept Practice slides must together cover at least 4 traps from this list.
* Content slides must teach the traps before practice slides test them.

SELF-GENERATED PRACTICE-QUESTION SEEDS
PRIVATE ANALYSIS INPUT ONLY -- NEVER PRINT ON SLIDES

The seed text is only a concept/trap reference. The generated deck must
create new questions using different wording, different code/data where
possible, and no source-year references.
  THIS IS A THEORY DECK. The 4 question(s) below are PRIVATE INPUT —
  do NOT reproduce, paraphrase, or show any of this text verbatim on a slide, and
  NEVER show a real year/marks-from-PYQ badge or the word "PYQ" on any slide.
  For each seed, self-generate a NEW practice question that tests the SAME concept
  and trap, worded purely about the concept itself (not as board/PYQ practice).
  Order the self-generated questions Easy -> Tough, 1M -> 2M -> 3M -> higher.

  Seed 1. [INTERNAL ONLY -- never shown on a slide] [5M] [Hard/MCQ] Concept: Data types, mutability and object identity
  ```
  a=int(input("enter an integer"))
  b=int(input("enter an integer"))
  if a<=0:
      b=b+1
  else:
      a=a+1
  if a>0 and b>0:
      print("W")
  elif a>0:
      print("X")
  if b>0:
      print("Y")
  else:
      print("Z")
  A. What letters will be printed if the user enters 0 for a and 0 for b?
  a. Only W
  b) . Only X
  c) . Only Y
  d) W and X e) W,X and Y
  B. What letters will be printed if the user enters 1 for a and 1 for b?
  a. W and X
  b) . W and Y
  c) . X and Y
  d) . X and Z e). W,X and Y
  C. What letters will be printed if the user enters 1 for a and -1 for b?
  a. W and X
  b) . X and Y
  c) . Y and Z
  d) . X and Z e). W and Z
  D. What letters will be printed if the user enters 1 for a and 0 for b?
  ... (truncated - see full question in study notes)
  ```
  Seed 2. [INTERNAL ONLY -- never shown on a slide] [2M] [Medium/Diagram/Logic Circuit] Concept: Data types, mutability and object identity
  ```
  Draw a flowchart for a program that accepts an integer input from the user and checks whether the number is even or odd. Display the appropriate message based on the result.
  ```
  Seed 3. [INTERNAL ONLY -- never shown on a slide] [2M] [Medium/Short Answer] Concept: Data types, mutability and object identity
  ```
  (b) What is None in Python?
  ```
  Seed 4. [INTERNAL ONLY -- never shown on a slide] [2M] [Medium/Short Answer] Concept: Data types, mutability and object identity
  ```
  What is the purpose of None data type in Python?
  ```

SLIDE WEIGHTING RULE:
  CONFUSING/CRITICAL concepts --> FIRST content slides; own theory slide + own
                                  worked-example or 'X vs Y' compare slide
  HIGH subtopics     --> own slide
  MEDIUM subtopics   --> 1 bullet max on a shared slide
  Every concept named in the QUESTION PATTERN BANK above MUST appear on a slide —
  a concept the board has actually tested may NEVER be dropped to save slides.

CONCEPT PRACTICE RULE:
  Make EXACTLY 4 self-generated Concept Practice slides unless the
  user explicitly requests a shorter deck -- this is the one authoritative count
  for this section.
  Each practice slide must contain ONE original question only.
  Answer and full explanation must appear only in speaker notes.
  The questions must progress Easy -> Medium -> Hard/Tough.
  Together, the questions must cover the most important examiner traps from
  the EXAMINER FINGERPRINT section above.
  For any question needing a skill NOT covered in this lecture's content slides,
  add a 1-line "Quick recall:" reminder of that skill in the speaker notes BEFORE
  the solution -- never leave students to bridge that gap alone.

NO PREVIOUS-QUESTION LEAK RULE:
  This is a theory deck.
  Use the private exam-analysis input only to decide emphasis, traps, and
  practice coverage.
  Never reproduce, paraphrase, or display an actual previous board question on
  any slide.
  Never show a real year badge.
  Never show "marks-from-previous-question" metadata.
  Never use the labels "PYQ", "previous year question", "PYQ-pattern",
  "PYQ-style", or "Representative PYQ-pattern question" anywhere on a slide.
  Every practice slide must read as original classroom practice content.
  Full answer and explanation must appear only in speaker notes.

================================================
SECTION G -- QUALITY CHECKLIST (VERIFY BEFORE OUTPUT)
================================================

Visual Checks:
  [ ] Title font >= 44 pt on every slide
  [ ] Body font >= 28 pt on every slide
  [ ] Code font >= 24 pt inside dark card only
  [ ] No instructional font below 24 pt; metadata/footer only may be 18-20 pt
  [ ] No decorative visual was forced onto Agenda or question-only slides
  [ ] No unnecessary repeated layout; continuation, paired worked-example, and necessary code-tracing slides may repeat layout.
  [ ] Sandwich: dark Title -> light content -> dark Key Takeaways -> light Exit Ticket
  [ ] { } bracket motif appears only on Title/transition/Key Takeaways slides
  [ ] NO accent lines under titles
  [ ] NO full-width colour bars or stripes
  [ ] NO cream/beige backgrounds
  [ ] Bullets left-aligned (titles centred only)
  [ ] ONE clear focal point per slide (one hero element, one accent moment)
  [ ] Objects snapped to the grid -- tops/left edges aligned, nothing free-floating
  [ ] Accent colour <= 10% of slide area; cards use 6-8% tints, not saturated fills
  [ ] Every slide's visual carries meaning (no decorative icon-circles / clip-art)
  [ ] Content has useful breathing space without being squeezed into a fixed quota

Content Checks:
  [ ] CRITICAL/HIGH subtopics in Section D have dedicated slides
  [ ] MEDIUM subtopics are covered on shared slides unless they have multiple
      distinct cases
  [ ] Multi-case subtopics have EACH case
      covered, not compressed into one slide
  [ ] Every theory slide has a plain-English restatement AND a concrete example
  [ ] No slide has more than 3 bullets
  [ ] Bullets target <=12 words and never exceed 14 words or one idea
  [ ] Every substantial code example has a Code Card slide; tiny
      inline snippets may stay beside the explanation when readable
  [ ] Common Mistakes slide has EXACTLY 3 examiner traps (red accent)
  [ ] Concept Practice slides: self-generated question + marks badge only -- NO real year, NO "PYQ"
      wording, NO "Representative PYQ-pattern question" label anywhere -- answer ONLY in speaker notes
  [ ] Concept Practice slides ordered easiest-to-hardest
  [ ] Key Takeaways slide has EXACTLY 3 takeaways in 3-Icon Grid layout
  [ ] Exit Ticket has 1 question with answer ONLY in speaker notes
  [ ] All speaker notes include teacher dialogue (EXCEPT Concept Practice & Exit Ticket, whose notes carry the full solution/answer instead -- Section C)
  [ ] Minimum 2 engagement techniques across speaker notes

Layout Safety Checks:
  [ ] Every slide uses 16:9 widescreen canvas
  [ ] All objects keep at least 0.35 inch margin from slide edges
  [ ] Title uses the correct one-line or two-line safe area and wraps to max 2 lines
  [ ] Body/card start position moves down when the title wraps to two lines
  [ ] Badges stay in the top-right badge zone and never touch title/body
  [ ] No text, badge, icon, card, code block, or diagram overlaps another object
  [ ] No PowerPoint auto-fit has reduced required font sizes
  [ ] Continuation slides are used whenever content would otherwise crowd
  [ ] Rendered slide images have no clipped, hidden, overlapping, or tiny text

================================================
STUDENT LANGUAGE - MANDATORY FOR EVERY SLIDE AND SPEAKER NOTE
- Write for weak and average students who may be learning the topic for the first time.
- Use very simple English, short sentences, and one idea at a time. Keep the academic depth correct, but make the wording easy.
- First explain an idea in everyday words. Then show the exact CBSE/exam term in brackets or on a separate "Exam term" line.
- Explain every difficult technical word the first time it appears. Do not use words such as syntactically, exception, handler, iteration, mutable, protocol, constraint, or aggregate without a simple meaning.
- Slide bullets must be direct and easy to read. Do not compress several instructions or rules into one bullet merely to meet the slide limit; use a continuation slide instead.
- For code, queries, calculations, and procedures, explain what happens one line or one step at a time. Show the result/output clearly.
- Speaker notes must sound like a teacher speaking to a struggling student: simple explanation, tiny example, then exam wording.
- Prefer "The finally block always runs. It runs with an error and without an error" over "The finally block executes whether or not an exception occurs."
- Prefer "Read the code one line at a time. Check end= because it keeps the next output on the same line" over compressed instructions such as "Trace output separators carefully."
- Do not remove correct subject terminology. Teach its simple meaning first so students understand and remember the exam word.
- Before finalising, reread every visible sentence: if a weak student may need a teacher to translate it, rewrite it more simply.
================================================

27304 chars Customise board, duration & level