* Floris Bruynooghe <[email protected]> [2016-09-05 12:11:12 +0100]: > > > the second problem it creates is, it makes the pytest namespace > > > impossible to introspect for external tools > > > > > > I agree that's annoying, but that's a problem in general on how dynamic > > > pytest is (IDEs don't autocomplete on fixture parameters either), so I > > > would say this is small. > > If the external tools would call `pytest.init()` before introspecting > then it would work just fine. We could even provide a pylint plugin > by default for this in that case. That would be nice.
FWIW I recently updated pylint's "brain" module for pytest so it at least understands stuff added in pytest 3: https://github.com/PyCQA/astroid/commit/8ec025fa36c9c627bcdd6da7fab56271731d47eb But I agree this is less than optimal. Florian -- http://www.the-compiler.org | [email protected] (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/
signature.asc
Description: PGP signature
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
