You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The game uses marshal to serialize and deserialize remote procedure calls across the network, which isn't completely reliable according to this. It shouldn't be a huge issue now with 2.7 being really the highest anyone can run this on right now and everyone should have just about 2.7 running on any modern machine, but we shouldn't be operating under these assumptions as it could also differ between Python implementations as well.
The text was updated successfully, but these errors were encountered:
I think that this is something to keep an eye on, but not necessarily something we need to fix. Right now using Python 2.6 for the server (Cent6) and Python 2.7 for the client (packaged with or at least the shebang specifies python2 (which is valid even in legacy systems that only ship Python2) things seem to work -- the code is definitely not Python3 clean. Could someone give me a more detailed risk estimate regarding this?
The game uses marshal to serialize and deserialize remote procedure calls across the network, which isn't completely reliable according to this. It shouldn't be a huge issue now with 2.7 being really the highest anyone can run this on right now and everyone should have just about 2.7 running on any modern machine, but we shouldn't be operating under these assumptions as it could also differ between Python implementations as well.
The text was updated successfully, but these errors were encountered: