Portability of notebook export/import will be an issue irrespective of multi-interpreter support or not since the interpreter configurations are not part of note. One could also argue that it can never be part of the note since the environment could be different between source (from where note is exported) and the target (where note is imported)
Regarding multiple interpreter support, it will be better if we handle the interpreter definition purely by referring to "alias" as first class citizen. For e.g., if we have two spark interpreters "spark-dev" and "spark-prod", we should be able to refer anyone of the interpreters using the alias name like below. %<ALIAS_NAME>.<INTERPRETER> For e.g., %spark-dev.spark %spark-prod.pyspark %spark-prod.spark -- View this message in context: http://apache-zeppelin-users-incubating-mailing-list.75479.x6.nabble.com/Multiple-spark-interpreters-in-the-same-Zeppelin-instance-tp2171p2997.html Sent from the Apache Zeppelin Users (incubating) mailing list mailing list archive at Nabble.com.
