如何通过SSH免密从BitBucket使用pip安装自定义Python私有包

我尝试使用pip install git+ssh://git@bitbucket.org/my_org/my_package_repo.git命令从BitBucket安装可被多应用共享的自定义Python包，希望无需输入SSH密码即可完成安装。
我已经查阅过Stack Overflow上相关问题中适用于GitLab等平台的解决方案，也参考了对应的补充说明，但仍未解决问题。
我已经在本地Mac设备和当前BitBucket账号之间配置了SSH密钥，日常向该账号仓库推送、拉取代码时均无需重复输入SSH密码。为什么git命令可正常免密，执行pip install命令时却要求输入密码？基于我当前的配置，在BitBucket场景下是否有可行的规避方案？

问题更新 #

我按照评论推荐的方法执行GIT_SSH_COMMAND='ssh -vvv' pip install git+ssh://git@bitbucket.org/my_org/my_package_repo.git命令，得到如下脱敏后的返回结果：

Collecting git+ssh://git@bitbucket.org/my_org/my_package_repo.git
  Cloning ssh://git@bitbucket.org/my_org/my_package_repo.git to /private/var/folders/hh/v8z4pvkn3kl14c9ty827578c0000gq/T/pip-req-build-i9q_8b83
  Running command git clone -q ssh://git@bitbucket.org/my_org/my_package_repo.git /private/var/folders/hh/v8z4pvkn3kl14c9ty827578c0000gq/T/pip-req-build-i9q_8b83
  OpenSSH_8.1p1, LibreSSL 2.7.3
  debug1: Reading configuration data /Users/username/.ssh/config
  debug1: /Users/username/.ssh/config line 1: Applying options for *
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 47: Applying options for *
  debug1: Connecting to bitbucket.org port 22.
  debug1: Connection established.
  debug1: identity file /Users/username/.ssh/id_rsa type 0
  debug1: identity file /Users/username/.ssh/id_rsa-cert type -1
  debug1: identity file /Users/username/.ssh/id_dsa type -1
  debug1: identity file /Users/username/.ssh/id_dsa-cert type -1
  debug1: identity file /Users/username/.ssh/id_ecdsa type -1
  debug1: identity file /Users/username/.ssh/id_ecdsa-cert type -1
  debug1: identity file /Users/username/.ssh/id_ed25519 type -1
  debug1: identity file /Users/username/.ssh/id_ed25519-cert type -1
  debug1: identity file /Users/username/.ssh/id_xmss type -1
  debug1: identity file /Users/username/.ssh/id_xmss-cert type -1
  debug1: Local version string SSH-2.0-OpenSSH_8.1
  debug1: Remote protocol version 2.0, remote software version conker_a7531beec7 c7d1b850e369
  debug1: no match: conker_a7531beec7 c7d1b850e369
  debug3: fd 7 is O_NONBLOCK
  debug1: Authenticating to bitbucket.org:22 as 'git'
  debug3: hostkeys_foreach: reading file "/Users/username/.ssh/known_hosts"
  debug3: record_hostkey: found key type RSA in file /Users/username/.ssh/known_hosts:3
  debug3: load_hostkeys: loaded 1 keys from bitbucket.org
  debug3: order_hostkeyalgs: prefer hostkeyalgs: rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa
  debug3: send packet: type 20
  debug1: SSH2_MSG_KEXINIT sent
  debug3: receive packet: type 20
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c
  debug2: host key algorithms: rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519
  debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
  debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
  debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
  debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
  debug2: compression ctos: none,zlib@openssh.com,zlib
  debug2: compression stoc: none,zlib@openssh.com,zlib
  debug2: languages ctos:
  debug2: languages stoc:
  debug2: first_kex_follows 0
  debug2: reserved 0
  debug2: peer server KEXINIT proposal
  debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,ext-info-s
  debug2: host key algorithms: ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss
  debug2: ciphers ctos: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,chacha20-poly1305@openssh.com
  debug2: ciphers stoc: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,chacha20-poly1305@openssh.com
  debug2: MACs ctos: hmac-sha2-256-etm@openssh.com,hmac-sha2-256,hmac-sha1,hmac-sha1-96
  debug2: MACs stoc: hmac-sha2-256-etm@openssh.com,hmac-sha2-256,hmac-sha1,hmac-sha1-96
  debug2: compression ctos: none
  debug2: compression stoc: none
  debug2: languages ctos:
  debug2: languages stoc:
  debug2: first_kex_follows 0
  debug2: reserved 0
  debug1: kex: algorithm: curve25519-sha256@libssh.org
  debug1: kex: host key algorithm: rsa-sha2-512
  debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
  debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
  debug3: send packet: type 30
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug3: receive packet: type 31
  debug1: Server host key: ssh-rsa SHA256:serverhostkeyzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
  debug3: hostkeys_foreach: reading file "/Users/username/.ssh/known_hosts"
  debug3: record_hostkey: found key type RSA in file /Users/username/.ssh/known_hosts:3
  debug3: load_hostkeys: loaded 1 keys from bitbucket.org
  debug3: hostkeys_foreach: reading file "/Users/username/.ssh/known_hosts"
  debug3: record_hostkey: found key type RSA in file /Users/username/.ssh/known_hosts:11
  debug3: load_hostkeys: loaded 1 keys from 104.192.141.1
  debug1: Host 'bitbucket.org' is known and matches the RSA host key.
  debug1: Found key in /Users/username/.ssh/known_hosts:3
  debug3: send packet: type 21
  debug2: set_newkeys: mode 1
  debug1: rekey out after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug3: receive packet: type 21
  debug1: SSH2_MSG_NEWKEYS received
  debug2: set_newkeys: mode 0
  debug1: rekey in after 134217728 blocks
  debug1: Will attempt key: /Users/username/.ssh/id_rsa RSA SHA256:rsasha256zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
  debug1: Will attempt key: /Users/username/.ssh/id_dsa
  debug1: Will attempt key: /Users/username/.ssh/id_ecdsa
  debug1: Will attempt key: /Users/username/.ssh/id_ed25519
  debug1: Will attempt key: /Users/username/.ssh/id_xmss
  debug2: pubkey_prepare: done
  debug3: send packet: type 5
  debug3: receive packet: type 7
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: server-sig-algs=<ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp521,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com>
  debug3: receive packet: type 6
  debug2: service_accept: ssh-userauth
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug3: send packet: type 50
  debug3: receive packet: type 51
  debug1: Authentications that can continue: publickey
  debug3: start over, passed a different list publickey
  debug3: preferred publickey,keyboard-interactive,password
  debug3: authmethod_lookup publickey
  debug3: remaining preferred: keyboard-interactive,password
  debug3: authmethod_is_enabled publickey
  debug1: Next authentication method: publickey
  debug1: Offering public key: /Users/username/.ssh/id_rsa RSA SHA256:rsasha256zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
  debug3: send packet: type 50
  debug2: we sent a publickey packet, wait for reply
  debug3: receive packet: type 60
  debug1: Server accepts key: /Users/username/.ssh/id_rsa RSA SHA256:rsasha256zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
  debug3: sign_and_send_pubkey: RSA SHA256:rsasha256zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
  debug3: sign_and_send_pubkey: signing using rsa-sha2-512
