CARVIEW

MOTORHOMES

Select Language

HTTP/2 302 server: nginx date: Sun, 27 Jul 2025 16:40:44 GMT content-type: text/plain; charset=utf-8 content-length: 0 x-archive-redirect-reason: found capture at 20100316231840 location: https://web.archive.org/web/20100316231840/https://github.com/joshthecoder/tweepy/issues server-timing: captures_list;dur=0.636585, exclusion.robots;dur=0.021260, exclusion.robots.policy;dur=0.009721, esindex;dur=0.013830, cdx.remote;dur=202.007558, LoadShardBlock;dur=333.437793, PetaboxLoader3.datanode;dur=75.014761, PetaboxLoader3.resolve;dur=156.185759 x-app-server: wwwb-app224 x-ts: 302 x-tr: 562 server-timing: TR;dur=0,Tw;dur=0,Tc;dur=0 set-cookie: SERVER=wwwb-app224; path=/ x-location: All x-rl: 0 x-na: 0 x-page-cache: MISS server-timing: MISS x-nid: DigitalOcean referrer-policy: no-referrer-when-downgrade permissions-policy: interest-cohort=() HTTP/2 200 server: nginx date: Sun, 27 Jul 2025 16:40:48 GMT content-type: text/html; charset=utf-8 x-archive-orig-server: nginx/0.7.61 x-archive-orig-date: Tue, 16 Mar 2010 23:18:38 GMT x-archive-orig-connection: close x-archive-orig-status: 200 OK x-archive-orig-etag: "d5607b036bd53376fd8f7f3066b3da22" x-archive-orig-x-runtime: 209ms x-archive-orig-content-length: 44061 x-archive-orig-cache-control: private, max-age=0, must-revalidate x-archive-guessed-content-type: text/html x-archive-guessed-charset: utf-8 memento-datetime: Tue, 16 Mar 2010 23:18:40 GMT link: ; rel="original", ; rel="timemap"; type="application/link-format", ; rel="timegate", ; rel="first memento"; datetime="Sat, 29 Aug 2009 11:18:26 GMT", ; rel="prev memento"; datetime="Sat, 13 Feb 2010 06:04:51 GMT", ; rel="memento"; datetime="Tue, 16 Mar 2010 23:18:40 GMT", ; rel="next memento"; datetime="Thu, 12 Jul 2012 21:49:54 GMT", ; rel="last memento"; datetime="Sat, 26 Apr 2025 06:11:34 GMT" content-security-policy: default-src 'self' 'unsafe-eval' 'unsafe-inline' data: blob: archive.org web.archive.org web-static.archive.org wayback-api.archive.org athena.archive.org analytics.archive.org pragma.archivelab.org wwwb-events.archive.org x-archive-src: 51_14_20100316202444_crawl100-c/51_14_20100316231516_crawl101.arc.gz server-timing: captures_list;dur=0.517819, exclusion.robots;dur=0.017900, exclusion.robots.policy;dur=0.008048, esindex;dur=0.011049, cdx.remote;dur=3088.868601, LoadShardBlock;dur=544.061590, PetaboxLoader3.datanode;dur=497.212544, PetaboxLoader3.resolve;dur=258.059075, load_resource;dur=329.321736 x-app-server: wwwb-app224 x-ts: 200 x-tr: 4033 server-timing: TR;dur=0,Tw;dur=0,Tc;dur=0 x-location: All x-rl: 0 x-na: 0 x-page-cache: MISS server-timing: MISS x-nid: DigitalOcean referrer-policy: no-referrer-when-downgrade permissions-policy: interest-cohort=() content-encoding: gzip Issues - joshthecoder/tweepy - GitHub

joshthecoder / tweepy

Sort By: Priority | Votes | Last Updated

Loading…

5.

0 votes

Feature Request
x

allow tweepy requests to use a proxy
2 comments Created 4 months ago by brianmichelich

Here's a changeset with one approach:
https://github.com/brianmichelich/tweepy/commit/5cd1b3d1ce5d760e6c4e08af353c4c1ce406b475

This allows you to set a proxy_host and proxy_port on the API() and have binder.py pick them up when creating a connection.

Comments

joshthecoder Fri Oct 23 19:38:41 -0700 2009 | link

We can already provide a proxy host via the "host" parameter in the API init method.
There is not a way to provide a port though which could be easily added. I will look into providing this in the next release. Thanks!

Comment
We can already provide a proxy host via the "host" parameter in the API init method. There is not a way to provide a port though which could be easily added. I will look into providing this in the next release. Thanks!
or cancel

brianmichelich Sat Oct 24 08:48:37 -0700 2009 | link

Unless I missed something a changed host parameter would allow for a reverse proxy and I was setting up a forward proxy.
The reverse proxy worked when I sent the request to foo.com and forwarded to twitter.com. Setting a hosts on the connection as well as the request allowed the forward proxy to work. This allowed me to use a forward proxy without setting it for the python environment.

Comment
Unless I missed something a changed host parameter would allow for a reverse proxy and I was setting up a forward proxy. The reverse proxy worked when I sent the request to foo.com and forwarded to twitter.com. Setting a hosts on the connection as well as the request allowed the forward proxy to work. This allowed me to use a forward proxy without setting it for the python environment.
or cancel

