Ankita, why would a new project be forced to use Python 2 by a (probably old) package? A well-maintained package must already have its Python 3 version.
Why can't we find an alternative package that uses Python 3? I am curious about what package that is.
On Sun, Sep 22, 2019 at 12:32 AM Ankita Gupta <ankita.gupta1998@gmail.com> wrote:
Not related to Django, I have a project made in python3 but due to some package installation, i need to convert my project to python2. Is there any method or package to solve this?--
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/875549f9-5bca-4280-88fd-db197ca577dc%40googlegroups.com.
Regards,
Aldian Fazrihady
http://aldianfazrihady.com
http://aldianfazrihady.com
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/CAN7EoAaiCDsrd3hURY9kb_h%2BA7aMU24aoZk1Dw8oHLAVfkbKTw%40mail.gmail.com.
No comments:
Post a Comment