Even for existing users, at some point sticking with Python 2 can start to become a liability as some new libraries are released in Python 3 only or existing libraries migrate to Python 3 only. I use rpy2, which is an interface between Python and R, and the latest development branch has dropped support for Python 2 altogether. At some point, we'll need Python 3 support in order to be able to continue to take advantage of the Python ecosystem. That time is still a ways off, and perhaps we'll have web3py by then, but something to consider.
Anthony On Thursday, June 6, 2013 3:50:57 PM UTC-4, Michael Lutynski wrote: > > That's not true for me. I have been fascinated with web2py for the longest > time, and now I'm finally able to use it, I was sincerely hoping that there > would be a Python 3 option. But since I do not know anything about web2py > at all at this point, it makes it a daunting proposition to consider > helping to port it. > > It seems that for existing web2py users, there might not be the much > incentive to help porting it because of the investment with Python 2.x, but > that's not true for newcomers who will want Python 3, like me. > > On Saturday, 13 April 2013 10:48:17 UTC-7, Massimo Di Pierro wrote: >> >> Nobody helped with it. That shows how much interest there is here about >> Python 3.x. > > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
