I personally just edit my manage.py to change it from python to python3. Maybe we could just document that?
(Or would it work to use os.path.basename(sys.executable) ?) On Sun, Apr 8, 2018 at 11:02 AM, Tom Forbes <t...@tomforb.es> wrote: > It may be an obstacle but I believe it’s better than having them nuke > their base systems by accident by installing a package that conflicts with > their base system. This isn’t such a huge issue on MacOS but on Linux it is > and I’ve seen it happen a few times. Not to mention the issue of multiple > conflicting dependencies across projects - all in all it’s really not a > recommended and we should not look to make it easier IMO. > > People have different setups and whatever works, works, but things like > pipenv are maturing rapidly and solve the convenience issue you describe. > I personally use virtualenvwrapper which is really simple to set up and > displays the current virtual environment in the prompt, and makes it really > easy to switch between them/create new ones. > > Tom > > > > On 8 April 2018 at 15:00:46, Bobby Mozumder (bmozum...@gmail.com) wrote: > > I never really liked the idea of using VirtualEnv or HomeBrew over the > default installation in Mac OS. (FreeBSD has the same naming issues). > > Having beginners use VirtualEnv or HomeBrew always struck me as a huge > obstacle to getting a beginners Django developer's environment operational, > as well as being a huge pain-in-the-ass of always setting VirtualEnvs for > each shell. So, I personally don’t use them anymore, and just use the base > system now. > > I wish there was a process of running Django out-of-the-box from a default > Mac OS install. > > -bobby > > On Apr 8, 2018, at 8:27 AM, Tom Forbes <t...@tomforb.es> wrote: > > This only seems to be an issue when you are using the base system > interpreter to run manage.py. installing Django and other dependencies > there is not recommended for a variety of reasons, and this isn't a problem > when using a virtualenv, it doesn't seem like there is much to fix IMO. > > > On Sun, 8 Apr 2018, 08:19 Bobby Mozumder, <bmozum...@gmail.com> wrote: > >> Is it OK to reopen that ticket? >> >> The problem is that python2 and python3 need to coexist in most systems, >> and you can’t just rename python3 to python. >> >> -bobby >> >> On Apr 6, 2018, at 8:30 PM, Tim Graham <timogra...@gmail.com> wrote: >> >> It was tried in https://code.djangoproject.com/ticket/27878 but it >> caused problems, particularly on Windows. >> >> On Friday, April 6, 2018 at 6:35:50 PM UTC-4, Josh Smeaton wrote: >>> >>> I think you're right and PEP394 is the relevant text: >>> https://www.python.org/dev/peps/pep-0394/ >>> >>> TL;DR >>> >>> For now, *python* should refer to python2 and *python3* should be used >>> to refer to python 3. >>> >>> On Saturday, 7 April 2018 07:07:35 UTC+10, Bobby Mozumder wrote: >>>> >>>> The header of manage.py has: #!/usr/bin/env python >>>> >>>> Shoudn’t it be: #!/usr/bin/env python3 >>>> >>>> Since 2.0 is now only Python3. Both my Mac OS & FreeBSD environments >>>> have Python 3.5+ as “python3". (I’m not sure about Linux or other >>>> environments). >>>> >>>> Is that a bug I need to file? >>>> >>>> -bobby >>>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-developers+unsubscr...@googlegroups.com. >> To post to this group, send email to django-developers@googlegroups.com. >> Visit this group at https://groups.google.com/group/django-developers. >> To view this discussion on the web visit https://groups.google. >> com/d/msgid/django-developers/7cdf48bb-ab0b-449d-8f33- >> a4c6d7777369%40googlegroups.com >> <https://groups.google.com/d/msgid/django-developers/7cdf48bb-ab0b-449d-8f33-a4c6d7777369%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-developers+unsubscr...@googlegroups.com. >> To post to this group, send email to django-developers@googlegroups.com. >> Visit this group at https://groups.google.com/group/django-developers. >> To view this discussion on the web visit https://groups.google.com/d/ >> msgid/django-developers/E1881F92-2D8C-45D8-8315-E5D72D0D7B6E%40gmail.com >> <https://groups.google.com/d/msgid/django-developers/E1881F92-2D8C-45D8-8315-E5D72D0D7B6E%40gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-developers/CAFNZOJORs_f%3D70fkjdCRX%2BHwY4%2B%3DTk2Ns8TZwU- > m7zboTY8Ssg%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAFNZOJORs_f%3D70fkjdCRX%2BHwY4%2B%3DTk2Ns8TZwU-m7zboTY8Ssg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-developers/AF1F8F57-9E1D-47D5-A655-A86F60E2969F%40gmail.com > <https://groups.google.com/d/msgid/django-developers/AF1F8F57-9E1D-47D5-A655-A86F60E2969F%40gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-developers/CAFNZOJO5N2uaqvNXkD_% > 2BDKcaTzuo_UcsJix2A12m1tvWY9L_WA%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAFNZOJO5N2uaqvNXkD_%2BDKcaTzuo_UcsJix2A12m1tvWY9L_WA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFO84S5rYmrQ9ggK4hr%3DBR78kP%2BDYJhW4PgZQgyKUizFxsOnhg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
