tcod_tutorial_v2 VS typing

The map shouldn't be hidden by the changes. You can compare your sources with the expected part-6 sources here.

The old branches from 2020 don't work anymore. So I tried to get the changes from the new version and update the old part-13 (final) branch. You can find it in backports branch of my repo. This won't be merged with upstream, and here is the reason why.

engine is supposed to exist as engine.py in your projects working directory. See the part-3 example code for the correct layout. Something as simple as running main.py from a directory other its own will cause imports to not be found, so try running the sample code once.

The engine itself had a few fixes which were planned for a 2021 tutorial which wasn't finished, those changes and panned ones are listed here and include things like a dedicated data directory, most modules being moved into a package, an updated color scheme, automated linting, and automated deployment of Win/Mac/Linux builds. Since then I didn't do much other than test a scene graph implementation that I've mentioned previously.

I've made an issue to keep track of my current progress, and I'd also like suggestions on what people want updated in the tutorial.

I finally remembered to add a license to the v2 Python tutorial. It is now in the public domain.

The latest tutorial with type-hinting is the "new" one, but this is if you wanted to follow the tutorial. To review the code itself you should look at the GitHub repository instead. This tutorial was written for Python 3.7.

Iterable[str] is unfortunately evil as it matches str which is often unintended. (see: https://github.com/python/typing/issues/256) One would need both NOT-type and AND-type in order to properly handle these.

The basic motivation behind them is that functions can have arguments that can only take a specific set of values, and those functions return values/types change based on that input. Common examples are (you can find more here):

While yes 26 people liked the idea here: https://github.com/python/typing/issues/193

but looking at relevant issues on GitHub it seems this has been shot down repeatedly. python/typing#18, python/typing#213

See https://github.com/python/typing/issues/256 for a discussion.

Lower bounds are not supported for TypeVars, unfortunately.

Mypy allows that because initial versions of PEP-484 allowed that. This has changed; here's the current wording on the PEP:

> This is no longer the recommended behavior. Type checkers should move towards requiring the optional type to be made explicit.

https://www.python.org/dev/peps/pep-0484/#id29

Dunno, other, larger projects than the one I'm working on seem to run up against this from time to time. (rasa_core, to pick one example from near the top of a Google search; also Telethon, Blender, TensorFlow, Pandas. Guido also filed a bug on the typing module in an early version of Python 3.5 because of unexpected implications of this particular issue, so the problem isn't exactly purely theoretical.) That's aside from the wish for conceptual purity in the call signatures of classes and their subclasses, which is not always and automatically a bad wish to have; and the notion that a language that prides itself on its introspective faculties might want to make introspection of classes from the top of a class hierarchy possible, at least in theory? Perhaps to facility learning about the language and/or visualizing large class hierarchies easily, for instance?