Add to a new directory called "docs" or something similar. Walk through the process of resolving a broken script and describe common issues.
It would be especially cool if the notebook could show code from specific scripts within the project without copy-pasting the code (e.g. dynamically pulling code from a different file). I am not sure if this concept has an already built-out method, but it would be nice, especially when producing call-outs to explain how the GenericScraper ABC relates to the concrete scraper classes.
Add to a new directory called "docs" or something similar. Walk through the process of resolving a broken script and describe common issues.
It would be especially cool if the notebook could show code from specific scripts within the project without copy-pasting the code (e.g. dynamically pulling code from a different file). I am not sure if this concept has an already built-out method, but it would be nice, especially when producing call-outs to explain how the GenericScraper ABC relates to the concrete scraper classes.