Your message dated Sat, 3 Dec 2016 15:30:05 +0000
with message-id <[email protected]>
and subject line Fixed previously, bug missed
has caused the Debian Bug report #808983,
regarding AttributeError: 'str' object has no attribute 'decode'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
808983: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808983
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3-requests-oauthlib
Version: 0.4.0-1
Severity: important
Tags: upstream fixed-upstream patch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Trying to use `retweet', I get the following error:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/tweepy/binder.py", line 187, in execute
proxies=self.api.proxy)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 454, in
request
prep = self.prepare_request(req)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 388, in
prepare_request
hooks=merge_hooks(request.hooks, self.hooks),
File "/usr/lib/python3/dist-packages/requests/models.py", line 297, in prepare
self.prepare_auth(auth, url)
File "/usr/lib/python3/dist-packages/requests/models.py", line 487, in
prepare_auth
r = auth(self)
File "/usr/lib/python3/dist-packages/requests_oauthlib/oauth1_auth.py", line
70, in __call__
r.url = to_native_str(r.url)
File "/usr/lib/python3/dist-packages/requests_oauthlib/oauth1_auth.py", line
14, in to_native_str
return string.decode('utf-8')
AttributeError: 'str' object has no attribute 'decode'
This seems to be fixed upstream in commit
9aa95160fa23443aea81b7c57db26522ad65f303.
I guess updating the whole package to a new upstream release would be
a good idea, there seem to be more fixes and enhancements in newer
version.
Cheers,
gregor
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQJ8BAEBCgBmBQJWfXNYXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGBKgQAIvbcyWLAt+CKTrF5FAqhuG9
2RLSjq3rqKAptI0FA9jvujy2tFNpCZlUWyaBHuNT0c/xGljw2HQgiHEXWpTGuGni
xPNIG7xFSQ/s1Kw5LvfrtPeqIdN+Zn4upjiRvOuyCGRhtWfeRBJu+jE5Kj9HYQls
1wLVagJGkIhFzKfoN5yQJiASZUScGIhIx3Gwg6jg/0nS75xlpEkGGwMVb/wmfLXx
NEjYvNv5VESblBoXcPGbR4/vnb+uUMJATfpStKMtsqA6+5NwLL3AEyHLgjgUtFae
Z/4l0IwH/gXBFmLGCC/NL2pecPRFWk6J17jetYhB3u6kRakSepqDz+sq+qoJnKFt
2MkyvLZU+aDE74LtLl4daBtdDRqfXHNSZuRmHE8jPHV812kf79cScwKBAllnHzlg
FBVtwdJLh+nBELLm1OWG1G0qFQGtgjprzJ4/oG4/aJsZG99uSeeJjwOh27nJus0V
5qw75DoWfnQR6svi19ItGCe1f/GzOyBMrLhWeP5Fh+UjDuxtfZPxO1iwlzJy5uVD
YoQSz+G4YNKIyUJNZMKyjAQMtE8QEklQFAjaQyX2bRPbII+RLwqrQI5e0U7oiqlB
O3VKZfxJWrDI8aS0qZUJ2qzVOTI8Oq6yUwUmFVW+6O0uQs2SxKgD5LGfVgo1Hi7Q
LxkLocRNf33ULMFzC/d8
=QHDa
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Fixed: 0.6.2-0.1
Hi,
This was fixed when I NMU'd a new upstream version. I completely missed the
bug, closing it now.
Thanks,
Iain.
signature.asc
Description: PGP signature
--- End Message ---
