Jake Vanderplas

Thanks for raising this! That would be great. One choice we have to make is whether to continue inferring the dtype from pandas dataframes, or just leave all type inference...

Thanks – I think this has to do with the way temporal data is serialized to JSON.

Thanks! Note the line at the top of the file: https://github.com/altair-viz/altair/blob/0217b2e73703d3b7b529b73b4dec9c17e7fb09bb/altair/utils/schemapi.py#L1-L2 You should make these changes in https://github.com/altair-viz/altair/blob/master/tools/schemapi/schemapi.py instead, and then run [generate_schema_wrapper.py](https://github.com/altair-viz/altair/blob/master/tools/generate_schema_wrapper.py) to sync the results to this file.

I've seen this before reported on Vega-Lite, but I can't find the issue reference right now.

No, I'm not aware of any functionality to automatically prevent text overlap. It would be worth a feature request in Vega-Lite.

No, it has not been implemented yet as far as I am aware.

Can you clarify what you mean by "the most verbose"? For example, if you have something like ```python chart.encode(x='x') ``` do you want the result to look something like this?...

Thanks - I think the closest thing to getting this kind of verbose specification would be to do a `to_dict`/`from_dict` round-trip. This would wrap each entry in the associated schema...

Thanks for looking into this - unfortunately I don't think this is something we can merge. When using Jupyter Notebook, this will break in very strange and confusing ways if...

Given the problems users have reported in the past, I think we need to avoid at all costs the possibility of charts being created with matching output div IDs. Div...