Python 3 port - all PostgreSQL tests now pass on 2.7.2 and 3.2.2 with the same codebase

I now have Django passing the test suite with the PostgreSQL backend, on Python 2.7.2 and Python 3.2.2. The tests were run on Ubuntu Oneiric 64-bit in a VM. Python 3: Python 3.2.2 from the Ubuntu package repository. psycopg2-2.4.2 from http://initd.org/psycopg/ Python 2: Python 2.7.2 - Oneiric's

Re: Python 3 port - all PostgreSQL tests now pass on 2.7.2 and 3.2.2 with the same codebase

On 10 déc. 2011, at 09:03, Vinay Sajip wrote: > Is Oracle XE (Express Edition) a valid platform for Django's Oracle tests? Yes, it is. > Does anyone here have experience installing it on Ubuntu 64-bit? Yes, I documented the procedure here: https://code.djangoproject.com/wiki/OracleTestSetup

Re: Python 3 port - all PostgreSQL tests now pass on 2.7.2 and 3.2.2 with the same codebase

On Sat, Dec 10, 2011 at 1:03 AM, Vinay Sajip wrote: > So - with Ian Clelland's post[1] from a couple of days ago, we have > successful runs on 2.x and 3.x using a single codebase and SQLite, > PostgreSQL and MySQL backends. I suppose Oracle will be the next one > to focus

Re: New feature: HTTP OPTIONS and improved HEAD for View

Just bumping this - can anyone suggest what the next steps should be? It'd be nice to get it fixed for 1.4. Thanks, Jamie On Nov 28, 5:59 pm, Jamie Matthews wrote: > > Yeah, that implementation seems preferable. What was the reason for backing > > it out? > > Not

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

What I would love as a developer in the documentation is, what do I need to do so my code "could" run on Python 3. It might not work, but most obvious issues (like b() and u()) would be out of the way. -- Gert Mobile: +32 498725202 Twitter: @gvangool Web: http://gertvangool.be On Sat, Dec 10,

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

On Dec 10, 12:40 pm, Gert Van Gool wrote: > What I would love as a developer in the documentation is, what do I > need to do so my code "could" run on Python 3. > It might not work, but most obvious issues (like b() and u()) would be > out of the way. I know it's not the

Proposal: drop Python 2.5 support in Django 1.5

Hi all, In other threads we've discussed the problem of Python 2/3 compatibility where we need to catch exceptions and need the exception object itself. This leads to ugliness and possible poor performance on PyPy. However, we could get around it completely if we drop Python 2.5 support, since

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

On Fri, Dec 9, 2011 at 4:32 PM, Paul Egges wrote: > I was thinking the same thing. Make absolutely sure it works under 2.5-2.7 > and even if there are a couple of issues or items not fully tested under > 3.2.2 at least we will be moving in the right direction. > > My

Re: Proposal: drop Python 2.5 support in Django 1.5

> I propose that we attempt to merge the py3k work after the release > of 1.4, rather than let it go stale and lose the good work done so far, > and also drop support for Python 2.5 for Django 1.5. +1 I think dropping Python 2.5 in the process of porting Django to Python 3.X are reasonable

Re: Python 3 port - all PostgreSQL tests now pass on 2.7.2 and 3.2.2 with the same codebase

> Stupidly, I had left the 'HOST' line out of the above configuration, > causing both 'default' and 'other' to point to 'localhost'. Once this > was rectified, the test times seem a lot more reasonable. So it was > nothing to do with runtime overheads like calling u() etc. I did a little

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

On 09/12/11 20:26, Ram Rachum wrote: > In which Django release are we hoping to release this port? 1.4 or 1.5? 1.4 is never going to happen. We are hoping to release a 1.4 alpha very soon, merging this work would be a major mistake at this point. The patch requires lots of changes to the way

Re: Proposal: drop Python 2.5 support in Django 1.5

On Sat, Dec 10, 2011 at 8:36 AM, Luke Plant wrote: > So, I propose that we attempt to merge the py3k work after the release > of 1.4, rather than let it go stale and lose the good work done so far, > and also drop support for Python 2.5 for Django 1.5. I think both of

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

