django-admin pointing outside virtualenv

I've initialised a virtual environment using the virtualenvwrapper command mkvirtualenv -a <path to project> django_project.

I then installed django with pip install django. But then if i try to use django-admin i get:

Traceback (most recent call last):

File "/usr/local/bin/django-admin", line 7, in <module>

from django.core.management import execute_from_command_line

ModuleNotFoundError: No module named 'django'

Now pip list gives me

Package    Version

---------- -------

Django     2.1.3

pip        18.1

pytz       2018.7

setuptools 40.6.2

wheel      0.32.3

python -m django --version gives

2.1.3

If I run which python it correctly points to my virtualenv, however which django-admin gives:

/usr/local/bin/django-admin

I'd think that it should point to my venv. Why would it point to a global django admin? How do I fix it so that it'll work for my future virtual environments?

I'm on MacOS using zsh and python 3.7.0.

Thank you!

Edit: Mistake in a command

Edit: I realised I don't have a system-wide installation of Django and so the django-admin and django-admin.py files in my /usr/local/bin must've been leftovers from an earlier installation. Hence I deleted them and that solved the problem. Without any further django-admin inside the venv point to the correct django installation (inside the venv).

However, I would still like to know why the command didn't point to the Django installed in the venv in the first place?

edited Nov 27 '18 at 16:00

asked Nov 27 '18 at 15:06

Morten

326

Jus checked my $PATH inside the venv, and it correctly points to the venv as the first directory. In the env/bin there is a django-admin with the shebang line correctly pointing to the venv...

– Morten
Nov 27 '18 at 15:29

add a comment |

I've initialised a virtual environment using the virtualenvwrapper command mkvirtualenv -a <path to project> django_project.

I then installed django with pip install django. But then if i try to use django-admin i get:

Traceback (most recent call last):

File "/usr/local/bin/django-admin", line 7, in <module>

from django.core.management import execute_from_command_line

ModuleNotFoundError: No module named 'django'

Now pip list gives me

Package    Version

---------- -------

Django     2.1.3

pip        18.1

pytz       2018.7

setuptools 40.6.2

wheel      0.32.3

python -m django --version gives

2.1.3

If I run which python it correctly points to my virtualenv, however which django-admin gives:

/usr/local/bin/django-admin

I'd think that it should point to my venv. Why would it point to a global django admin? How do I fix it so that it'll work for my future virtual environments?

I'm on MacOS using zsh and python 3.7.0.

Thank you!

Edit: Mistake in a command

However, I would still like to know why the command didn't point to the Django installed in the venv in the first place?

edited Nov 27 '18 at 16:00

asked Nov 27 '18 at 15:06

Morten

326

Jus checked my $PATH inside the venv, and it correctly points to the venv as the first directory. In the env/bin there is a django-admin with the shebang line correctly pointing to the venv...

– Morten
Nov 27 '18 at 15:29

add a comment |

I've initialised a virtual environment using the virtualenvwrapper command mkvirtualenv -a <path to project> django_project.

I then installed django with pip install django. But then if i try to use django-admin i get:

Traceback (most recent call last):

File "/usr/local/bin/django-admin", line 7, in <module>

from django.core.management import execute_from_command_line

ModuleNotFoundError: No module named 'django'

Now pip list gives me

Package    Version

---------- -------

Django     2.1.3

pip        18.1

pytz       2018.7

setuptools 40.6.2

wheel      0.32.3

python -m django --version gives

2.1.3

If I run which python it correctly points to my virtualenv, however which django-admin gives:

/usr/local/bin/django-admin

I'd think that it should point to my venv. Why would it point to a global django admin? How do I fix it so that it'll work for my future virtual environments?

I'm on MacOS using zsh and python 3.7.0.

Thank you!

Edit: Mistake in a command

However, I would still like to know why the command didn't point to the Django installed in the venv in the first place?

edited Nov 27 '18 at 16:00

asked Nov 27 '18 at 15:06

Morten

326

I've initialised a virtual environment using the virtualenvwrapper command mkvirtualenv -a <path to project> django_project.

I then installed django with pip install django. But then if i try to use django-admin i get:

Traceback (most recent call last):

