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
{{ message }}
Repository navigation
TypeError: __init__() got an unexpected keyword argument 'pkey' #82
The previous ticket suggests to use a particular version of dulwich but surely this should just work ootb?
File "/Users/sadams/Workspace/sales-engineering-demo-server/admin/apps.py", line 20, in ready
Gittle.clone(settings.GIT_DEMO_REPO_URL, settings.GIT_DEMO_REPO_DIR, auth=auth)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/gittle/gittle.py", line 440, in clone
repo.fetch(bare=bare)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/gittle/gittle.py", line 407, in fetch
remote_refs = self.fetch_remote(origin_uri)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/gittle/gittle.py", line 364, in fetch_remote
client, remote_path = self.get_client(origin_uri=origin_uri)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/gittle/gittle.py", line 328, in get_client
client, remote_path = get_transport_and_path(origin_uri, **client_kwargs)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/dulwich/client.py", line 1197, in get_transport_and_path
return SSHGitClient(host, username=user, **kwargs), path
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/dulwich/client.py", line 921, in __init__
TraditionalGitClient.__init__(self, **kwargs)
TypeError: __init__() got an unexpected keyword argument 'pkey'
Activity
jelmer commentedon Jul 7, 2016
Dulwich should work out of the box, although upstream dulwich doesn't support the pkey argument that gittle is specifying.
jelmer commentedon Jul 7, 2016
By default, dulwich doesn't use paramiko but standard ssh in which case 2fa should just work.
menge101 commentedon Jul 21, 2017
I just hit this as well, so it is still an issue, a year later.