thanks you very much. I will try this issue and will return later. Le lun. 26 avr. 2021 à 13:48, Benjamin Schollnick < [email protected]> a écrit :
> Okay, it appears you are on a Macintosh…. > > Which is not the problem, but I ran into the same issue, and it’s most > likely that you installed a different version of Python than what came with > the OS? > > try: > > python3 -m pip list | grep -i django > python2 -m pip list | grep -i django > > I would bet even money, that the python2 command comes back with django > being installed there… > > That’s because the python2 install is earlier in the path than python3 > > How did I work around it, well. That’s going to be a bit different for > you since your using a different terminal package. > (In Apple’s Terminal -> Preferences -> Profiles -> Shell -> Startup, > check “Run Command”, and type “source ~/<profile filename>” assuming it’s > in the user home directory. > That will run the profile file on every opening of a terminal window, and > thus load your presets. I suspect that Parrot Terminal will have something > similar) > > (Yes, I know, why not use .profile or .bash_rc, etc, etc. Because I don’t > want the file to be hidden. It can be updated by any text editor, even > dropbox’s editor in the cloud, and it’s synced without having to worry > about it.) > > export PATH="/opt/homebrew/opt/[email protected]/libexec/bin:$PATH" > export PATH="/opt/homebrew/lib/python3.9/site-packages:$PATH" > > Which points to the python 3.9.2 install that I have from homebrew. > > I previously used aliases with mixed luck at times.. > (eg > alias pip='python3.9 -m pip $*' > alias pip='python3.9 -m pip $*’ > ) > But that broke when I went to an M1 Mac, because it wasn’t possible to > reliably get it to distinguish between an Rosetta2 session and an M1 > session. So > I stopped using the aliases. I did eventually resolve the M1 / Rosetta2 > session smartly, but that’s a chunk of the profile file, and probably > better left for another time. > > Hope that helps… > > On Apr 26, 2021, at 4:35 AM, Théodore KOSSI <[email protected]> > wrote: > > can you help me for this problem? > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/CAKiMjQG3F-qktrhRd3mF-ucK2fn8ph55r_sKD8ue5HakuWc%3DRQ%40mail.gmail.com > <https://groups.google.com/d/msgid/django-users/CAKiMjQG3F-qktrhRd3mF-ucK2fn8ph55r_sKD8ue5HakuWc%3DRQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > <django.png> > > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/20E47B5D-99D9-41A6-95BF-91B606C08B07%40schollnick.net > <https://groups.google.com/d/msgid/django-users/20E47B5D-99D9-41A6-95BF-91B606C08B07%40schollnick.net?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAKiMjQGBV%3DbdJNK-Yoe6m0oK0%2B1HxU-43Voj_nSgCLEKb4RAkA%40mail.gmail.com.
