Hello,
I am looking for clarification about the identity and lifecycle semantics of PythonAnywhere consoles. The questions are about general platform behavior only; I am not asking you to inspect a specific account or console.
Could you please clarify the following points, ideally indicating whether the behavior is a documented/stable provider guarantee, current implementation behavior, behavior that may change, or behavior that is unknown/not guaranteed? Where possible, please answer Q1 through Q8 separately.
Thank you.
<h2>F. Exact provider question set Q1..Q8</h2>Q1:
What exact entity does {id} in /consoles/{id}/ identify: logical console object, running backend process, shell-process generation, browser-connected session, or another entity?
Q2:
What are the uniqueness domain and ID-reuse semantics? Can a deleted, expired, killed or terminated {id} ever be assigned to another console object or instance?
Q3:
On browser disconnect/reconnect, does the same {id} prove the same shell-process generation, or only the same logical console object?
Q4:
On backend restart, process death, server maintenance or console reset, can {id} remain unchanged while the shell-process generation changes?
Q5: Is there a public/stable immutable generation identifier, creation-generation token, provider-attested process-generation field or equivalent?
Q6: Is there a field with stable semantics for process start time, creation time, generation counter or instance incarnation that distinguishes recreation under one logical console object?
Q7: Can PythonAnywhere produce a provider-controlled attestation binding console ID, exact instance/generation and lifecycle/continuity semantics without target-console self-report?
Q8:
Which events invalidate the equivalence same console ID = same exact running console instance?
