You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In setuptools and distribute there is another parameter to setup() called test_loader (http://peak.telecommunity.com/DevCenter/setuptools#test-loader) which could be used to load the setuptest test runner instead of having to monkey patch the test command. Just an idea.. :)
The text was updated successfully, but these errors were encountered:
Very interesting, should be much better than monkey-patching. I've been looking through the code now but can't figure out how test_loader can be used to alter the actual test runner. Seems like test_loader only really influences test lookup and I'd still need to do some sort of wonkey-patching somewhere. Any clues, existing package example maybe? Thanks for the pointer nonetheless, I was unaware of test_loader.
Yeah, not sure about the usefulness of the parameter, to be honest. But you could even just do the monkey patch there, it's not like setuptools isn't doing the same extensively, too ;)
In setuptools and distribute there is another parameter to
setup()
calledtest_loader
(http://peak.telecommunity.com/DevCenter/setuptools#test-loader) which could be used to load the setuptest test runner instead of having to monkey patch the test command. Just an idea.. :)The text was updated successfully, but these errors were encountered: