Closed H-Shay closed 2 years ago
Sorry to be the bearer of bad news (though this might save you the hassle of maintaining these later, so maybe it's good news!)
There appears to be a types-opentracing
package (this is a common theme; worth checking for types-xxx
and xxx-stubs
when wanting stubs for a module xxx
).
If you remove the lines from mypy.ini
that skip opentracing and do pip install types-opentracing
, does it lead to great success?
If so, that may be the way to go — I suppose it would need to be added as a dev dependency.
If you remove the lines from
mypy.ini
that skip opentracing and dopip install types-opentracing
, does it lead to great success?It does indeed lead to great success. I will put up a separate PR with these changes, I suppose the best thing to do with this PR is to close/scrap it?
It could be great to use those on Synapse too! Might be worth filing an issue.
It does indeed lead to great success. I will put up a separate PR with these changes
woot!
I suppose the best thing to do with this PR is to close/scrap it?
Yes, probably. Sorry. But thanks for taking the time to do it anyway :)
There appears to be a
types-opentracing
package (this is a common theme; worth checking fortypes-xxx
andxxx-stubs
when wanting stubs for a modulexxx
).
If it's any consolation, the package is apparently really new: first released last Thursday!
It could be great to use those on Synapse too! Might be worth filing an issue.
I can just do this today, not a problem.
To cross reference, this was done in #287.
When looking at how to get Sygnal to 80% precision, I noticed many of the imprecise lines were either from intentional
Any
s in our code (i.e. Json dicts withDict[str, Any]
as the type and similar situations) or un-typed third-party code, so I tackled stubbing some of those libraries. More to come.