The hard part is usually code, but the fact they'll be writing that code in Python rather than MUSHcode should speed up the process considerably.
On the one hand you've got "installing @Thenomain's ready-to-go WoD library and tweaking it on TinyMUX" and on the other hand you've got "learning a new framework + building an entire WoD chargen/skill system from scratch in Python + redoing lots of MUSH globals that don't exist in core Evennia". There are many reasons to use Evennia. But there's no way on earth it'll be faster - or even vaguely comparable in effort.
Well. I mean. If you have an experienced Python coder on-hand, I bet they can at least come up with a sheet and stat storage system in short order. 2/3rds of the hard work that I did was emulating an indexed database by way of something more like XML. (May the sobbing begin.) The speed of using my code is that it is done. The difficulty of using my code is that it's MUX, and if you wanted to add systems it's going to be far, far faster in the long-run.
Isn't that always the case? Prototype and run, or structure and release when ready? Most Mu*s work on the former principle. I thank @Cobaltasaurus at first then the EldritchMUX gang for giving me the time and platform for doing it the latter.
(I'm done side-tracking @Saulot's thread, honest.)