Griatch

Yes `evennia test enennia.accounts` will work. To get to a specific test in a tests.py module you could also specify down to class or even class method level; like `evennia...

@BeaData Any tests are good tests. See the first post of this issue, they should help to get you going. Pick an untested module/package that looks interesting to you. :)

@selberhad Oh, haven't looked at the detailed coverage in the while. I updated the root now, so you should be able to see the source code. Thanks for the heads...

Turns out that coverage doesn't like parallel execution. The coverage data was fixed now, so `develop` branch shows the correct percentage (66%): https://coveralls.io/github/evennia/evennia?branch=develop :tada:

Kudos for providing a unit test - this made this easy to reproduce! :+1: After some digging, I figured out what was going on here - the alternating row lengths...

Interesting observations, thanks for your work on this so far! - The `PYTHONPATH` is generally necessary to allow imports across the library on different platforms. If it is necessary at...

The checks done here are superseded by one big point - PyPy currently (Sept 2019) is only compatible with CPython 3.6. So this is put on hold for now.

I agree with this particular error probably being worthy of an exception, just not 100% sure about putting these are separate settings variables; it may be more appropriate to have...

As an update, I have not forgotten about this, but I'll hold off on merging it for a little. I'm considering if it's better to organize strings like this differently...

Fixed this within the `help` command and `format_grid` as suggested. In the future, the moving of markup-to-ANSI parsing to the protocol level will likely lead to resolving this in another...