Closed sgongar closed 9 years ago
That syntax belongs to Python 3. Are you inside of the right virtualenv?
Xabi is right, have you set up a Python 3 environment? Please, check the version that you are using within your virtual environment with the following commands:
source .venv/bin/activate
python --version
... and let us know!
The installation script set up a virtualenv with python 2.7.3 however if I do the same actions in Debian 8 I get a Python 3 environment with no problems.
So, the problem could be this, maybe we must correct the installation script.
Yes, that is the problem. The Python 3 environment is automatically set up in a Debian 8, meanwhile in Debian 7 the environment that the script installs is a Python 2.7.3. This is because the first version of the software was developed for Debian 7 and Python 2.7, meanwhile the current "development_3k" branch is being developed for Debian 8 and Python 3.
Do you have any concerns in installing Debian 8 and Python 3?
The "legacy" Debian 7 and Python 2.7 installation is kept in the script for compatibility issues but should be used only when installing the branch "master". Maybe we should rename the branch "devleopment_3k" to master and "master" to legacy.
No, the server runs fine in Debian 8. Rename the branches isn't a bad idea.
Is this still an issue or can we close it?
If Debian 7 won't support server/development_3k we should rename the branches as proposed by @rtp-calpoly. Anyway, we can close this issue.
Ok, @rtp-calpoly can you rename the branches? I close the issue right now.
Please post a new is he with this task. My idea was to rename the branches once development_3k was stable, that is, after conducting real tests during the summer. As of today, only the master branch has been deployed and tested; therefore, I think that it is better to wait....
When I try to run the server using:
python manage.py
I get this output:I'm using the last release of Debian 7 and Python 2.7. The system is running on a VBox machine with nothing else.