qutebrowser/tests
Florian Bruhin aa5da1b312 Don't set up YAML constructors/resolvers for default loaders
After reading https://pyyaml.org/wiki/PyYAMLDocumentation again, turns out
Loader.add_constructor and .add_implicit_resolver are actually *class* methods.

In other words, we've been adding dozens of constructors/resolvers to the
default YAML loader object, causing it to slow down massively in other tests
which call configdata.init().

Instead, create our own loader class and only add them once there.

I'm still not sure why this caused the duration to increase with every YAML load
though - that might still be some kind of bug in PyYAML.

Fixes #2777
2018-02-10 19:35:03 +01:00
..
end2end Don't set up YAML constructors/resolvers for default loaders 2018-02-10 19:35:03 +01:00
helpers Update pytest log handling 2018-02-06 23:17:40 +01:00
manual Update some more references to old config options 2017-07-04 16:46:02 +02:00
unit Merge remote-tracking branch 'origin/pr/3430' 2018-02-10 16:27:41 +01:00
conftest.py Skip failing scrolling tests on Qt 5.10 on Travis 2018-02-08 10:42:55 +01:00
test_conftest.py Update copyright years 2018-02-05 12:19:50 +01:00