Blackifying and fixing bugs
source link: http://evennia.blogspot.com/2019/09/blackifying-and-fixing-bugs.html
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Blackifying and fixing bugs
Since version 0.9 of Evennia, the MU*-creation framework, was released, work has mainly been focused on bug fixing. But there few new features also already sneaked into master branch, despite technically being changes slated for Evennia 1.0.On Frontends
Contributor friarzen has chipped away at improving Evennia's HTML5 web client. It already had the ability to structure and spawn any number of nested text panes. In the future we want to extend the user's ability to save an restore its layouts and allow developers to offer pre-prepared layouts for their games. Already now though, it has gotten plugins for handling both graphics, sounds and video:
On Black
Evennia's source code is extensively documented and was sort of
adhering to the Python formatting standard PEP8. But many places were sort of hit-and-miss and others
were formatted with slight variations due to who wrote the code.
After pre-work and recommendation by Greg Taylor, Evennia has adopted the black autoformatter
for its source code. I'm not really convinced that black produces the
best output of all possible outputs every time, but as Greg puts it,
it's at least consistent in style. We use a line width of 100.
I
have set it up so that whenever a new commit is added to the repo, the
black formatter will run on it. It may still produce line widths >100
at times (especially for long strings), but otherwise this reduces the
number of different PEP8 infractions in the code a lot.
On Python3
Overall
the move to Python3 appears to have been pretty uneventful for most
users. I've not heard almost any complaints or requests for help with
converting an existing game.
The purely Python2-to-Python3
related bugs have been very limited after launch; almost all have been
with unicode/bytes when sending data over the wire.
People
have wholeheartedly adopted the new f-strings though, and some
spontaneous PRs have already been made towards converting some of
Evennia existing code into using them.
Post-launch we
moved to Django 2.2.2, but the Django 2+ upgrades have been pretty
uneventful so far.Some people had issues installing Twisted on Windows
since there was no py3.7 binary wheel (causing them to have to compile
it from scratch). The rise of the Linux Subsystem on Windows have
alleviated most of this though and I've not seen any Windows install
issues in a while.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK