pylacewing - Lacewing for Python

[DizzyDoo]

I'll look into the ServerProtocol.leaveChannel issue

Great.

I'm quite sure acceptChannelLeave is fired, so are you sure it's not a bug with your code? acceptChannelLeave is not checked if the ServerProtocol.leaveChannel method is called directly (eg. only if the request comes from the client itself), so perhaps that's it?

You're right, it works fine. I was expecting it to be called when the connection fails (after all, channelLeft() is called). Of course, this is silly, the server can hardly say "Nope, you cannot leave the channel" if someones just powered off their computer. :P

channelListSent and acceptChannelListRequest should be working too. Are you sure ServerFactory.channelListing is set to True?

Hahaha, yeah, it was indeed set to false. I wasn't even aware there was such a variable existing.

Thanks, I look forward to the leave channel issue being sorted out.

[Mathias]

Jamie found a rather tricky bug today, so pylacewing 0.2.15 has been released! Will be up on Villy's server in a moment or so.

[Mathias]

pylacewing 0.2.3 has been released, and it is now compatible with Lacewing build 13. I will update aquadasoft.com in a few moments, hang on!

[Mathias]

Quick bugfix, 0.2.31 has been released.

[Mathias]

Another bugfix, 0.2.32 released!

[LeoLamas]

I get a 'server error' from google everytime i try to access the site :/

[Mathias]

Well, it's definitely fixed now

[Mathias]

0.2.4 has been released, and fixes pinging (this means that "dead" connections are automatically kicked now).

[Hernan]

Hi Mathias, thanks for the update. Lately I'm having problems with random disconnects. The error lacewing returns is "Connection denied. Not denied". Unfortunalety nearly impossible to reproduce, because it happens so randomly.
Could this error be related to when you're disconnected due to not responding to ping in time?
I'm using the newest versions for server and client.

[Mathias]

Hnm, might sound like it. I'll dig a bit around to see if I can find the cause