File "/usr/local/bin/django-admin", line 7, in <module>

from django.core.management import execute_from_command_line

ModuleNotFoundError: No module named 'django'

Now pip list gives me

Package    Version

---------- -------

Django     2.1.3

pip        18.1

pytz       2018.7

setuptools 40.6.2

wheel      0.32.3

python -m django --version gives

2.1.3

If I run which python it correctly points to my virtualenv, however which django-admin gives:

/usr/local/bin/django-admin

I'd think that it should point to my venv. Why would it point to a global django admin? How do I fix it so that it'll work for my future virtual environments?

I'm on MacOS using zsh and python 3.7.0.

Thank you!

Edit: Mistake in a command

However, I would still like to know why the command didn't point to the Django installed in the venv in the first place?

django python-3.x virtualenvwrapper

edited Nov 27 '18 at 16:00

asked Nov 27 '18 at 15:06

Morten

326

edited Nov 27 '18 at 16:00

asked Nov 27 '18 at 15:06

Morten

326

edited Nov 27 '18 at 16:00

asked Nov 27 '18 at 15:06

Morten

326

asked Nov 27 '18 at 15:06

Morten

326

asked Nov 27 '18 at 15:06

Morten

326

Jus checked my $PATH inside the venv, and it correctly points to the venv as the first directory. In the env/bin there is a django-admin with the shebang line correctly pointing to the venv...

– Morten
Nov 27 '18 at 15:29

add a comment |

Jus checked my $PATH inside the venv, and it correctly points to the venv as the first directory. In the env/bin there is a django-admin with the shebang line correctly pointing to the venv...

– Morten
Nov 27 '18 at 15:29

Jus checked my $PATH inside the venv, and it correctly points to the venv as the first directory. In the env/bin there is a django-admin with the shebang line correctly pointing to the venv...

– Morten
Nov 27 '18 at 15:29

add a comment |

1 Answer
1

active

oldest

votes

So Django has been installed at system level, while you verified that python command refer to your virtual environment. I bet this is an issue with pip. You may check that it is under <path to project>/bin and is correctly used when you perform

(django_project) $ pip install django

Try to run

which pip

with your venv enabled and disabled to see what pip is used in each case

answered Nov 27 '18 at 15:46

Antwane

7,93332456

Thank you Antwane. I don't think django was installed system-wide this time around. which pip correctly points to the venv, while active and to the system while not active. I can also see that django is installed in the venv/bin folder.

– Morten
Nov 27 '18 at 15:53

In such case, you have to understand why django-admin executable was copied into /usr/local/bin/django-admin. It may have been installed from OS package manager (previous installation ?). Can you try to pip uninstall django and check the list of files about to be deleted to see if this command try to modify something at system level ? Also, which user own /usr/local/bin/django-admin ?

– Antwane
Nov 27 '18 at 15:57

As I write in my latest edit, I think the django-admin executables in /usr/local/bin/ are leftovers from a previous installation, as you write. I deleted them and it solved the problem for me. I can't see the owner as I have deleted them, but I'm quite sure it would have been me.

– Morten
Nov 27 '18 at 16:06

add a comment |

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53502536%2fdjango-admin-pointing-outside-virtualenv%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

(django_project) $ pip install django

Try to run

which pip

with your venv enabled and disabled to see what pip is used in each case

answered Nov 27 '18 at 15:46

Antwane

7,93332456

Thank you Antwane. I don't think django was installed system-wide this time around. which pip correctly points to the venv, while active and to the system while not active. I can also see that django is installed in the venv/bin folder.

– Morten
Nov 27 '18 at 15:53

In such case, you have to understand why django-admin executable was copied into /usr/local/bin/django-admin. It may have been installed from OS package manager (previous installation ?). Can you try to pip uninstall django and check the list of files about to be deleted to see if this command try to modify something at system level ? Also, which user own /usr/local/bin/django-admin ?

– Antwane
Nov 27 '18 at 15:57

As I write in my latest edit, I think the django-admin executables in /usr/local/bin/ are leftovers from a previous installation, as you write. I deleted them and it solved the problem for me. I can't see the owner as I have deleted them, but I'm quite sure it would have been me.

– Morten
Nov 27 '18 at 16:06

