|
|
2010-06-01
, 15:45
|
|
Posts: 1,667 |
Thanked: 561 times |
Joined on Feb 2010
|
#461
|
|
|
2010-06-01
, 15:47
|
|
Posts: 21 |
Thanked: 0 times |
Joined on May 2010
@ London
|
#462
|
|
|
2010-06-01
, 16:36
|
|
|
Posts: 529 |
Thanked: 262 times |
Joined on Dec 2008
@ Eastleigh, Hampshire, UK
|
#463
|
|
|
2010-06-01
, 16:40
|
|
|
Posts: 529 |
Thanked: 262 times |
Joined on Dec 2008
@ Eastleigh, Hampshire, UK
|
#464
|
Opened Twitter.com, no network issues now.
Ran witter from command line. Timeline was empty, refreshed and got rerror: Error retreiving tweets Server returning 400
Version 0.3.3-9
Using oAuth Should I be ?
|
|
2010-06-01
, 17:30
|
|
Posts: 1,667 |
Thanked: 561 times |
Joined on Feb 2010
|
#465
|
which update? 0.3.3-9?
did you delete:
/home/user/.wittertl
/home/user/.wittermon
/home/user/.witterdm
?
|
|
2010-06-01
, 17:56
|
|
Posts: 1,667 |
Thanked: 561 times |
Joined on Feb 2010
|
#466
|
missing option in config
no service setting
No stored ids from last run
No more users to load
Establishing api for Twitter using basic auth
Establishing api for Twitter using oauth
Connection working ok
Traceback (most recent call last):
File "/opt/witter/witter.py", line 1148, in <module>
app = Witter()
File "/opt/witter/witter.py", line 169, in __init__
self.activeAccount.tweetstore = self.reload_timeline_data('/home/user/.wittertl',self.activeAccount.getTimeline())
File "/opt/witter/witter.py", line 615, in reload_timeline_data
config.readfp(open(file))
File "/usr/lib/python2.5/ConfigParser.py", line 286, in readfp
self._read(fp, filename)
File "/usr/lib/python2.5/ConfigParser.py", line 490, in _read
raise e
ConfigParser.ParsingError: File contains parsing errors: /home/user/.wittertl
|
|
2010-06-01
, 19:19
|
|
|
Posts: 103 |
Thanked: 20 times |
Joined on Jan 2008
|
#467
|
|
|
2010-06-01
, 19:30
|
|
Posts: 1,667 |
Thanked: 561 times |
Joined on Feb 2010
|
#468
|
|
|
2010-06-01
, 19:40
|
|
|
Posts: 529 |
Thanked: 262 times |
Joined on Dec 2008
@ Eastleigh, Hampshire, UK
|
#469
|
| The Following User Says Thank You to dwould For This Useful Post: | ||
|
|
2010-06-01
, 19:44
|
|
Posts: 1,667 |
Thanked: 561 times |
Joined on Feb 2010
|
#470
|
:-) in xterm:
rm /home/user/.wittertl
rm /home/user/.wittermon
rm /home/user/.witterdm
basically in 0.3.3-8 the code which persisted tweets to disc didn't check for newline characters in tweets, and wrote them anyway. But the code to load the files didn't cope with newlines in the format.
this is fixed in 0.3.3-9, however the files need to be cleaned of the bad format.
This is why it effected some people and not others, basically it was only if there was a newline in a tweet in the last 20 when you quit, that it would have problems on the next load.
just one of those perils of playing in extras-devel
assuming no other problems with 0.3.3-9, I may promote it to testing.
![]() |
| Tags |
| python, twitter |
| Thread Tools | |
|