Suggestion: add support for sessions

[n05tr0m0]

Hello Evgeniy,

Attended your presentation and would like to suggest adding session functionality to your utility.

Purpose of functionality:

Imagine working on a script and suddenly need to interrupt work to switch to a higher-priority task. Currently, every time the script starts, instld downloads all necessary libraries for it to function properly. With session functionality, won't have to wait for libraries to be downloaded each time. If need to interrupt work while a script is still in progress, can use a command like "instld session save", and stop work. When ready to continue working with the script, can use a command like "instld session restore". For remove session can use: "instld session remove or delete" or remove session after use command "instld session restore".

Session functionality will remember which script it was executed for. Instld will keep the path and name of the script.

Thank you!

[pomponchik]

Hi! I'm glad to see you here.

Tell me in more detail, how do you see this functionality? Which of the three modes of operation do you want to add it to (REPL, script launch mode, context manager)? How do you propose to make a custom API for these functionalities? What specific information should be stored as part of sessions, where will it be stored and in what format? In your opinion, should any session be created by default? How does the session differ from the temporary virtual environments that instld is already working with?