search

qizhiyi / sqlalchemy-migrate

Automatically exported from code.google.com/p/sqlalchemy-migrate
MIT License
0 stars 0 forks source link

Initial py3k support #93

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Attached is some very basic work getting sqlalchemy-migrate to work under 
python 3.1. While it imports cleanly it fails 32/73 tests. Note that I had to 
remove (by renaming) the shell.py tests due to scripttest not being available 
for py3k. Similarly many tests failed because tempita is not available either.

I've attached a diff against hg head + complete test run output.

Original issue reported on code.google.com by mutual...@gmail.com on 24 Aug 2010 at 2:17

Attachments:

GoogleCodeExporter commented 8 years ago 
Thanks, any recommendations how Python 3k release should be handled?

Original comment by iElect...@gmail.com on 12 Sep 2010 at 11:24

GoogleCodeExporter commented 8 years ago 
I would appreciate some feedback regarding migrate/schema.py:ColumnDelta. It is 
subclassing dict which is done differently in 3.x+ and I believe these 
differences are causing test failure. Please see attached tests.txt for details.

Original comment by mutual...@gmail.com on 13 Sep 2010 at 3:53

GoogleCodeExporter commented 8 years ago 
Note that now Tempita has Py3k suppport http://pythonpaste.org/tempita/#id1

Original comment by iElect...@gmail.com on 14 Sep 2010 at 9:23

GoogleCodeExporter commented 8 years ago 
Is sqlalchemy-migrate currently in a working state
for Python 3.2 and it's dependencies ?

cheers
James

Original comment by prolo...@shortcircuit.net.au on 18 Mar 2011 at 5:19

GoogleCodeExporter commented 8 years ago 
I have ported sqlalchemy-migrate on my local system to python3.2. 10 of 143 
tests fail with sqlite and postgres tested. I have to do some further work 
here. A comment based migration like in sqlalchemy would be great.

Original comment by jajadini...@gmail.com on 21 Jun 2011 at 4:11

GoogleCodeExporter commented 8 years ago 
Any further improvement on Py3k 3.2 support ? i would be interested and open to 
help.

Original comment by marra...@gmail.com on 15 Sep 2011 at 9:20

GoogleCodeExporter commented 8 years ago 
The upcoming 0.7.2 release will drop support for Python versions before 2.6. I 
think the release is a good point to "officialy" start the Py3k port. I will 
setup Py3k integration builds on our CI instance and will anounce them here 
too.

Original comment by jan.ditt...@gmail.com on 29 Oct 2011 at 10:19

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I'm guessing this is pretty dead, since Elveos has gone into hibernation and 
doesn't accept donations any more.

Original comment by neilkatin@gmail.com on 20 Apr 2012 at 11:33

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
due to a request by the Turbo Gears developers I started to work on a Python 3 
port again. The dependency situation has improved since the last time I looked 
into this issue and because of the dropped 2.5 and earlier support I think it 
should now be possible to create a working Py2/Py3 code base more easily.

Original comment by jan.ditt...@gmail.com on 27 Sep 2012 at 3:04

GoogleCodeExporter commented 8 years ago 
Even though it is just a rude hack to make work on Python3 the commands I 
needed to quickstart a new TurboGears2 project I'm going to provide the changes 
I did to sqlalchemy-migrate to make it correctly import and run the 
version_control and db_version commands.

They might provide a starting point for a real python3 port.

Original comment by alessand...@gmail.com on 27 Sep 2012 at 9:59

Attachments: