Łukasz Rogalski
Łukasz Rogalski
Quick question - why does astroid seems to be unable to fill arguments in inferred value for `open()` function? Inferred function seems to be correct - at least doc parameter...
@PCManticore I can either hardcode information on open() signature in astroid code, or use inspect module to try to fill all objects built in `raw_builder.py`. For me, second option is...
@ceridwen in which commit it was implemented?
Use mypy stub files to extract information about arguments and types of builtin and stdlib functions
This one could be a huge feature and can effectively remove astroid.brain package. Does anyone know if there are any production-ready parsers for *.pyi file format?
@stemid please re-run it on latest release (1.7.1 with astroid 1.5.2). It should work just fine.
Another case to consider, it's fairly common to mock stuff like this: ```python with mock.patch('mod1.mod2.qname', return_value=1), mock.patch('mod1.mod2.qname', side_effect=[1, 2, 3, 4, 5]): assert [1, 2, 3, 4, 5] == my_mod.tested_func()...
_Ability to test import on compiled files_ I'm quite sure you cannot build AST tree from bytecode file which means Pylint won't be able to do that. _an informational message...
You may disable those inline, although I'd just ignore all of them in pylintrc file. I'm just not sure what new problems would arise due to lack of those stdlib...
For me, it would be polluting config section with option that will be almost never used. `ignore-import-errors-on-stdlib`? The point is those modules _exist_ everywhere. Why there should be a switch...
> hi there! is this in expo go? This reproduces for me in Expo Go 2.30.9, with same `expo-av` in stacktrace.