| Time |
Nickname |
Message |
|
06:19
🔗
|
yipdw |
hmm |
|
06:20
🔗
|
yipdw |
if we want to put Seesaw on Python 3, it looks like the web component will have to be pretty much entirely rewritten |
|
06:20
🔗
|
yipdw |
socket.io has its own un-websockets-like protocol and there appears to be no Python 3-ready socket.io library that integrates well with Tornado |
|
06:21
🔗
|
yipdw |
luckily, most of Seesaw's Web code is of the form connection.on(EVENT, function(DATA) { ... }) |
|
06:21
🔗
|
yipdw |
I'll see how it goes getting Seesaw to use SockJS, which looks like it's in more for the long term |
|
06:22
🔗
|
yipdw |
unless people here just want to say "fuck it" and go straight to websockets |
|
06:22
🔗
|
yipdw |
(the main reason to use SockJS is to support browsers that don't do whatever flavor of websockets is popular right now) |
|
06:23
🔗
|
yipdw |
the benefit of dropping that compatibility layer is that we can drop a seesaw dependency and just write using tornado's websocket library |
|
06:23
🔗
|
yipdw |
opinions? |
|
06:23
🔗
|
yipdw |
alternatively, we can create a seesaw-sans-web package |
|
06:23
🔗
|
yipdw |
I think everything else runs on Python 3 just fine |
|
06:26
🔗
|
yipdw |
the main reason I'm concerned about Python 3 support is that chfoo's wpull currently works best with Python 3, and we're looking into getting wpull + archivebot working |
|
06:27
🔗
|
yipdw |
it would be nice to just be able to use Python 3 all the way |
|
06:27
🔗
|
yipdw |
archivebot doesn't use the web interface, so seesaw-sans-web is an option to satisfy that specific need |
|
10:45
🔗
|
ersi |
yipdw: It would indeed be neat to be on Py3 |