Mateusz Paprocki

See http://docs.python.org/2/library/stdtypes.html#str.decode. We can ignore errors, replace invalid byte sequences with 0xfffd (unicode replacement character) or (what I didn't know before) register a callback to handle errors. However, I think...

``` **Owner:** --- ``` Original comment: http://code.google.com/p/sympy/issues/detail?id=1198#c8 Original author: https://code.google.com/u/101069955704897915480/

> Although we protect usage behind TYPE_CHECKING as policy, it's just one more thing to have to keep track of in some way. This days it isn't much work at...

* we should remove any dependency that isn't actively being used, so we can base decision strictly on what, if anything, is needed in this particular module, in the future....

There are `Axis.axis_label_align` and `Axis.axis_label_text_align` properties, which respectively control how axis label is aligned along axis' panel and how text within that label is aligned. One doesn't have to influence...

This is due to efforts to circumvent issues `overflow: hidden`. I guess there's no winning with CSS. Not marking this issue as a regression though, because fullscreen support is experimental...

It does have bidirectional support for `bytes ArrayBuffer` serialization.

I'm not sure what's the best way of handling this. I suppose we could have the version stored and mutated in `__version__`, and then used in `setup.py` and in `implementation_version`....

At this rate I should be done with the initial pass over all models by the end of the week.

This is how model constructor signature looks like in VSCode: