#twisted

You guys are starting to tempt me to move to Python3 with Twisted with all that async-def coroutine support

nanonyme: can you link to what you're referring to

LindsayLojban, don't you see the https://tm.tl/#8849 above?

nanonyme: yes, in a sea of parts and joins and other noise

LindsayLojban, I'm using Weechat, it filters irrelevant parts and joins out

I'm using weechat, it doesn't.

It retroactively injects ones from people who actually speak

You probably haven't turned it on then

LindsayLojban, try /set *smart_filter*

Finding that really changed my life, now channel size really plays zero effect in usability

hi

I have gtk echo client, for example when I lose connection I try to reconnect, but It open a second window, it does not stay on the same

is there a possiblity to check ins

Okay, looks improbable the IRC port to Python3 will happen

Guess I'll be sticking with Python2 then

twisted's IRC support is the only reason why I'm still using Python2

nanonyme: Why do you say improbable?

tomprince, too unicode-orientated

nanonyme: All it would take is for someone to step up and do the work.

I was mainly looking at the pull requests and patches

Imo with IRC you want to decode at the last minute IOW when you have already resolved command and are going to send it somewhere, not as the first thing

Anything else will not allow the implementation to properly handle the clutterf* that IRC actually is with regards to encodings

Best case would be to be able to assign different encodings to decode with per user

But that would probably be overkill

Per-channel would imo still be appropriate though (which means most of the protocol implementation needs to happen with bytestrings)