Agreed - Mike's suggestion is a very sensible one. In the short term, supporting 2 and 3 could be very useful, until you have the option to drop support for 2.
On Wednesday, 25 September 2019 01:00:44 UTC+2, Mike Dewhirst wrote:
-- On Wednesday, 25 September 2019 01:00:44 UTC+2, Mike Dewhirst wrote:
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
> <andrea...@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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/dca5a92a-42c3-4740-9b7c-6bb7fa812d96%40googlegroups.com.
No comments:
Post a Comment