Pythonwhat

Improved

Documentation has been improved significantly (hopefully):

- Every 'compound statement check' has an example with explanation in the reference now.
- Common usecases have additional examples
- Checking compound statements article has been simplified, limits to context now.
- More helpful message in case check_object or has_printout not called on root state
- More helpful message in case the zoomed in on object is not an AST
- Explain has_equal_value vs has_equal_ast
- Get rid of some articles in favor of more fleshed out reference documentation

Fixed

- CI is now using the `datacamp` account on PyPi

Fixed

- Tuples of Numpy arrays can now be checked properly.

Removed

- Code in `ObjectAssignmentParser` that is not used.

Added

- Function `has_no_error()` to check earlier on whether the student did not generate any errors.

Improved

- Messaging between V1 and V2 is entirely consistent now.
- No need for `__JINJA__` prefix in custom messages specified in SCTs anymore.

Removed

- No more support for `expand_message` argument in old 'node checking functions' such as `test_for_loop()`.

Added

- Ability to check class definitions with ``check_class_def()`` (and ``check_bases()``). Tested and documented.

Changed

- The `check_object()` only on root check is only done if `PYTHONWHAT_V2_ONLY` environment variable is set.

Added

- More checks that guard against commonly made mistakes (some in v2 only, others not)

Added

- Function documentation (with examples) for `multi()`, `check_or()`, `check_correct()` and `check_not()`

Changed

- If an SCT is incorrectly coded, it will generate more easily understandable errors so the author can easily fix the issue.
- If an SCT correctly runs but does not make a lot of sense, easily understanble errors will be thrown so the author can make improvements.