Maybe, it wasn't on the radar of the django developers either and had to be fixed in the framework after python3 was released.
Happens sometimes I suppose, hard to keep up with depreciation of functions and the impact on a framework. Anyways, I suppose we juar have to file the bug reports and fix each function step by step until all deprecated functions are removed and replaced with the ones that need to be used for python 3.8 and forward. On Fri, 29 Nov 2019, 20:44 Woody, <[email protected]> wrote: > Shouldn't that be done before the release rather than afterward? > > -- > Resources: > - http://web2py.com > - http://web2py.com/book (Documentation) > - http://github.com/web2py/web2py (Source code) > - https://code.google.com/p/web2py/issues/list (Report Issues) > --- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/web2py/cbb87866-f170-4338-ba3f-e93dfc3861f3%40googlegroups.com > . > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/CADHCKLSkb6MXuXE-u%3Dw2xP5bUOAyXvUsj4LBJH4W45ADQgUgDg%40mail.gmail.com.