Enter passphrase for key '/Users/username/.ssh/id_rsa':

从debug日志可以直接定位问题根源：你的SSH私钥本身设置了密码保护，平时使用git命令时不需要输入密码，是因为系统ssh-agent已经缓存了私钥的解锁密码；而pip在执行克隆操作时，运行的是独立的子进程环境，没有继承当前shell的ssh-agent会话，所以会重新要求输入私钥密码。

有三种可直接落地的方案，按需选择即可：

方案1：临时关联当前ssh-agent #

确认ssh-agent已经在运行且缓存了私钥密码后，执行安装命令时传递ssh-agent的socket路径即可，重启终端后失效：

SSH_AUTH_SOCK=$SSH_AUTH_SOCK pip install git+ssh://git@bitbucket.org/my_org/my_package_repo.git

方案2：修改SSH配置永久生效 #

编辑~/.ssh/config文件，添加如下配置，Mac系统会自动在钥匙串中存储你的私钥密码，所有进程（包括pip触发的ssh会话）都可以直接读取已解锁的私钥：

Host bitbucket.org
  HostName bitbucket.org
  User git
  IdentityFile ~/.ssh/id_rsa
  UseKeychain yes
  AddKeysToAgent yes

方案3：使用HTTPS+应用密码安装，无需调整SSH配置 #

在BitBucket账号后台生成仓库只读应用密码，直接用HTTPS路径安装即可：

pip install git+https://<你的BitBucket用户名>:<生成的应用密码>@bitbucket.org/my_org/my_package_repo.git

内容的提问来源于stack exchange，提问作者Jed