Drop python 2.6

[Leonel Câmara]

Can we please drop it? Even GAE is using python 2.7 nowadays.

I got the idea that, since I'm making tests, after having a good enough coverage on a module I could then make sure the tests also pass on Python 3, but frankly it's too painful to support both python 2.6 and python 3, especially because I don't even have Python 2.6 installed.  

This could be a way for us to slowly move towards supporting python 3.  

[Paolo Valleri]

+1if it makes web2py closer to py3

--
-- mail from:GoogleGroups "web2py-developers" mailing list
make speech: web2py-d...@googlegroups.com
unsubscribe: web2py-develop...@googlegroups.com
details : http://groups.google.com/group/web2py-developers
the project: http://code.google.com/p/web2py/
official : http://www.web2py.com/
---
You received this message because you are subscribed to the Google Groups "web2py-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web2py-develop...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Massimo DiPierro]

yes. we should drop python 2.6 support. But not in the next release. In the one after.

Massimo

[Nico Zanferrari]

I'm not a developer, but I like a lot this decision. Since testing, supporting Python 3.0  and cleanup are top priorities it goes in the right direction!

For the sake of clarity, you could label next version as 2.6.x - where only security patches will be officially backported. And then let's start working on 2.7 !

[LightDot]

The bluntly honest "especially because I don't even have Python 2.6 installed" remark really made me laugh, in a good way. I'm sooo tempted to come up with a sarcastic remark or two about the enterprise aspects of web2py...

Once this move is decided, I suggest posting it prominently on the user's list well in advance.

There are some of us who... well, let's put it this way, RHEL/CentOS/SL 6 just won't die. Anyway, I'll push things to RHEL 7 or 8 eventually, in the mean time, we'll make do. It's not such a big issue really, if anything big pops up, we'll backport. So, having form.py, web3py and whatnot in mind, +1 from me.

Regards