Mike,

On Oct 2, 2009, at 9:42 PM, Mike Markley wrote:
> On Oct 2, 11:47 am, Tim Stewart <[email protected]> wrote:
>> On Oct 2, 2009, at 2:32 PM, Mike Markley wrote:
>>
>>> I've applied the patch above to the latest git source, but I'm also
>>> getting a password failure. I had yahoo.py print out all the  
>>> arguments
>>> it passes to ylib.YahooCon(), and the password getting passed in is
>>> correct.
>>
>> I'm not absolutely positively sure that this patch applies cleanly
>> against the latest Git source since I was working from the CVS repo  
>> at
>> the time.  I'll be patching against Git (and pushing that patch up to
>> the main tree, thanks Norman), and I'll send out a mail when I've  
>> done
>> that and you can try the latest version from GitHub at that time.
>
> False alarm. Since I had issues with 0.4, I first ran patch with -- 
> dry-
> run... and then forgot to run it without, like a genius. *slaps
> forehead* The git version without the protocol 16 patch fails to
> connect in a different way than 0.4 does, further confusing the
> existing keyboard actuator error...

So, the verdict is that you're able to log in now?

I know I had some initial trouble because I was logging in and out a  
bunch and Yahoo ended up locking my account for a while :)  Oddly  
enough I could still log in via the web interface even though the  
transport and the official Yahoo client were giving me password  
errors.  Interestingly, the errors I look for in the transport are  
more descriptive than the official client, which has a single catch- 
all "login failure" message.

-- 
-TimS

Tim Stewart
Stoo Research
[email protected]






--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"py-transports" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/py-transports?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to