• Welcome to the new COTI server. We've moved the Citizens to a new server. Please let us know in the COTI Website issue forum if you find any problems.
  • We, the systems administration staff, apologize for this unexpected outage of the boards. We have resolved the root cause of the problem and there should be no further disruptions.

StaBase ongoign development

It's written in Python 2.7 so it's not Python 3 compatible I'm afraid. The page linked in my Sig explains what you need to get a Dev environment up and running. I'm happy to answer any further questions on it though.

Simon

How much work do you think it might be to convert it? Is it missing a bunch of imports that were never converted to 3.x or is it more syntax?
 
How much work do you think it might be to convert it? Is it missing a bunch of imports that were never converted to 3.x or is it more syntax?

I think it's mostly syntax, with the biggest issue being string handling. All strings in 3.x are a native Unicode type while in 2.x they are really just byte arrays. It would involve refactoring the code everywhere I use strings, which is all over the place. There are also a few modules like CSV that have some differences. I think all the external modules I use should have 3.x versions by now. I don't use anything truly obscure (just checked this, NetworkX, Pyside and Py2exe have 3.x versions so it should be fine).

To be honest, because I've never coded in 3.x I'm not familiar with the differences. I can only really guess from what I've read.

If you're up for it, you're welcome to have a go. A project like that would mean going through pretty much the whole code base so it would be a great way to get familiar with it. Also if anyone else is prepared to put any time into it, I'll happily throw my own time in as well. I'll even commit to doing all future development (if any, I have to say) in the 3.x branch.

Simon Hibbs
 
I think it's mostly syntax, with the biggest issue being string handling. All strings in 3.x are a native Unicode type while in 2.x they are really just byte arrays. It would involve refactoring the code everywhere I use strings, which is all over the place. There are also a few modules like CSV that have some differences. I think all the external modules I use should have 3.x versions by now. I don't use anything truly obscure (just checked this, NetworkX, Pyside and Py2exe have 3.x versions so it should be fine).

To be honest, because I've never coded in 3.x I'm not familiar with the differences. I can only really guess from what I've read.

If you're up for it, you're welcome to have a go. A project like that would mean going through pretty much the whole code base so it would be a great way to get familiar with it. Also if anyone else is prepared to put any time into it, I'll happily throw my own time in as well. I'll even commit to doing all future development (if any, I have to say) in the 3.x branch.

Simon Hibbs

While I won't officially sign off on the project yet, I will load the code into a 2.7 environment and see what might be involved. I started in Python in 3.x so I have no idea what I am up against.
 
While I won't officially sign off on the project yet, I will load the code into a 2.7 environment and see what might be involved. I started in Python in 3.x so I have no idea what I am up against.

Sue, if you want to do a Skype or hangout to go through any of it just let me know. I'm simonhibbs on Skype. My Google ID is my fistname.lastname at gmail dot com.

Simon Hibbs
 
Back
Top