pip fork to experiment with PEP-458 implementation https://www.python.org/dev/peps/pep-0458/: See branch tuf-v2 (and tuf-mvp and tuf-mvp-vendored for earlier work)
I don't think this is a planned use case for pip but: A user could currently run two separate instaces of pip (e.g. system pip and a pip in virtualenv) at the same time and I think it would currently mostly work. The cache directory is shared and that could lead to bugs but only very rarely.
The current plan (and implementation) for TUF integration uses a shared runtime metadata location: this would increase the chances of concurrent access and potential dataloss.
Need to assess if shared runtime metadata is a valid idea
I don't think this is a planned use case for pip but: A user could currently run two separate instaces of pip (e.g. system pip and a pip in virtualenv) at the same time and I think it would currently mostly work. The cache directory is shared and that could lead to bugs but only very rarely.
The current plan (and implementation) for TUF integration uses a shared runtime metadata location: this would increase the chances of concurrent access and potential dataloss.
Need to assess if shared runtime metadata is a valid idea