This repository has been archived by the owner on Jun 16, 2018. It is now read-only.
django.core.management error during setup #133
Comments
Hi Jessica, that error usually comes from not having Django installed or not activating your virtualenv or something similar. It's essentially saying "Command Not Found." Make sure that you installed Django in your virtual env and not just systemwide, also. |
Excellent, thanks for getting back to me so quickly! Will give it another
shot.
Best,
Jessica
…On Sun, Apr 16, 2017 at 12:18 PM, jkokenge ***@***.***> wrote:
Hi Jessica, that error usually comes from not having Django installed or
not activating your virtualenv or something similar. It's essentially
saying "Command Not Found." Make sure that you installed Django in your
virtual env and not just systemwide, also.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#133 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AZMisdn7PcJMfNq4P7krwT4FtcGgg24hks5rwj9NgaJpZM4M-c9w>
.
--
*Jessica Batke *|* Senior Editor, ChinaFile, **Center on U.S.-China
Relations*
*Asia Society *| 725 Park Avenue | New York, NY | 10021 | t: 212-327-9357
*| *AsiaSociety.org/ChinaCenter <http://www.asiasociety.org/ChinaCenter> |
ChinaFile.com <http://www.chinafile.com/>
Hong Kong | Houston | Los Angeles | Manila | Mumbai | New York | San
Francisco | Seoul | Shanghai | Sydney | Washington DC | Zürich
|
@jkokenge is totally right. Let us know how it goes. |
Guys -- you may or may not care, but thought I would let you know that I
found this while waiting for your reply (which is not meant as a dig - you
guys replied REALLY quickly):
https://www.kryogenix.org/code/browser/sorttable/
and that's what I'm using at the moment since we need to get our new
section of the website up post-haste. I'm planning to return to datadesk
once I have a bit more time to think about more long-term data management,
but I'm sure you know how the last-minute time pressure goes . . .
…On Sun, Apr 16, 2017 at 8:03 PM, Ben Welsh ***@***.***> wrote:
@jkokenge <https://github.com/jkokenge> is totally right. Let us know how
it goes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#133 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AZMisT5uJHFW2TfiBOlEQF0CsPc1dcSnks5rwqxpgaJpZM4M-c9w>
.
--
*Jessica Batke *|* Senior Editor, ChinaFile, **Center on U.S.-China
Relations*
*Asia Society *| 725 Park Avenue | New York, NY | 10021 | t: 212-327-9357
*| *AsiaSociety.org/ChinaCenter <http://www.asiasociety.org/ChinaCenter> |
ChinaFile.com <http://www.chinafile.com/>
Hong Kong | Houston | Los Angeles | Manila | Mumbai | New York | San
Francisco | Seoul | Shanghai | Sydney | Washington DC | Zürich
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm trying to follow the great getting started instructions here: http://latimes-table-stacker.readthedocs.io/en/latest/gettingstarted.html but have run into an error that I wanted to see if anyone else had overcome. I've never used django before, so apologies if this is something obvious for the more django-inclined.
Every step was working perfectly until I got to the database setup phase. When I ran this:
python manage.py syncdb
I got this error message:
is this an error that other people have run into? If so, is there an easy way to overcome it?
thanks!
The text was updated successfully, but these errors were encountered: