Optional w3 upon package instantiation became unwieldy - a la discussion in #67
How was it fixed?
Instead of making a w3 instance optional upon Package instantiation, require it whenever creating a Package object
I left Package.set_default_w3 so that you can change the default w3 instance - which seems like something we want? (ie. to switch chains to fetch a certain deployment??)
What was wrong?
Optional
w3
uponpackage
instantiation became unwieldy - a la discussion in #67How was it fixed?
Instead of making a
w3
instance optional uponPackage
instantiation, require it whenever creating a Package objectPackage.set_default_w3
so that you can change the defaultw3
instance - which seems like something we want? (ie. to switch chains to fetch a certain deployment??)Cute Animal Picture