Menu
If I use the following format in my application, everything works, except PyCharms resolving / autocomplete feature:
from flask.ext.sqlalchemy import SQLAlchemy
If I use the following format in my application, everything works. But, alas, it is not the correct way to import the libraries:
from flask_sqlalchemy import SQLAlchemy
Is there any way to make PyCharm resolve the first syntax correctly?
869
One of which is that Flask-SQLAlchemy has its own API. This adds complexity by having its different methods for ORM queries and models separate from the SQLAlchemy API. Another disadvantage is that Flask-SQLAlchemy makes using the database outside of a Flask context difficult.
The Python "ModuleNotFoundError: No module named 'flask_sqlalchemy'" occurs when we forget to install the Flask-SQLAlchemy module before importing it or install it in an incorrect environment. To solve the error, install the module by running the pip install Flask-SQLAlchemy command.
Flask-SQLAlchemy is a Flask extension that makes using SQLAlchemy with Flask easier, providing you tools and methods to interact with your database in your Flask applications through SQLAlchemy. In this tutorial, you'll build a small student management system that demonstrates how to use the Flask-SQLAlchemy extension.
To check which version of sqlalchemy is installed, use pip show sqlalchemy or pip3 show sqlalchemy in your CMD/Powershell (Windows), or terminal (macOS/Linux/Ubuntu) to obtain the output major.
FYI. flask.ext is deprecated, and the right way is:
from flask_sqlalchemy import SQLAlchemy
In case anyone found this SO question on Google.
26
The flask.ext namespace is a transistion namespace, see the Extension Import Transition section of the Flask Extension Development docs:
For a while we recommended using namespace packages for Flask extensions. This turned out to be problematic in practice because many different competing namespace package systems exist and pip would automatically switch between different systems and this caused a lot of problems for users.
and
Flask extensions should urge users to import from
flask.ext.fooinstead offlask_fooorflaskext_fooso that extensions can transition to the new package name without affecting users.
So to transition between versions, the flask.ext alias was added, which will automatically try to import flask_[name] packages when importing flask.ext.[name]. But that transition is now moot; you no longer will find packages that still rely solely on flask.ext.
As such, it is perfectly fine to use the actual module name and have PyCharm autocomplete the module contents.
You only really have to use flask.ext if you are still using an older version of the extension and need to be future compatible. That future is already here.
142
Use a virtualenv and set that virtualenv for your project in PyCharm. I had the same problem as you do and after setting the correct virtualenv (which contains the flask and flask_sqlalchemy extension) my problem is solved.
To set a virtualenv for your project in PyCharm (from JetBrains Web Help):
To add an existing virtual environment to the list of available interpreters In the Project Interpreter page of the project settings, click
. In the drop-down list, choose Add local.
In the Select Python Interpreter dialog box that opens, choose the desired Python executable, and click OK.
Moreover try adding requirements.txt to the root of your project, afterward PyCharm will notify you to install missing dependencies which might help.
32
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
