CMS is compatible with Python 3.3+, the mysql-python package is not. Before you install the Python adapters for your chosen database, you will need to first install the appropriate headers and development python-pip sudo pip install virtualenv Next, install the appropriate libraries to build the Python adapters for your selected database. For PostgreSQL: 22 Chapter 5. Table of contents django cms Documentation install python pip install virtualenv Next, install the appropriate libraries to build the Python adapters for your selected database. For PostgreSQL: brew install postgres For MySQL: brew install mysql

is compatible with Python 3.3+, the mysql-python package is not. Before you install the Python adapters for your chosen database, you will need to first install the appropriate headers and development python-pip sudo pip install virtualenv Next, install the appropriate libraries to build the Python adapters for your selected database. For PostgreSQL: sudo aptitude install libpq-dev postgresql-client-9 install python pip install virtualenv Next, install the appropriate libraries to build the Python adapters for your selected database. For PostgreSQL: brew install postgres For MySQL: brew install mysql

adapter, and Django won’t help you. Although that behavior is specified in PEP 249, implementations of adapters aren’t always consistent with one another. Review the documentation of the adapter you’re using main thread. The reason this is needed in Django is that many libraries, specifically database adapters, require that they are accessed in the same thread that they were created in. Also a lot of existing with sensitive_variables(), used to mask local variables from exception reports. If using these adapters with sensitive variables, ensure to audit exception reporting, and consider implementing a custom

and Django won’ t help you. Although that behavior is specified in PEP 249, implementations of adapters aren’t always consistent with one another. Review the documentation of the adapter you’re using main thread. The reason this is needed in Django is that many libraries, specifically database adapters, require that they are accessed in the same thread that they were created in. Also a lot of existing with sensitive_variables(), used to mask local variables from exception reports. If using these adapters with sensitive variables, ensure to audit exception reporting, and consider imple- menting a custom

adapter, and Django won’t help you. Although that behavior is specified in PEP 249, implementations of adapters aren’t always consistent with one another. Review the documentation of the adapter you’re using main thread). The reason this is needed in Django is that many libraries, specifically database adapters, require that they are accessed in the same thread that they were created in, and a lot of existing compiling them from source. However, Xcode is still necessary for compiling the Python database adapters psycopg2 (for PostGIS). Note SpatiaLite users should consult the macOS-specific instructions section

adapter, and Django won’t help you. Although that behavior is specified in PEP 249, implementations of adapters aren’t always consistent with one another. Review the documentation of the adapter you’re using main thread. The reason this is needed in Django is that many libraries, specifically database adapters, require that they are accessed in the same thread that they were created in. Also a lot of existing compiling them from source. However, Xcode is still necessary for compiling the Python database adapters psycopg2 (for PostGIS). Note: SpatiaLite users should consult the macOS-specific instructions section

adapter, and Django won’t help you. Although that behavior is specified in PEP 249, implementations of adapters aren’t always consistent with one another. Review the documentation of the adapter you’re using main thread. The reason this is needed in Django is that many libraries, specifically database adapters, require that they are accessed in the same thread that they were created in. Also a lot of existing compiling them from source. However, Xcode is still necessary for compiling the Python database adapters psycopg2 (for PostGIS). Note: SpatiaLite users should consult the macOS-specific instructions section

adapter, and Django won’t help you. Although that behavior is specified in PEP 249, implementations of adapters aren’t always consistent with one another. Review the documentation of the adapter you’re using main thread). The reason this is needed in Django is that many libraries, specifically database adapters, require that they are accessed in the same thread that they were created in, and a lot of existing compiling them from source. However, Xcode is still necessary for compiling the Python database adapters psycopg2 (for PostGIS). Note: SpatiaLite users should consult the macOS-specific instructions section

adapter, and Django won’t help you. Although that behavior is specified in PEP 249, implementations of adapters aren’t always consistent with one another. Review the documentation of the adapter you’re using main thread. The reason this is needed in Django is that many libraries, specifically database adapters, require that they are accessed in the same thread that they were created in. Also a lot of existing compiling them from source. However, Xcode is still necessary for compiling the Python database adapters psycopg2 (for PostGIS). Note: SpatiaLite users should consult the macOS-specific instructions section

adapter, and Django won’t help you. Although that behavior is specified in PEP 249, implementations of adapters aren’t always consistent with one another. Review the documentation of the adapter you’re using main thread. The reason this is needed in Django is that many libraries, specifically database adapters, require that they are accessed in the same thread that they were created in. Also a lot of existing compiling them from source. However, Xcode is still necessary for compiling the Python database adapters psycopg2 (for PostGIS). Note SpatiaLite users should consult the macOS-specific instructions section