How artist-newgood/python-tasks_github works
Project type and purpose
• This is a small, script‑based Python project containing two independent “matrix” tasks (Python_task_1_matrix and Python_task_2_matrix).
• Each task folder holds:
• A Python script (.py) that implements the matrix logic
• A task‑description.txt that spells out the requirements
• A test‑data.txt with sample inputs/expected outputs
• There is no frontend, backend server, database, or external service—just standalone CLI scripts plus IDE config (.idea) and sample files.
File structure
• Top level:
• .idea (IDE configuration – not part of runtime)
• Two task folders (each is a self‑contained module)
• README.txt, task-description_sample.txt, test-data_sample.txt (documentation/sample data)
• No build scripts, no dependencies beyond the standard Python interpreter.
README
• The README is empty, so there are no explicit architectural notes or dependency lists. All architecture must be inferred from the file tree.
Main components
a. Python Interpreter (runtime)
b. Task Module 1 (Python_task_1_matrix)
• Script: Python_task_1_matrix_18.09.22.py
• Task Description
• Test Data
c. Task Module 2 (Python_task_2_matrix)
• Script: Python_task_2_matrix_18.09.22.py
• Task Description
• Test Data
d. User / Developer
e. Documentation folder (README & sample files)
Relationships and interactions
• The user/developer invokes each script via the Python interpreter.
• Each script reads its own task-description.txt and test-data.txt files as input (or those files are read by the developer to run and verify the script).
• The Python interpreter executes the script logic, producing output on the console or writing to files (not shown in the tree, but implied).
• The sample docs (task-description_sample.txt, test-data_sample.txt) serve as reference inputs.
Architectural patterns or principles
• There is no layered or service‑oriented architecture; it’s simply two standalone CLI programs.
• Separation of concerns: each task folder encapsulates its own code and data.
• Keep environment config (.idea) separate from code.
Technologies and libraries
• Core: Python 3.x interpreter
• No external frameworks or libraries are visible in the file tree.