add a comment |

(django_project) $ pip install django

Try to run

which pip

with your venv enabled and disabled to see what pip is used in each case

answered Nov 27 '18 at 15:46

Antwane

7,93332456

Thank you Antwane. I don't think django was installed system-wide this time around. which pip correctly points to the venv, while active and to the system while not active. I can also see that django is installed in the venv/bin folder.

– Morten
Nov 27 '18 at 15:53

In such case, you have to understand why django-admin executable was copied into /usr/local/bin/django-admin. It may have been installed from OS package manager (previous installation ?). Can you try to pip uninstall django and check the list of files about to be deleted to see if this command try to modify something at system level ? Also, which user own /usr/local/bin/django-admin ?

– Antwane
Nov 27 '18 at 15:57

As I write in my latest edit, I think the django-admin executables in /usr/local/bin/ are leftovers from a previous installation, as you write. I deleted them and it solved the problem for me. I can't see the owner as I have deleted them, but I'm quite sure it would have been me.

– Morten
Nov 27 '18 at 16:06

add a comment |

(django_project) $ pip install django

Try to run

which pip

with your venv enabled and disabled to see what pip is used in each case

answered Nov 27 '18 at 15:46

Antwane

7,93332456

(django_project) $ pip install django

Try to run

which pip

with your venv enabled and disabled to see what pip is used in each case

answered Nov 27 '18 at 15:46

Antwane

7,93332456

answered Nov 27 '18 at 15:46

Antwane

7,93332456

answered Nov 27 '18 at 15:46

Antwane

7,93332456

answered Nov 27 '18 at 15:46

Antwane

7,93332456

Thank you Antwane. I don't think django was installed system-wide this time around. which pip correctly points to the venv, while active and to the system while not active. I can also see that django is installed in the venv/bin folder.

– Morten
Nov 27 '18 at 15:53

In such case, you have to understand why django-admin executable was copied into /usr/local/bin/django-admin. It may have been installed from OS package manager (previous installation ?). Can you try to pip uninstall django and check the list of files about to be deleted to see if this command try to modify something at system level ? Also, which user own /usr/local/bin/django-admin ?

– Antwane
Nov 27 '18 at 15:57

As I write in my latest edit, I think the django-admin executables in /usr/local/bin/ are leftovers from a previous installation, as you write. I deleted them and it solved the problem for me. I can't see the owner as I have deleted them, but I'm quite sure it would have been me.

– Morten
Nov 27 '18 at 16:06

add a comment |

Thank you Antwane. I don't think django was installed system-wide this time around. which pip correctly points to the venv, while active and to the system while not active. I can also see that django is installed in the venv/bin folder.

– Morten
Nov 27 '18 at 15:53

In such case, you have to understand why django-admin executable was copied into /usr/local/bin/django-admin. It may have been installed from OS package manager (previous installation ?). Can you try to pip uninstall django and check the list of files about to be deleted to see if this command try to modify something at system level ? Also, which user own /usr/local/bin/django-admin ?

– Antwane
Nov 27 '18 at 15:57

As I write in my latest edit, I think the django-admin executables in /usr/local/bin/ are leftovers from a previous installation, as you write. I deleted them and it solved the problem for me. I can't see the owner as I have deleted them, but I'm quite sure it would have been me.

– Morten
Nov 27 '18 at 16:06

Thank you Antwane. I don't think django was installed system-wide this time around. which pip correctly points to the venv, while active and to the system while not active. I can also see that django is installed in the venv/bin folder.

– Morten
Nov 27 '18 at 15:53

In such case, you have to understand why django-admin executable was copied into /usr/local/bin/django-admin. It may have been installed from OS package manager (previous installation ?). Can you try to pip uninstall django and check the list of files about to be deleted to see if this command try to modify something at system level ? Also, which user own /usr/local/bin/django-admin ?

– Antwane
Nov 27 '18 at 15:57

As I write in my latest edit, I think the django-admin executables in /usr/local/bin/ are leftovers from a previous installation, as you write. I deleted them and it solved the problem for me. I can't see the owner as I have deleted them, but I'm quite sure it would have been me.

– Morten
Nov 27 '18 at 16:06

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Btukfyl