Removing Python since C# is complete and I need time to make it use a bytes approach

Appreciate you! I'll get on that when I come back to the Python edits!

Probably you wanna use this: https://docs.python.org/3/library/io.html#io.BytesIO

Just don't have any tests over a thousand bytes or so, literally pointless.

Tests should not print to console.

You can't (safely). There's a few similar interfaces in Python that could be used though.

Corrected.

Makes sense. Went and reduced the 'super large' tests and reduced the overall number of tests period, since FNV1 is fairly simple to implement.

Either tighten the performance requirements to require actual optimisation (I have no idea if any exists) or remove the "performance" tests as there is no way to fail them. All they do is annoy the user.

Implementing the algorithm exactly as laid out in the description clears the tests (and is intended to) so why make it take several seconds when milliseconds is enough to verify correctness.

Random import of sys in the solution setup?

Invalidating solutions doesn't matter. Nobody loses points for it.

Random test for Rust and fix Setup

Approved by Johan

If someone gets sad because their solution got invalidated, they can always submit a new one. Invalidation of solutions during beta process is perfectly fine. It's also not a great thing to document an oversight after one day and keep it forever, instead of fixing it and having a good thing for the years to come.

I personally do not like option 1, because "FNV, but with arbitrary, artificial additional conditions" is, well, not FNV. Going option 2, you can not only implement FNV to its full spec, but you also have a chance to build a nice exercise with a practical interface based on, for example, streams, which I believe would be much more beneficial to people who try to solve it. Making the functions accept a System.IO.Stream (or whatever equivalent of a binary stream in Python) would IMO make it as close to a "good interface" as possible.