eppye-bots / bots

Automatically exported from code.google.com/p/bots
66 stars 126 forks source link

migrate to python 3.* #253

Closed GoogleCodeExporter closed 4 years ago

GoogleCodeExporter commented 9 years ago
Support for python > 3.3
No support for both python 2.* and python 3.* 

Libraries are critical;
- django: supports python 3 (since version 1.6)
- cherrypy: supports python 3
- genshi: supports python 3
- paramiko 20130909: no
- python MySQL-db: 20130909: no
- psycopg2 (for postgreSQL): supports python 3

Original issue reported on code.google.com by hjebb...@gmail.com on 9 Sep 2013 at 4:10

GoogleCodeExporter commented 9 years ago
Another option is to make a version with support for python 2.6 and 2.7
A lot of worrk for python3 can be done than.
Than check how much work still has to be doen for python3.
If not to much, make one version  (supporting both python 2 and 3)

Original comment by hjebb...@gmail.com on 9 Sep 2013 at 5:08

GoogleCodeExporter commented 9 years ago
python MySQL-db is still not suited for python 3.
paramiko seems to be moving slowly forward, but suited yet.
so...not for this time.

Original comment by hjebb...@gmail.com on 2 Jan 2014 at 7:34

GoogleCodeExporter commented 9 years ago

Original comment by hjebb...@gmail.com on 3 Jan 2014 at 6:36

GoogleCodeExporter commented 9 years ago
20150325:
status of libraries:
- OK: django, cherrypy, paramiko, genshi 
- NOK: mysqlbd; trying forrk 'mysqlclient-python '
Issues:
- Reading of excel does not work

Original comment by hjebb...@gmail.com on 25 Mar 2015 at 7:05

techieroshan commented 7 years ago

Any ETA on Python 3+ compatible version especially with postgres?

pepr commented 7 years ago

Hi,

I have the experience with Python, and also some experience with conversion from 2 to 3, with refactoring, and the related taks. I am going to use bots in near future, and I am willing to participate with the transition.

My experience is that it would be much easier to keep the Python 2 version in maintenance mode and create the Python 3 version -- separated from Python 2 version. I believe it is easier than trying to keep it Python-version independent.

Is this issue thread the mean for coordinating the effort? Or is there any other preferred communication channel to discuss the development?

Thanks, Petr