Stop supporting python 2.6

[Vinicius Assef]

Interesting article written by one of the core developers:
http://www.curiousefficiency.org/posts/2015/04/stop-supporting-python26.html

--
Vinicius Assef

[Giovanni Barillari]

Would simplify a lot the code and the development process. But I would like to see python3 support attach to the drop of 2.6.

/Giovanni

[Michele Comitini]

+1

--
-- 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.

[Leonel Câmara]

Agreed on dropping 2.6 and adding python 3 support which would be much easier since a lot of features are backported to 2.7.

Feel free to assign me some modules to convert towards this effort.

[Richard Vézina]

+1 for python 3

If Python 2.6 is blocking ditch it...

Richard

On Tue, Oct 13, 2015 at 8:44 AM, Leonel Câmara <leonel...@gmail.com> wrote:

Agreed on dropping 2.6 and adding python 3 support which would be much easier since a lot of features are backported to 2.7.

Feel free to assign me some modules to convert towards this effort.

--

[Niphlod]

nothing is blocking. it's just a good example to post on "why we dropped 2.6 support". Up until now travis is taking care of the 2.6 testing and I'm not seeing lots of tests failing solely on 2.6 (meaning, we're not used to write code that works on 2.7 and not on 2.6).

That being said there are a few places where we used a compatible syntax (or it's there since the beginning of times) that could be refactored to work on 2.7 only, but that's pretty much about it.

PY3 support, on the other end, is a total different story.

[Vinicius Assef]

I'd suggest one step a time.

IMHO, more important is having a clear roadmap to address Python 3 in
near future.

--
Vinicius Assef