A server backend for interactive online exercises.
Testing and documentation
Testing is done using tox. Install it, and run it from the command line in the repository root. This will create a virtualenv for each supported environment, install the necessary things in it, run the tests, and build the documentation.
Speeding up builds
[global] use-wheel = True [install] find-links = /tmp/wheelhouse [wheel] wheel-dir = /tmp/wheelhouse
After that, build wheels out of the requirements by running the following command once:
pip wheel -r requirements.txt -r requirements-docs.txt -r requirements-testing.txt
That will build wheels, which are faster to install than regular
packages. You can make installations even faster by adding
= True to the
[install] section; that way, installations won't
even hit PyPI, further reducing latency. Keep in mind that you will
then no longer be able to use
pip install to install anything,
unless you've first made a wheel out of it.
Added per-user secrets. Once pyca/cryptography will have HKDF support, this will turn into per-user entropy.
Also minor fixes, version upgrades.
Now being continuously tested on Travis, with coverage monitoring thanks to Coveralls.
Several other minor improvements:
- A useful mixin for resources that represent exercises, for helping them resolve and notify when an exercise is completed.
- User e-mails are indexed.
- Persisted factories are now unary callables that take a store. This prevents some otherwise icky global mutable state.
- New behavior for adding persisted factories: addOrUpdate; don't just blindly add more factories with the same identifier.
- Added support for a
dhparam.pem, enabling DH-based PFS ciphersuites. ECDH-based PFS ciphersuites is a work in progress, see #6.
- Moved requirements into setup.py for easier installs
clarentversion requirement bump
- localhost manhole support for debugging
- Only support good ciphersuites.
Renamed to merlyn (see "Whence the name" below).
- Drastically simplified exercise API
- Authentication API based on SSL certificate verification
- Basic documentation for steps and exercises
- Interfaces: IStep, IRenderer, IValidator (see docs)
- A renderer based on string templating (str.format)
- repoze.sphinx.autointerface -> sphinxcontrib-zopeext, which appears to be a shinier, more updated version of the same thing
- Exercise and Step classes
- Step validation draft
- Step solution submission interface
Initial public release. Nothing much to see here.
Whence the name?
This project was originally called merlin, because the step-by-step oracle-like model reminded me of Merlin in the AM complexity class and Arthur-Merlin protocols. It's since been renamed to merlyn, because the primo merlin PyPI real estate has been taken up by some kind of weird setuptools fork.
Since Arthur is the person who performs the protocol together with Merlin, it only made sense to name the client side project arthur. Finally, clarent, named after king Arthur's ceremonial sword, holds common tools.