Note: there's a few use-cases in-tree where both: * We have a lockfile that's been generated that isn't influenced by vendored (or pypi-installed) packages * We're using said lockfile in an active Mach process, so the lockfile isn't fully being honoured (already-imported packages are being used, even if they are different from the locked versions).
Bug 1732946 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Note: there's a few use-cases in-tree where both: * We have a lockfile that's been generated that isn't influenced by vendored (or pypi-installed) packages * We're using said lockfile in an active Mach process, so the lockfile isn't fully being honoured (already-imported packages are being used, even if they are different from the locked versions). This will require some shaking-down of the tree to conform :)