You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Providing the --verbose argument to pip when installing a package via git+https does not result in the verbosity being passed down to the VCS (Git) subshell commands, e.g. git submodule update.
I am on a slow and unstable internet connection. When installing packages via git+https with lots of submodules I'd like to stay informed on the progress, as to ensure that I still have a connection to the Git repository hosts referenced by the submodules and can identify when Git has detected a broken connection and is retrying.
What's the problem this feature will solve?
Providing the
--verbose
argument topip
when installing a package viagit+https
does not result in the verbosity being passed down to the VCS (Git) subshell commands, e.g.git submodule update
.I am on a slow and unstable internet connection. When installing packages via
git+https
with lots of submodules I'd like to stay informed on the progress, as to ensure that I still have a connection to the Git repository hosts referenced by the submodules and can identify when Git has detected a broken connection and is retrying.Describe the solution you'd like
There does not seem to be an environment variable for configuring Git verbosity globally, so passing it to the VersionControl::unset_environ base class does not seem to be an option.
Instead it might be feasible to (either/or):
VersionControl
interface to allow for explicitly passing additional subshell argumentsVersionControl
interface specifically for passing a generic verbosity flagIn both instances the subshell command(s) affected by this feature request would need to be adapted to accept the verbosity flag.
Alternative Solutions
As described in solution
Additional context
n/a
Code of Conduct
The text was updated successfully, but these errors were encountered: