How mohitpawaskar1/python works
Project type and purpose
• This is an educational Python code repository organized as a “learn-by-doing” curriculum.
• It contains:
• Core topic scripts (Variables.py, Functions.py, etc.)
• Practice exercises (Practice Question/*)
• Mini-projects (Rock Paper Scissors, Flappy Bird)
• A small application project (Jarvis Virtual Assistant).
File structure
• Top-level directories:
• “Project” – contains the Jarvis assistant and a top-level main.py orchestrator.
• “Mini Projects” – self-contained demos.
• “Practice Question” – exercise scripts plus data files.
• Core topic files live at the repo root (Strings.py, Loops.py, etc.).
• README.md describes the learning path and lists topics.
Main components
A. Core Modules Layer
• Each topic script (Variables, Strings, Lists, …)
B. Practice Exercises Layer
• Practice Question folder with sub-folders per topic
C. Mini-Projects Layer
• Each mini-project is an independent unit that may import core modules
• Under “Mini-Projects”
D. Application Project
• The “Jarvis Virtual Assistant” with main.py, moviesLibrary.py, musicLibrary.py
• It depending on Core Modules where it uses Python standard libraries
E. External Environment
• Python Interpreter & Virtual Env / PIP
• External APIs (if Jarvis calls any, but here assume none)
Relationships and interactions
• Core Modules → Practice Exercises (students apply each topic)
• Core Modules → Mini-Projects and Jarvis (projects import and reuse modules)
• Python Runtime / Virtual Env → All scripts (execution environment)
• README → Guides user through the flow (not in runtime, but in documentation)
Architectural patterns and principles
• Layered / curriculum progression: Theory → Exercises → Applications
• Separation of concerns: each script/module addresses one topic
• Reusability: modules can be imported by mini-projects and Jarvis assistant
Relevant technologies
• Python 3.x
• Virtual environments (venv) & pip (listed in README)
• No web or database component—entirely file-based scripts