On Dec 10, 4:47 pm, Luke Plant wrote: > > 1.4 is never going to happen. We are hoping to release a 1.4 alpha very > soon, merging this work would be a major mistake at this point. > > The patch requires lots of changes to the way things work. Many are > small, but they

Re: Proposal: drop Python 2.5 support in Django 1.5

On Sat, Dec 10, 2011 at 10:56 AM, Adrian Holovaty wrote: > I think both of these proposals are great -- start merging the Python > 3 work right after we release 1.4, and drop support for Python 2.5 in > trunk after 1.4 is released. I totally agree. Jacob -- You received

Python 3 port - notes for people wanting to review changes/port apps

I've created a page on the Django Wiki indicating what guidelines I used when porting Django from 2.x to a single codebase for 2.x/3.x, and which can also be followed by people wanting to port apps across on the same basis. The first cut is at

Re: Python 3 port - notes for people wanting to review changes/port apps

On Sat, Dec 10, 2011 at 11:53 AM, Vinay Sajip wrote: > I've created a page on the Django Wiki indicating what guidelines I > used when porting Django from 2.x to a single codebase for 2.x/3.x, > and which can also be followed by people wanting to port apps across > on the

Re: Python 3 port - notes for people wanting to review changes/port apps

On Dec 10, 8:49 pm, Jacob Kaplan-Moss wrote: > What do you think about using lib2to3 to write some custom > fixers to do some of this grunt work automatically? Might help people > port their Django sites/apps a bit easier, right? On the face of it, I'd say it's doable, and

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

So, with the current plan to add 3.x support to 1.5 and the plan to remove 2.5.x support in 1.5. Should all the exception handling blocks be converted to "except MyExceptionClass as e:" style notation then? This also removes the need for u() and b(), right? This is because 2.6.x supports u' ' and

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/10/2011 03:35 PM, Joe & Anne Tennies wrote: > So, with the current plan to add 3.x support to 1.5 and the plan to > remove 2.5.x support in 1.5. Should all the exception handling blocks be > converted to "except MyExceptionClass as e:" style

Re: Proposal: drop Python 2.5 support in Django 1.5

On Sun, Dec 11, 2011 at 1:32 AM, Jacob Kaplan-Moss wrote: > On Sat, Dec 10, 2011 at 10:56 AM, Adrian Holovaty wrote: >> I think both of these proposals are great -- start merging the Python >> 3 work right after we release 1.4, and drop support for Python

Re: Proposal: drop Python 2.5 support in Django 1.5

On Sat, Dec 10, 2011 at 7:35 PM, Paul Egges wrote: > +1 > > I thought there was an implicit understanding that only 3 versions of > Python would be supported at any given time. If so it makes sense to drop > support for 2.4 when we add 3.x. > > > > On Sat, Dec 10, 2011

Re: Proposal: drop Python 2.5 support in Django 1.5

Wasn't the reason why Django 1.4 should still support Python 2.5 because of RHEL 5? If so, RHEL 5 never had official Python 2.5 support but only supported Python 2.4. RHEL 6 does not support 2.5 either, its Python version is 2.6. What is the reason that Django 1.4 needs to support Python 2.5?

Re: Proposal: drop Python 2.5 support in Django 1.5

On Sat, Dec 10, 2011 at 6:37 PM, Alex Gaynor wrote: > 2.5 is EOL and no longer receiving security patches even, it is > *irresponsible* of us to support it (I claim).  ANyways +1 This is a very good reason I hadn't though of. Anyway, looks like this is a plan! Excellent.

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

I would like to say congrats and thanks to all those who have put in hard work on the Python 3 port. It is a very socially responsible thing to do, as django is one of the major open-source python framework, and will certainly act as encouragement for other python-based open-source to do the

Re: Proposal: drop Python 2.5 support in Django 1.5

+1 Regards, Kok HOOR Sent from my iPad On Dec 11, 2011, at 10:06 AM, Adrian Holovaty wrote: > On Sat, Dec 10, 2011 at 6:37 PM, Alex Gaynor wrote: >> 2.5 is EOL and no longer receiving security patches even, it is >> *irresponsible* of us to