Philipp Rudiger

Interesting, I haven't really thought about it and would have to play around a bit to see if it's possible. An issue on the hvPlot tracker would definitely help me...

This would also be very helpful for [geoviews](https://github.com/pyviz/geoviews).

The main problem I see with proposals as laid out above is that object references are not handled, i.e. if two objects reference the same subobject there is no way...

>Or did you mean that automatic serialization would always create such separate objects, to make the implementation easier, while a user hand-writing their own .yml file wouldn't have to do...

>If you catch that happening, please file an issue; I don't think there is any valid scenario where the name would be ignored. This would likely be because some subclass...

@ea42gh Happy to make you an external collaborator so you can push to @MarcSkovMadsen's PR.

@ea42gh Now that I've added you (and once you accept), you will be able to clone the repo, check out Marc's branch (once he's pushed it to the param repo),...

Ahh, seems this is actually expected behavior according to the docstrings. ``` Ordinarily, when a Python object is instantiated, attributes not given values in the constructor will inherit the value...

This will be a major backwards compatibility breakage that I expect to affect a lot of people, not just Panel internally but we have plenty of examples iterating over `.objects`...

Really don't see how, I really only think we can safely do this in 2.0.