Errors when running the tests

[djc]

Errors when running the tests

[jjlee]

What did you expect to happen?

[djc]

I expect to be able to run tests without warnings.

[jjlee]

OK, thanks.

The warning tells me or a developer using mechanize why the tests are skipped, which is useful information to those users.

Does gentoo typically run tests when installing an ebuild? Is that why you don't want it to print the warnings? If so, is there a reason why your ebuild can't send stdout/stderr of test.py somewhere other than the stdout/stderr of your ebuild? It could use the exit status of test.py to ensure that something appropriate is output (for example, it could print nothing if the exit code was zero, or otherwise print the output of test.py).

[jjlee]

BTW, these warnings are not errors: they don't indicate that the test run failed, and the 0 exit status of test.py reflects that.

[jjlee]

Just for completeness: the SyntaxWarning is an annoyance that's hard to suppress, IIRC (hard for test.py, not hard for you, since you can just suppress the whole output).

[djc]

We use the tests to verify that the package works correctly (but we'd prefer not to install twisted just to run the test). Even if I understand that the second warning is useful somehow, the first warning is something you could easily fix, right?

BTW, I know run the tests with -Wignore, which seems okay for this.

[jjlee]

You should use the exit status of test.py if you want to know whether the tests ran successfully.

If you want to know whether the package works correctly, then you get to choose whether to make that decision based on running all of the tests, or just the ones that don't require twisted.

I still don't think this is a bug, so I'm closing the issue. If there's some specific thing you can't achieve without a change to mechanize, feel free to re-open it.