Following up on jupyterhub/binderhub#1017 (comment). In particular the comment about "reduce duplication".

A possible way to do that which I've seen in other projects is to add an endpoint to the backend from which the UI loads the config. We'd have an endpoint like binder.example.com/_config which returns a JSON which is then used to configure the dropdow

In runtime configurations, it would be helpful to import/export runtime configurations.
In addition, importing / exporting a list or selection of configurations would be a nice additional feature

Objective

Python 3.6 and above supports type hints and optional statically typing of Python code. Since its introduction is has seen a lot of adoption in many Python projects in particular in larger code bases. Type hints are completely optional and are stripped by the Python parser before runtime.

I am not the only one @plumerai anymore who li

Ian and I are always saying "Oh, it'd be great to have this example in our docs!" but because we can't always add them immediately we don't and we end up losing them. This issue is an effort to document these little good snippets that we wish we had to someday actually add them to our docs.

Please feel free to drop yours in the comments :)
Just add a sentence (or more) explaining what the exam