You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pylint dep versions:
astroid-1.4.3 colorama-0.3.5 lazy-object-proxy-1.2.1 pylint-1.5.2 wrapt-1.10.6
It also errors with pylint==1.4.5, but I think it ends up being astroid errors there.
The relevant portion of the code for the lazy:
async def metar_callback(self, cmd):
resp = await aiohttp.get(METAR_URL.format(cmd.remainder.upper()))
if resp.status == 404:
cmd.mention_reply('{} is not a valid METAR code'.format(
cmd.remainder))
return
elif resp.status != 200:
cmd.mention_reply('Unable to get METAR for {}'.format(
cmd.remainder))
return
try:
data = await resp.text()
cmd.mention_reply(data.split('\n')[1])
except KeyError:
cmd.mention_reply('Malformed METAR data for {}'.format(
cmd.remainder))
When support for Python 3.5 was added, AsyncFunctionDef
wasn't handled properly in terms of FunctionDef, which meant
that most of the checks which involved a function were never
called for AsyncFunctionDef. This led to spurious false positives
which occurred when AsyncFunctionDef were analyzed.
Closes#767
https://travis-ci.org/belak/python-seabird/builds/100674977
https://github.com/belak/python-seabird/blob/async-metar/seabird/plugins/metar.py
pylint dep versions:
astroid-1.4.3 colorama-0.3.5 lazy-object-proxy-1.2.1 pylint-1.5.2 wrapt-1.10.6
It also errors with pylint==1.4.5, but I think it ends up being astroid errors there.
The relevant portion of the code for the lazy:
And the log:
The text was updated successfully, but these errors were encountered: