#27753: Cleanups when no supported version of Django supports Python 2 anymore -------------------------------------+------------------------------------- Reporter: Aymeric Augustin | Owner: nobody Type: | Status: new Cleanup/optimization | Component: Utilities | Version: master Severity: Normal | Resolution: Keywords: | Triage Stage: | Someday/Maybe Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Claude Paroz): The question we discussed on IRC and GitHub with Tim is about deprecating or not deprecating those items. I would be for a standard deprecation process as I don't see how this is different from any other deprecation. But I'm open to read about use cases which would push for a delayed deprecation process for items related to Python 2. -- Ticket URL: <https://code.djangoproject.com/ticket/27753#comment:3> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/067.b88a2b1aa8c093290934976ef8a3b706%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.