This isn't fixed unfortunately because the internal _pip module uses snapcraft.internal.common.run directly rather than the run/run/output methods of the plugin.
This isn't fixed unfortunately because the internal _pip module uses snapcraft. internal. common. run directly rather than the run/run/output methods of the plugin.