I think the original question was around backwards conversion of 3.x
code to 2.7.
I don't know of course because all my efforts have been forwards but I
believe the six module would be the easiest way backwards.
And I imagine you would simply run your unit tests in 2.7 and use the
six utilities to correct errors. With a little luck that would
simultaneously keep the codebase compatible with 3.x for the inevitable
forward upgrade.
Just a thought
Mike
On 24/09/2019 10:00 pm, Larry Martell wrote:
On Tue, Sep 24, 2019 at 4:15 AM Andréas Kühne
<andreas.ku...@hypercode.se> wrote:
Official access isn't denied - and python 2 will probably be available. The
problem is that you don't get any security fixes or any updates at all. That in
itself is a major problem. If someone is saying that you need to use python 2,
I would strongly recommend them to not even think about it. All code that is
written will be useless in a couple of years time, and need to be updated or
even worse thrown away.
This is totally untrue. Yes, all code should be converted to py3, but
that is simply not happing at many companies. They will continue to
use their py2 apps, and either support them internally or purchase py2
support from one of the many companies offering it. Is that a good
idea? No, but it's a reality.
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/251d3edb-1d78-cc02-8f46-4171f9639255%40dewhirst.com.au.
