Hi Bruno,
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
the second problem it creates is, it makes the pytest namespace
impossible to introspect for external tools
also - import works just fine - there is no need for a dynamic
namespace, people can import from concrete/correct locations
-- Ronny
On 26.08.2016 13:45, Bruno Oliveira wrote:
Hi Ronny,
I'm not sure I understand what you mean by "ugly and without full
knowledge of what should happen"... could you give more details?
Also, what would we provide instead? This is a largely used feature,
I'm sure we can't just remove it.
Cheers
On Fri, Aug 26, 2016 at 4:41 AM Ronny Pfannschmidt
<[email protected]
<mailto:[email protected]>> wrote:
hi all
currently the need to initialize the namespace makes it necessary
to do
the initialization of the plugin-manager in a relatively ugly fashion
and without full knowledge of what should happen to the process
i would like to remove that need, so we only ever initialize a
pluginmanager from a call to pytest.main
-- Ronny
_______________________________________________
pytest-dev mailing list
[email protected] <mailto:[email protected]>
https://mail.python.org/mailman/listinfo/pytest-dev
_______________________________________________
pytest-dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pytest-dev
