René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Section 3.3: Code Decoupling \u0026 Abstractions","articleBody":"I like the spirit of [Section 3.3](https://carpentries-incubator.github.io/python-intermediate-development/instructor/33-code-decoupling-abstractions.html) but not so much the delivery.\n\nIn the first exercise we separate out the data loading from the analyse function (good!), so we end up with two functions\n```python\ndef load_inflammation_data(dir_path): ...\ndef analyse_data(data_dir): ...\n```\nI would think it would make some sense to completely decouple these two functions so that when they are used, a user would do something like\n```python\ndata = load_inflammation_data(\"/path/to/data\")\nresult = analyse_data(data)\n```\nbut instead the example leaves the `load_inflammation_data` call inside `analyse_data`. This isn't the worst thing in the world to do but I would think that separating them would be better?\n\nThen in the next example they suggest going more towards this approach, but by introducing a class `CSVDataSource`. This seems a little pointless to me, and in fact Pylint would complain about this class having too few methods ([R0903](https://pylint.pycqa.org/en/latest/user_guide/messages/refactor/too-few-public-methods.html))! And in the end they still pass that class to the function and rely on duck typing to load the data...\n","author":{"url":"https://github.com/tomneep","@type":"Person","name":"tomneep"},"datePublished":"2025-02-20T16:44:18.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/12/python-intermediate-development/issues/12"}