@abuckenheimer wrote:
a couple thoughts:
on size: The actual size of the dependency isn’t that bad, I run most of my stuff ontop of a docker image (jfloff/alpine-python:3.7) and
pip install requests-asynconly costs 9mb (a 3% increase) in my image sizeon experience: I think being able to test your application is a pretty core functionality, I lean towards keeping it as it keeps the developer experience better and especially if it makes contributor lives easier.
I think I lightly lean towards making it a hard dependency, especially to start if it keeps complexity down. We can always factor it out later if we find its strongly desired. That said if you think its a good point to start that testing repo and don’t think it will be that hard then by all means charge ahead.
