How akhilr529/python_practice works
Project type and purpose
• This is a personal “Python Practice” repository, not a deployed application.
• Purpose: daily exercises in core Python concepts (syntax, data structures, OOP, file I/O, logging, etc.) and demonstration of solutions via scripts and notebooks.
File structure
• Top-level categorization:
– Notebooks: *.ipynb (daily practice in Jupyter)
– Scripts: .py files for utilities, data models, test harnesses, command-line tools
– Data & config: .csv, .json, .yaml, .ser, .txt files, material/ folder with reference notes
– Logs: .log files showing output from various runs
– Archives: .zip files containing previous sessions or bulk data
• Patterns & conventions:
– Module-based approach (e.g., module1.py, module2.py, custom_logger.py)
– CLI entry-points (demo.py, receiver.py, sender.py, test*.py)
– Dedicated logger components (custlogger.py, cust_console_logger.py, logging_config.init)
– Data modeling scripts around emp.py, student.py
Extract insights from the README
• No high-level system architecture described—focus is on learning outcomes.
• Emphasis on modular code and incremental practice.
a. Main components
1. Notebooks layer (daily practice, interactive exploration)
2. Core modules layer (reusable Python modules: data models, algorithms)
3. Utilities layer (logging, CLI handlers, file I/O helpers)
4. Data & material layer (datasets, reference materials)
5. Test harness layer (scripts that validate or demonstrate module behavior)
6. Outputs layer (log files, serialized data, console output)
b. Relationships & interactions
• Notebooks import core modules and utilities to run examples.
• Core modules read/write data from the Data layer.
• Utilities provide logging and argument parsing to both notebooks and scripts.
• Test harness scripts invoke core modules and utilities and generate logs.
• All scripts and notebooks produce outputs (logs, serialized data) captured in the Outputs layer.
c. Architectural patterns & principles
• Modular separation: data models vs. utilities vs. test drivers.
• Single Responsibility: each module handles one concept (e.g., logging, command-line args, data serialization).
• Reusability: core modules are consumed by both notebooks and CLI scripts.
d. Key technologies/frameworks
• Python 3.x standard library (logging, argparse, file I/O)
• Jupyter notebooks for interactive practice
• YAML/JSON/CSV for configuration and sample data