Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More explicit list of limitations/restrictions on the underlying processes #71

Open
chrahunt opened this issue Mar 20, 2022 · 0 comments

Comments

@chrahunt
Copy link
Owner

chrahunt commented Mar 20, 2022

From the README it's not clear what the differences are for a process running normally and under quicken.

What is different:

  • the environment, stdin/stdout/stderr, umask, cwd, sys.argv, pid will be different between the execution of the top-level code (e.g., imports, function definitions, global variable definitions) and the execution of the entrypoint
  • signals to a quickened process are proxied to the actual process (source)
  • the actual app being executed will be a child of the command server, not the users shell
  • there may be a long time between execution of the top-level code and execution of the entrypoint (for edample, state retrieved at the top-level of an application may be stale by the time it is used)

What isn't different:

  • global changes made from the application entrypoint onward will only exist in that instance of the application

TBD:

  • atexit callbacks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant