Fix resource leaks caused by `pkg_resources` about protofuzz

[jscanlannyc]

Cool, that was helpful. I do have a PR ready that passed tests through this cmdline workflow:

python3 setup.py install; 
python3 -m unittest discover; 

I will issue the PR shortly.

[jscanlannyc]

Hi,

I am interested in fixing this issue. I have a few smaller questions before I write an implementation, as I do not want to annoy with a bad PR. I am flexible on all these answers, I see some of these as improvements, but I also know that keeping the change small is more manageable.

1. Would it be OK if I replaced .format() with f-strings?
2. Would it be OK if I used pathlib instead of strings for file location?
3. While resolving the location fuzzdb dependency with importlib, would you like this to potentially be configurable as an env variable (os.environ)? This is in case someone installs this via pip or does not --recursively clone the project or has a separate fuzzdb instance they maintain.
4. How do you feel about type annotations?

Please let me know. Thank you for your time.

[woodruffw]

Thanks for stating your interest!

• Would it be OK if I replaced .format() with f-strings?
• Would it be OK if I used Pathlib instead of strings for file location?

Yes, and yes! Please do these, any modernization would be greatly appreciated.

3. While resolving the location fuzzdb dependency with importlib, would you like this to potentially be configurable as an env variable (os.environ)? This is in case someone installs this via pip or does not --recursively clone the project or has a separate fuzzdb instance they maintain.

Sounds good to me. This is definitely a usability annoyance at the moment.

4. How do you feel about type annotations?

We love type annotations! Any you add here would also be greatly appreciated.

[jscanlannyc]

Thanks so much for the quick reply.

I have made my changes and would like to verify them against the test suite before issuing a PR. What is the suggested workflow for that? The nose website says it is in maintenance mode, should I use nose2? Something else?

[woodruffw]

Hmm, you shouldn't need either -- the tests under protofuzz/tests should be bog-standard unittest-based tests, meaning that the default built-in harness should work:

python -m unittest protofuzz.tests

(I think that's the right syntax.)

[woodruffw]

Whoops, this should work:

python -m unittest discover

[woodruffw]

Awesome! Feel free to give me a ping on it when you submit it.

[woodruffw]

#68.