Please log in to comment.
14.

0 votes

Bug
x

all exceptions are caught in Stream._run, even listener exceptions
0 comments Created 28 days ago by athoune

If you made a mistake in your StreamListener implementation (when a str become an unicode), Stream._run will hide this exception. The application stop silently.

Comments

Please log in to comment.
15.

0 votes

Maybe Bug
x

'module' object has no attribute 'OAuthHandler'
0 comments Created 26 days ago by Swizec

when installing the latest tweepy (1.5 I think) with "python setup.py install" the error that OAuthHandler does not exist keeps popping up.

This seems to be resolved if you simply copy the dist/tweepy directory into dist-packages, which seems to indicate something goes wrong with install.

Comments

Please log in to comment.
18.

0 votes

Maybe Bug
x

streaming.py crash
0 comments Created 15 days ago by scardig
Downloaded streamwatcher.py from tweepy-examples. Sometimes, after a day of running, it crashes with the following (I commented out lines 117->119 in stremaing.py to catch the exception):

Traceback (most recent call last):
File "webapps/siti/mex/scripts/mystreamwatcher.py", line 68, in
```
myfunc()
```
File "webapps/siti/mex/scripts/mystreamwatcher.py", line 63, in myfunc
```
stream.filter(followed)
```
File "/home/user/webapps/siti/mex/scripts/tweepy/streaming.py", line 195, in filter
```
self._start(async)
```
File "/home/user/webapps/siti/mex/scripts/tweepy/streaming.py", line 160, in _start
```
self._run()
```
File "/home/user/webapps/siti/mex/scripts/tweepy/streaming.py", line 111, in _run
```
self._read_loop(resp)
```
File "/home/user/webapps/siti/mex/scripts/tweepy/streaming.py", line 140, in _read_loop
```
c = resp.read(1)
```
File "/usr/local/lib/python2.6/httplib.py", line 517, in read
```
return self._read_chunked(amt)
```
File "/usr/local/lib/python2.6/httplib.py", line 563, in _read_chunked
```
raise IncompleteRead(value)
```
httplib.IncompleteRead
Comments

Please log in to comment.

20.

0 votes

Maybe Bug
x

UnicodeEncodeError constructing TweepError

0 comments Created 11 days ago by treelinelabs

24.

0 votes

Maybe Bug
x

Patch in access to the OAuth rate limit status
4 comments Created 3 days ago by BonsaiDen
Since the limit for OAuth requests is currently at 350 per hour and authenticated requests don't count against the normal rate_limit_status api, there should be a way to access the OAuth limit.

The information gets send with the header of every response on an authenticated call:
x-ratelimit-class = "api_identified"
x-ratelimit-limit = The current maximum of request per hour.
x-ratelimit-remaining = The requests remaining till the reset.
x-ratelimit-reset = UNIX timestamp as seconds when the next reset will occur.

I already patched this into api.py and binder.py:
https://github.com/BonsaiDen/tweepy/commit/cf0b4068e3e882498619d897d51462de91ca7e4e

May need some changes to the variable names, but besides that it should be OK I guess.

Comments
joshthecoder Fri Mar 12 16:49:23 -0800 2010 | link

Is OAuth rate limit still incorrect for the rate_limit_status api call?

According to this issue it is "fixed": https://code.google.com/p/twitter-api/issues/detail?id=1501

Comment
Is OAuth rate limit still incorrect for the rate_limit_status api call? According to this issue it is "fixed": https://code.google.com/p/twitter-api/issues/detail?id=1501
or cancel
BonsaiDen Fri Mar 12 16:56:44 -0800 2010 | link
Hm ok seems to be fixed now, wasn't when I checked last time.

But anyways, I think saving the information from the header might still be good, since this doesn't require an extra request, it's available immediately(which cuts down startup time in my application).

So I guess the whole thing could be refactored into something like:

def rate_limit_status(self):
if self.last_rate_limit_status == None:

# make api call

else:

# return the information that came with the last request
Comment
Hm ok seems to be fixed now, wasn't when I checked last time. But anyways, I think saving the information from the header might still be good, since this doesn't require an extra request, it's available immediately(which cuts down startup time in my application). So I guess the whole thing could be refactored into something like: def rate_limit_status(self): if self.last_rate_limit_status == None: # make api call else: # return the information that came with the last request
or cancel
BonsaiDen Fri Mar 12 17:22:34 -0800 2010 | link

Patch here:
https://github.com/BonsaiDen/tweepy/commit/3fa304e2ba662ae46ecea3fe34069d240b66458d

Comment
Patch here: https://github.com/BonsaiDen/tweepy/commit/3fa304e2ba662ae46ecea3fe34069d240b66458d
or cancel

BonsaiDen Fri Mar 12 17:28:24 -0800 2010 | link

Oh and in the case that you merge it, make sure to check out the latest commit, since my editor kinda screwed up with the whitespace in the one above.

Comment
Oh and in the case that you merge it, make sure to check out the latest commit, since my editor kinda screwed up with the whitespace in the one above.
or cancel

Please log in to comment.