On Fri, Aug 26, 2016 at 9:54 AM Ronny Pfannschmidt < opensou...@ronnypfannschmidt.de> wrote:
> the problem it creates is, that we need to load plugins before even > parsing the config and before even having config object just in order to > literally monkeypatch a module > You mean that just importing "pytest" you automatically load all plugins? Hmmm I agree that's not very nice. 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. > also - import works just fine - there is no need for a dynamic namespace, > people can import from concrete/correct locations > I see, but TBH I don't see how we could just deprecate that without providing an alternative solution which won't break user code. Too many plugins and code depend on that, and we would need to have a **really** good reason to break them all in a future pytest version (I wouldn't even dare to introduce such a deprecation until 4.0 for example). But that's my opinion of course. Cheers, Bruno.
_______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
