This file is a historical cleanup note. It lists optional deletion candidates that remain archived, plus the files already removed in the first cleanup pass.
These paths are listed for historical context only. They are no longer present in the repository.
archive/skeleton.pyarchive/python_threading.pyarchive/lre.pyarchive/db_decorator.pyarchive/learning_python.pyarchive/part5.pyarchive/legacy_ops/hadoop/hbase_migrate_legacy.py
Reason:
- These were the strongest deletion candidates.
- They had little practical or educational value, or were direct duplicates.
archive/legacy_ops/hadoop/compaction.pyarchive/legacy_ops/hadoop/get_data.pyarchive/legacy_ops/hadoop/get_job_json.pyarchive/legacy_ops/hadoop/mapper.pyarchive/legacy_ops/hadoop/reducer.py
Reason:
-
Old Hadoop/HBase scripts tied to a specific environment.
-
No tests and no current repo integration.
-
archive/legacy_ops/integration/log4j_parser.py -
archive/legacy_ops/integration/log_cleaner.py -
archive/legacy_ops/integration/read_keys.py -
archive/legacy_ops/integration/send_sms.py -
archive/legacy_ops/integration/soap_send.py -
archive/legacy_ops/integration/test_avro.py
Reason:
-
Environment-specific integration scripts.
-
Retained only as historical artifacts.
-
archive/legacy_ops/postgres/calculate_trx.py -
archive/legacy_ops/postgres/check_backup.py -
archive/legacy_ops/postgres/check_idx_bloat.py
Reason:
- Large operational scripts with heavy environment assumptions.
- No evidence they are still part of a maintained workflow here.
-
technical_assessments/tt.pyReason: interactive tic-tac-toe script, no tests, low assessment/reference value. -
technical_assessments/yandex.pyReason: mixed task snippets rather than a cohesive, tested solution file. -
practice/algorithms/bst.pyReason: educational, but minimal and untested. -
practice/algorithms/permutation_string.pyReason: educational CLI exercise, limited reuse. -
practice/algorithms/fact.pyReason: mostly benchmarking/demo material, but still reasonable to keep as a language exercise.
These are not strong deletion candidates. Remove them only if the goal is to aggressively trim the repository.
Do not remove these in the first cleanup pass:
src/tests/projects/reporter/technical_assessments/practice/algorithms/files with passing embedded testspractice/leetcode/unless you explicitly want to drop the large practice archive