future-fstrings

I did something similar to option 3 to make the builtin numeric types "callable", since the dunder __call__ methods can't be overwritten for builtins. For example, in regular arithmetic notation, something like 6(7+8) could be read as 6*(7+8), but trying to do this in Python gives you `SyntaxWarning: 'int' object is not callable;`, since you're essentially trying to do a function call on the literal 6. The workaround was to use a custom codec to wrap all integer literals to give them the expected call behavior. Repo if anyone is interested: https://github.com/ckw017/blursed This was inspired by a way less silly usecase, future f-strings, which added f-string support to older versions of Python in a similar way using codecs: https://github.com/asottile-archive/future-fstrings

In case anyone is stuck on older versions of Python for any reason, here are some backports of some of the listed features: * f-strings: https://github.com/asottile/future-fstrings (this is a pretty crazy hack, all the way to Python 2) * pathlib: https://pypi.org/project/pathlib2/ * typing: https://pypi.org/project/typing/ * enum: https://pypi.org/project/enum34/ (doesn't include any additions in 3.5+) * functools.lru_cache: https://github.com/jaraco/backports.functools_lru_cache * dataclasses: https://github.com/ericvsmith/dataclasses (3.6 only, requires ordered class __annotations__) I'm half-expecting someone to come along with a hacked-up Python 2 backport for implicit namespace packages :)