I am trying to run a django project on an EC2 server, however, when I run python3 manage.py runserver, it returns this error, django.core.exceptions.ImproperlyConfigured: SQLite 3.9.0 or later is required (found 3.7.17).. I then check to see what version of SQLite3 is running on my python installation on my EC2 server by running sqlite3.sqlite_version, and it returns 3.7.17. So I then try to update SQLite3 using the default AWS EC2 Amazon Linux package manager, yum, by running yum install sqlite. It then returns this, Package sqlite-3.7.17-8.amzn2.1.1.x86_64 already installed and latest version, even though it is not the latest version. How can I install the latest version of SQLite3 to fix this?
I had the same problem. Since my app is very small with little dependency, I was able to quickly switch to EC2 sever running Ubuntu. It is necessary to learn how to use Ubuntu (apt).
You can find right now in the installation:
Package: sqlite3
Version: 3.31.1-4ubuntu0.2
Related
So I've been going in circles looking for answers to this and it seems to be a problem very specific to my situation.
I am trying to get a Python Django project connecting to an Azure SQL Database with the ODBC 17 Driver.
I have used brew to install msodbcsql17 and mssql-tools.
I have created a virtualenv using pip install virtualenv and python3 -m venv env
After activating this virtual environment with source ./env/bin/activate and trying pip install pyodbc I get this error:
ld: library not found for -lodbc
I'm guessing this is some sort of PATH issue, but I'm ignorant on how to debug it or correct it.
Any information on how to properly set up Python and Django on Mac OS 11.4 to work with Azure SQL database in a virtual environment would be much appreciated, because everything I have tried os far has led me to similar dead ends with libraries not being found or loaded one way or another.
Edit 1:
So I've discovered from https://learn.microsoft.com/en-us/sql/connect/odbc/linux-mac/install-microsoft-odbc-driver-sql-server-macos?view=sql-server-ver15 that ODBC does not support M1, which I realize now is what my laptop has... so this may be the underlying issue for all the problems I've been encountering.
I have used the entire day trying to install EB CLI on windows in order to connect to AWS Elastic Beanstalk but I keep getting the same error:
Running setup.py install for docker-py
Could not find .egg-info directory in install record for docker-py>=1.1.0 <=1.7.2 (from awsebcli)
I started out with the latest version of Python but after reading of other users issues on Stack Overflow I decided to downgrade my Python version to 3.4.0. However, I still get the same error, meaning that I cannot do EB init to connect to my Elastic Beanstalk instance since it does not recognise the command.
I also tried to un-install docker-py and re-install it - still not working.
Any ideas to what I am doing wrong?
It looks as if you may have version conflicts. See a similar issue here
Try installing awsebcli in a virtual environment, as suggested by the aws docs.
I created my own python module and packaged it with distutils. Now I installed it on a new system (python setup.py install) and I'm trying to call it from a plpython3u function, but I get an error saying the module does not exist.
It was working on a previous Ubuntu instalation, and I'm not sure what I did wrong when setting up my new system.
I'm trying this on a Ubuntu 15.10 pc with postgresql 9.5, everything freshly installed. I'm also trying this setup in a docker image built with the same componentes (ubuntu 15.10 and pg 9.5). I get the same error in both setups.
Could you please hint me about why this is failing? I wrote down my installation instructions for both systems (native and docker), so I can provide them if that helps.
Thanks
Sorry guys I think I found the problem. I'm using plpython3 in my stored procedure, but intalled my custom module using python 2. I just did sudo python3 setup.py install and now it's working on the native Ubuntu. I'll now try modifying my docker image and see if it works there too.
Thanks
I am getting this error: signalling support is unavailable because the blinker library is not installed.
I am running Django 1.6.5 under python 2.6.9.
Is it possible that the error will go away if i update python on the server to 2.7.x?
If so how can I update the server without losing everything I have done upto this point creating my website on the instance?
Thanks so much in advance.
Just install blinker by typing pip install blinker in the console.
Be sure you install it in your virtualenv if by any chance you use one, just by activating it before executing the pip command.
You may also review your staging procedure to correctly install project dependencies.
I'm following Heroku's "Getting started with Django on Heroku" article and am getting a long series of errors on "pip install psycopg2". Django 1.4.3 and PostgreSQL 9.2.2 are already installed, and yes, the postgres \bin\ directory is on the PATH.
Any ideas?
It doesn't look like Psycopg on Windows is as simple as using pip. The Psycopg website recommends using these Windows builds.
As a windows users running through the Python Getting Started tutorial on Heroku I ran into a similar issue. I found pycopg2 here: http://www.stickpeople.com/projects/python/win-psycopg/
And then used easy_install in the virtual env directory.