Fridolín Pokorný

> @fridex could you have a look at this, or is it better to reassign it? thx! Let's reassign it. Thx!

This [resulted in PEP-710](https://peps.python.org/pep-0710/). Please [feel free to participate in the discussion](https://discuss.python.org/t/pep-710-recording-the-provenance-of-installed-packages/25428) if you find this feature valuable. Thank you!

> Thanks for the info. So, the goal is to implement some kind of report functionality into micropipenv when the pip starts to provide files proposed in the PEP we...

> Consumers can automatically take the file when needed. If micropipenv upstream decides to be the consumer of this file, it can provide some kind of ``report`` subcomand. IMHO, it...

> It sounds like this PEP would give us the information we've asked for with this issue, so support for it (at least in a behavioral/outputs sense) seems appropriate 🙂...

I was thinking about a solution for this. We could add inter-process communication that would guarantee that `stack_info` is propagated correctly to the parent process once the child process is...

The problem here are users that will not get any recommendations if OOM is done. What we could do - if there is a risk of OOM, we could stop...

/remove-lifecycle stale We can do this once the recommendations for one runtime environment stabilize. It will be just a manner of providing a workflow for this with a task that...

> @fridex do we have an issue to create the workflow? if not, could you please create it? thx! This user story will deserve multiple changes - I've added a...

Still relevant, see also linked issues. /remove-lifecycle rotten