Michael Lenzen
Michael Lenzen
> # Migrating your code style without ruining git blame > A long-standing argument against moving to automated code formatters like Black is that the migration will clutter up the...
GitHub respects the `.git-blame-ignore-revs` file now: https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view
Maybe ditch 3rd party services? https://hynek.me/articles/ditch-codecov-python/
This is blocking #41 Work is being done in core Python that may obviate this issue. - https://github.com/python/typing/issues/689 - https://mail.python.org/archives/list/[email protected]/thread/NDEJ7UCDPINP634GXWDARVMTGDVSNBKV/ - https://www.python.org/dev/peps/pep-0661/#reference-implementation
Maybe, add a list to the backing. Whenever a mutable elem is added/accessed, it would fall back to the list.
I think this does make sense, it won't reduce performance, it will just make bag more flexible.
Not going to do, invalid syntax for old versions.
Maybe only support recent versions in 1.0
Can support 2 & 3 by putting the annotations in a stub file or as a comment - https://www.python.org/dev/peps/pep-0484/#stub-files - https://www.python.org/dev/peps/pep-0484/#suggested-syntax-for-python-2-7-and-straddling-code
Check that autodoc uses type annotations https://pypi.org/project/sphinx-autodoc-typehints/