| Name | django-informixdb JSON |
| Version |
1.11.5
JSON |
| download |
| home_page | |
| Summary | A database driver for Django to connect to an Informix db via ODBC |
| upload_time | 2023-12-18 23:16:28 |
| maintainer | |
| docs_url | None |
| author | |
| requires_python | |
| license | APLv2 |
| keywords |
django
informix
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
Django InformixDB
==================
A database driver for Django to connect to an Informix database via pyodbc.
**Some limitations**:
- Does not support default values
- Informix automatically creates indexes on foreign keys, but Django attempts to do that
manually; the current implementation here just attempts to catch the error on index
creation. It may unintentionally catch other index creation errors where the index
already exists.
Configure local environment
---------------------------
The following environment variables should exist:
INFORMIXDIR
The path to the Informix client install directory
INFORMIXSERVER
The name of the Informix service to which we need to connect
INFORMIXSQLHOSTS
The path to the ``sqlhosts`` file that the Informix driver should use
LD_LIBRARY_PATH
The path(s) to the various Informix library files: Usually
``$INFORIMIXDIR/lib:$INFORMIXDIR/lib/cli:$IMFORMIXDIR/lib/esql``
DB_LOCALE
In case of ``Database locale information mismatch.`` error during connection,
you should specify your database locale, e.g. ``DB_LOCALE=en_US.8859-15``
You will also need to add an entry within your ``sqlhosts`` file for each remote/local Informix
server connection in the following format::
<INFORMIX_SERVER_NAME> onsoctcp <INFORMIX_HOST_NAME> <INFORMIX_SERVICE_NAME>
For example::
dev onsoctcp localhost 9088
You may alternatively use a symbolic name in that line in place of the port number, typically ``sqlexec`` and
then configure the port number in the ``/etc/services`` file::
sqlexec 9088/tcp
Configure settings.py
---------------------
Django’s settings.py uses the following to connect to an Informix database:
.. code-block:: python
'default': {
'ENGINE': 'django_informixdb',
'NAME': 'myproject',
'SERVER': 'ifxserver',
'USER' : 'testuser',
'PASSWORD': 'passw0rd',
'OPTIONS': {
'DRIVER': '/path/to/iclit09b.so'. # Or iclit09b.dylib on macOS
'CPTIMEOUT': 120,
'CONN_TIMEOUT': 120,
'ISOLATION_LEVEL': 'READ_UNCOMMITTED',
'LOCK_MODE_WAIT': 0,
'VALIDATE_CONNECTION': True,
},
'CONNECTION_RETRY': {
'MAX_ATTEMPTS': 10,
},
'TEST': {
'NAME': 'myproject',
'CREATE_DB': False
}
}
CPTIMEOUT
This will set connection pooling timeout.
Possible values::
0 - Turn off connection pooling
nn - timeout set nn seconds
CONN_TIMEOUT
This will set timeout for operations on connections (connection, ??closing??, we're not sure).
Possible values::
0 - Default timeout to the database (which could mean no timeout)
nn - timeout set nn seconds
ISOLATION_LEVEL
This will set database isolation level at connection level
Possible values::
READ_COMMITED
READ_UNCOMMITTED
SERIALIZABLE
LOCK_MODE_WAIT
This will set database LOCK MODE WAIT at connection level
Application can use this property to override the default server
process for accessing a locked row or table.
The default value is 0 (do not wait for the lock).
Possible values::
-1 - WAIT until the lock is released.
0 - DO NOT WAIT, end the operation, and return with error.
nn - WAIT for nn seconds for the lock to be released.
VALIDATE_CONNECTION
Whether existing connections should be validated at the start of the request. Defaults to
`False`.
VALIDATION_INTERVAL
How often in seconds to revalidate connections if `VALIDATE_CONNECTION` is enabled. Defaults to
`300` (5 minutes).
VALIDATION_QUERY
Query used to validate whether a connection is usable. Defaults to
`"SELECT 1 FROM sysmaster:sysdual"`.
CONNECTION_RETRY
When opening a new connection to the database, automatically retry up to ``MAX_ATTEMPTS`` times
in the case of errors. Only error codes in ``ERRORS`` will trigger a retry. The wait time
between retries is calculated using an exponential backoff with jitter formula::
random_between(WAIT_MIN, min(WAIT_MAX, WAIT_MULTIPLIER * WAIT_EXP_BASE ** (attempt - 1)))
Defaults (wait times are in milliseconds)::
MAX_ATTEMPTS: 1 # this implies no retries
WAIT_MIN: 0
WAIT_MAX: 1000
WAIT_MULTIPLIER: 25
WAIT_EXP_BASE: 2
ERRORS: ['-908', '-930', '-27001']
Each of these settings can be overridden in the ``CONNECTION_RETRY`` section of the database
configuration in ``settings.py``. For example::
DATABASES = {
'default': {
'ENGINE': 'django_informixdb',
'CONNECTION_RETRY': {
'MAX_ATTEMPTS': 10,
'WAIT_MIN': 0,
'WAIT_MAX': 500,
},
# ...
},
}
The error codes that are retried by default correspond to the following errors:
* ``-908 Attempt to connect to database server (servername) failed``
* ``-930 Cannot connect to database server servername``
* ``-27001 Read error occurred during connection attempt``
These errors are often seen when the database server is too busy, too many clients are
attempting to connect at the same time or a network firewall has chopped the connection.
.. note:
The ``DRIVER`` option is optional, default locations will be used per platform if it is not provided.
.. note:
The ``TEST`` option sets test parametes. Use ``NAME`` to override the name of the test database
and set ``CREATE_DB`` to ``False`` to prevent Django from attempting to create a new test
database.
Using with the Docker Informix Dev Database
-------------------------------------------
The docker image from IBM for the Informix developer database image behaves a little differently compared to other images. As such it needs a little extra handling, and doesn't seem to work with docker-compose
Firstly we need to download and getting it running:
.. code-block:: bash
$ docker run -itd --name iif_developer_edition --privileged -p 9088:9088 -p 9089:9089 -p 27017:27017 \
-p 27018:27018 -p 27883:27883 -e LICENSE=accept ibmcom/informix-developer-database:latest
This will download the image if it doesn't exist, and then run it with the name ``iif_developer_edition``. The first time this run, the image will do a bunch of initial setup stuff. As we used the ``-d`` option, it will run in the background as a detached process. So don't be concerned that you do not see anything in the output.
You can stop and restart the container with:
.. code-block:: bash
$ docker stop iif_developer_edition
$ docker start iif_developer_edition
It seems that the Informix ODBC driver does not currently support creating databases. So we will need to do
that manually, by attaching to the running container
.. code-block:: bash
$ docker attach iif_developer_edition
This will give you a shell on the running container, and you can therefore use dbaccess to create your database.
You can exit this shell using ``Ctrl-p`` ``Ctrl-q`` without shutting down the whole container.
This Django database adaptor for Informix requires transaction support to be enabled in our database.
This is not the default within the Informix Developer image. So you need to enable it on a per database basis:
.. code-block:: bash
$ docker attach iif_developer_edition
$ ontape -s -B <DB_NAME>
Again, you can detach using ``Ctrl-p`` ``Ctrl-q``.
Finally you need to ensure that our local dev database is included in the ``sqlhosts`` file. e.g.:
.. code-block:: bash
dev onsoctcp localhost 9088
You should now be able to point Django to our local test database using the syntax detailed above.
Using Django InformixDB with docker-compose
-------------------------------------------
It is possible to use the Informix developer docker image with docker-compose with a little effort.
Example docker-compose.yml
.. code-block:: yaml
version: '3'
services:
db:
image: ibmcom/informix-developer-database
tty: true # Needed to ensure container doesn't self terminate
environment:
LICENSE: accept
privileged: true
ports:
- "9088:9088"
- "9089:9089"
- "27017:27017"
- "27018:27018"
- "27883:27883"
The key entry in the compose file which is out of the ordinary is `tty: true`. This allocates a (virtual) TTY to the container. The Informix developer database container expects a `tty` and terminates without one when run inside docker-compose.
Once it is up and running with `docker-compose up` you can run a `bash` shell on the running container with:
.. code-block:: bash
docker exec -it informix_db_1 bash
Where `informix_db_1` is the name of the running container. From this shell you can create your DB with `dbaccess` etc.
.. warning::
This approach still requires the SDK to installed locally and the appropriate environmental variables to be set up. Along with entries in `sqlhosts` and `/etc/services`
Testing against an Informix Database
------------------------------------
Due to a bug in the Informix ODBC driver, it is not currently possible to run Django tests normally. Specifically, it is not possible for Django to create a test database. As such, you will need to do it manually. By default Django will attempt to create a database with a name equal to the default database name with a ``test_`` prefix. e.g. if you database name is ``my_database``, the test database name would be ``test_my_database``. This can be overridden with the ``NAME`` option under ``TEST``.
To prevent Django from attempting to create a test database, set the ``CREATE_DB`` option
under ``TEST`` to ``False``: see 'Configure settings.py' above.
You can follow the steps above, in the section on using Informix locally with Docker to create a test database. Then when running the test you can tell Django to re-use an existing database, rather than trying to create a new one with the ``-k`` parameter:
.. code-block:: bash
./manage.py test -k
For django_informixdb Developers
--------------------------------
To run the django_informixdb test suite, you need to set the INFORMIXDIR environment variable, and the tests
expect an Informix database at host "informix". Change that host in `test/conftest.py` if you need to.
Then run the test suite with:
tox
This will run the tests under Django 3 and 4.
Docker based testing
^^^^^^^^^^^^^^^^^^^^
If you don't want to install the Informix libraries and multiple versions of Python locally, then you can test within
Docker containers.
Try using the helper script `test-in-docker.sh`, or inspect the script and adapt for your own purposes.
Requirements: Docker 19.03.2 or newer and Docker Compose 1.24.1 or newer.
Release History
---------------
Version 1.11.4
- Update pyproject.toml / setup.cfg and update docker tests to use Rocky9 instead of Centos7
Version 1.11.3
- Switch from setup.py to pyproject.toml / setup.cfg
Version 1.11.2
- Begin support for Python 3.10
Version 1.11.1
- Convert from TravisCI to GitHub Actions
Version 1.11.0
- Begin support for Django 4.x
- End support for Django 2.x
- End support for Python 3.6
Version 1.10.1
- Fix for https://github.com/reecetech/django_informixdb/issues/31
Version 1.10.0
- Begin support for Django 3.x
- Begin support for Python 3.9
Version 1.9.1
- Begin support for Python 3.7 and 3.8
- End support for Django 1.x and Python 3.5
Version 1.9.0
- Enable setting a validation interval.
Version 1.8.0
- Enable validating connections at start of request.
Version 1.7.0
- Add CONN_TIMEOUT setting.
Version 1.5.0
- Enable retrying if get connection fails.
Version 1.3.3
- Compability fix for Django 2+ to remove old "context" argument from
custom fields
Version 1.3.0
- Addressing deprecation warning for conversion functions in Django 2+
- Detect incorrect INFORMIXSQLHOSTS setting earlier for better error message
Version 1.2.0
- Fix bug in DecimalField handling under Django 2+
Version 1.1.0
- Added LOCK_MODE_WAIT option
Version 1.0.0
- Initial public release
Raw data
{
"_id": null,
"home_page": "",
"name": "django-informixdb",
"maintainer": "",
"docs_url": null,
"requires_python": "",
"maintainer_email": "",
"keywords": "django,informix",
"author": "",
"author_email": "Reecetech <opensource@reecetech.com.au>",
"download_url": "https://files.pythonhosted.org/packages/a4/ab/6db09eb9d6ac2547ca603cf4d3f4414de636fbca471a89dc16739307a755/django_informixdb-1.11.5.tar.gz",
"platform": null,
"description": "Django InformixDB\n==================\n\nA database driver for Django to connect to an Informix database via pyodbc.\n\n**Some limitations**:\n\n- Does not support default values\n- Informix automatically creates indexes on foreign keys, but Django attempts to do that\n manually; the current implementation here just attempts to catch the error on index\n creation. It may unintentionally catch other index creation errors where the index\n already exists.\n\n\nConfigure local environment\n---------------------------\n\nThe following environment variables should exist:\n\nINFORMIXDIR\n The path to the Informix client install directory\n\nINFORMIXSERVER\n The name of the Informix service to which we need to connect\n\nINFORMIXSQLHOSTS\n The path to the ``sqlhosts`` file that the Informix driver should use\n\nLD_LIBRARY_PATH\n The path(s) to the various Informix library files: Usually\n ``$INFORIMIXDIR/lib:$INFORMIXDIR/lib/cli:$IMFORMIXDIR/lib/esql``\n\nDB_LOCALE\n In case of ``Database locale information mismatch.`` error during connection,\n you should specify your database locale, e.g. ``DB_LOCALE=en_US.8859-15``\n\nYou will also need to add an entry within your ``sqlhosts`` file for each remote/local Informix\nserver connection in the following format::\n\n <INFORMIX_SERVER_NAME> onsoctcp <INFORMIX_HOST_NAME> <INFORMIX_SERVICE_NAME>\n\nFor example::\n\n dev onsoctcp localhost 9088\n\nYou may alternatively use a symbolic name in that line in place of the port number, typically ``sqlexec`` and\nthen configure the port number in the ``/etc/services`` file::\n\n sqlexec 9088/tcp\n\n\nConfigure settings.py\n---------------------\n\nDjango\u2019s settings.py uses the following to connect to an Informix database:\n\n.. code-block:: python\n\n 'default': {\n 'ENGINE': 'django_informixdb',\n 'NAME': 'myproject',\n 'SERVER': 'ifxserver',\n 'USER' : 'testuser',\n 'PASSWORD': 'passw0rd',\n 'OPTIONS': {\n 'DRIVER': '/path/to/iclit09b.so'. # Or iclit09b.dylib on macOS\n 'CPTIMEOUT': 120,\n 'CONN_TIMEOUT': 120,\n 'ISOLATION_LEVEL': 'READ_UNCOMMITTED',\n 'LOCK_MODE_WAIT': 0,\n 'VALIDATE_CONNECTION': True,\n },\n 'CONNECTION_RETRY': {\n 'MAX_ATTEMPTS': 10,\n },\n 'TEST': {\n 'NAME': 'myproject',\n 'CREATE_DB': False\n }\n }\n\nCPTIMEOUT\n This will set connection pooling timeout.\n Possible values::\n\n 0 - Turn off connection pooling\n nn - timeout set nn seconds\n\nCONN_TIMEOUT\n This will set timeout for operations on connections (connection, ??closing??, we're not sure).\n Possible values::\n\n 0 - Default timeout to the database (which could mean no timeout)\n nn - timeout set nn seconds\n\nISOLATION_LEVEL\n This will set database isolation level at connection level\n Possible values::\n\n READ_COMMITED\n READ_UNCOMMITTED\n SERIALIZABLE\n\nLOCK_MODE_WAIT\n This will set database LOCK MODE WAIT at connection level\n Application can use this property to override the default server\n process for accessing a locked row or table.\n The default value is 0 (do not wait for the lock).\n Possible values::\n\n -1 - WAIT until the lock is released.\n 0 - DO NOT WAIT, end the operation, and return with error.\n nn - WAIT for nn seconds for the lock to be released.\n\nVALIDATE_CONNECTION\n Whether existing connections should be validated at the start of the request. Defaults to\n `False`.\n\nVALIDATION_INTERVAL\n How often in seconds to revalidate connections if `VALIDATE_CONNECTION` is enabled. Defaults to\n `300` (5 minutes).\n\nVALIDATION_QUERY\n Query used to validate whether a connection is usable. Defaults to\n `\"SELECT 1 FROM sysmaster:sysdual\"`.\n\nCONNECTION_RETRY\n When opening a new connection to the database, automatically retry up to ``MAX_ATTEMPTS`` times\n in the case of errors. Only error codes in ``ERRORS`` will trigger a retry. The wait time\n between retries is calculated using an exponential backoff with jitter formula::\n\n random_between(WAIT_MIN, min(WAIT_MAX, WAIT_MULTIPLIER * WAIT_EXP_BASE ** (attempt - 1)))\n\n Defaults (wait times are in milliseconds)::\n\n MAX_ATTEMPTS: 1 # this implies no retries\n WAIT_MIN: 0\n WAIT_MAX: 1000\n WAIT_MULTIPLIER: 25\n WAIT_EXP_BASE: 2\n ERRORS: ['-908', '-930', '-27001']\n\n Each of these settings can be overridden in the ``CONNECTION_RETRY`` section of the database\n configuration in ``settings.py``. For example::\n\n DATABASES = {\n 'default': {\n 'ENGINE': 'django_informixdb',\n 'CONNECTION_RETRY': {\n 'MAX_ATTEMPTS': 10,\n 'WAIT_MIN': 0,\n 'WAIT_MAX': 500,\n },\n # ...\n },\n }\n\n The error codes that are retried by default correspond to the following errors:\n\n * ``-908 Attempt to connect to database server (servername) failed``\n * ``-930 Cannot connect to database server servername``\n * ``-27001 Read error occurred during connection attempt``\n\n These errors are often seen when the database server is too busy, too many clients are\n attempting to connect at the same time or a network firewall has chopped the connection.\n\n\n.. note:\n The ``DRIVER`` option is optional, default locations will be used per platform if it is not provided.\n\n.. note:\n The ``TEST`` option sets test parametes. Use ``NAME`` to override the name of the test database\n and set ``CREATE_DB`` to ``False`` to prevent Django from attempting to create a new test\n database.\n\nUsing with the Docker Informix Dev Database\n-------------------------------------------\n\nThe docker image from IBM for the Informix developer database image behaves a little differently compared to other images. As such it needs a little extra handling, and doesn't seem to work with docker-compose\n\nFirstly we need to download and getting it running:\n\n.. code-block:: bash\n\n $ docker run -itd --name iif_developer_edition --privileged -p 9088:9088 -p 9089:9089 -p 27017:27017 \\\n -p 27018:27018 -p 27883:27883 -e LICENSE=accept ibmcom/informix-developer-database:latest\n\nThis will download the image if it doesn't exist, and then run it with the name ``iif_developer_edition``. The first time this run, the image will do a bunch of initial setup stuff. As we used the ``-d`` option, it will run in the background as a detached process. So don't be concerned that you do not see anything in the output.\n\nYou can stop and restart the container with:\n\n.. code-block:: bash\n\n $ docker stop iif_developer_edition\n $ docker start iif_developer_edition\n\nIt seems that the Informix ODBC driver does not currently support creating databases. So we will need to do\nthat manually, by attaching to the running container\n\n.. code-block:: bash\n\n $ docker attach iif_developer_edition\n\n\nThis will give you a shell on the running container, and you can therefore use dbaccess to create your database.\nYou can exit this shell using ``Ctrl-p`` ``Ctrl-q`` without shutting down the whole container.\n\nThis Django database adaptor for Informix requires transaction support to be enabled in our database.\nThis is not the default within the Informix Developer image. So you need to enable it on a per database basis:\n\n.. code-block:: bash\n\n $ docker attach iif_developer_edition\n $ ontape -s -B <DB_NAME>\n\nAgain, you can detach using ``Ctrl-p`` ``Ctrl-q``.\n\nFinally you need to ensure that our local dev database is included in the ``sqlhosts`` file. e.g.:\n\n.. code-block:: bash\n\n dev onsoctcp localhost 9088\n\nYou should now be able to point Django to our local test database using the syntax detailed above.\n\n\nUsing Django InformixDB with docker-compose\n-------------------------------------------\n\nIt is possible to use the Informix developer docker image with docker-compose with a little effort.\n\nExample docker-compose.yml\n\n.. code-block:: yaml\n\n version: '3'\n\n services:\n db:\n image: ibmcom/informix-developer-database\n tty: true # Needed to ensure container doesn't self terminate\n environment:\n LICENSE: accept\n privileged: true\n ports:\n - \"9088:9088\"\n - \"9089:9089\"\n - \"27017:27017\"\n - \"27018:27018\"\n - \"27883:27883\"\n\n\nThe key entry in the compose file which is out of the ordinary is `tty: true`. This allocates a (virtual) TTY to the container. The Informix developer database container expects a `tty` and terminates without one when run inside docker-compose.\n\nOnce it is up and running with `docker-compose up` you can run a `bash` shell on the running container with:\n\n.. code-block:: bash\n\n docker exec -it informix_db_1 bash\n\n\nWhere `informix_db_1` is the name of the running container. From this shell you can create your DB with `dbaccess` etc.\n\n.. warning::\n\n This approach still requires the SDK to installed locally and the appropriate environmental variables to be set up. Along with entries in `sqlhosts` and `/etc/services`\n\n\nTesting against an Informix Database\n------------------------------------\n\nDue to a bug in the Informix ODBC driver, it is not currently possible to run Django tests normally. Specifically, it is not possible for Django to create a test database. As such, you will need to do it manually. By default Django will attempt to create a database with a name equal to the default database name with a ``test_`` prefix. e.g. if you database name is ``my_database``, the test database name would be ``test_my_database``. This can be overridden with the ``NAME`` option under ``TEST``.\n\nTo prevent Django from attempting to create a test database, set the ``CREATE_DB`` option\nunder ``TEST`` to ``False``: see 'Configure settings.py' above.\n\nYou can follow the steps above, in the section on using Informix locally with Docker to create a test database. Then when running the test you can tell Django to re-use an existing database, rather than trying to create a new one with the ``-k`` parameter:\n\n.. code-block:: bash\n\n ./manage.py test -k\n\n\nFor django_informixdb Developers\n--------------------------------\n\nTo run the django_informixdb test suite, you need to set the INFORMIXDIR environment variable, and the tests\nexpect an Informix database at host \"informix\". Change that host in `test/conftest.py` if you need to.\nThen run the test suite with:\n\n tox\n\nThis will run the tests under Django 3 and 4.\n\n\nDocker based testing\n^^^^^^^^^^^^^^^^^^^^\n\nIf you don't want to install the Informix libraries and multiple versions of Python locally, then you can test within\nDocker containers.\n\nTry using the helper script `test-in-docker.sh`, or inspect the script and adapt for your own purposes.\n\nRequirements: Docker 19.03.2 or newer and Docker Compose 1.24.1 or newer.\n\n\nRelease History\n---------------\n\nVersion 1.11.4\n\n- Update pyproject.toml / setup.cfg and update docker tests to use Rocky9 instead of Centos7\n\nVersion 1.11.3\n\n- Switch from setup.py to pyproject.toml / setup.cfg\n\nVersion 1.11.2\n\n- Begin support for Python 3.10\n\nVersion 1.11.1\n\n- Convert from TravisCI to GitHub Actions\n\nVersion 1.11.0\n\n- Begin support for Django 4.x\n- End support for Django 2.x\n- End support for Python 3.6\n\nVersion 1.10.1\n\n- Fix for https://github.com/reecetech/django_informixdb/issues/31\n\nVersion 1.10.0\n\n- Begin support for Django 3.x\n- Begin support for Python 3.9\n\nVersion 1.9.1\n\n- Begin support for Python 3.7 and 3.8\n- End support for Django 1.x and Python 3.5\n\nVersion 1.9.0\n\n- Enable setting a validation interval.\n\nVersion 1.8.0\n\n- Enable validating connections at start of request.\n\nVersion 1.7.0\n\n- Add CONN_TIMEOUT setting.\n\nVersion 1.5.0\n\n- Enable retrying if get connection fails.\n\nVersion 1.3.3\n\n- Compability fix for Django 2+ to remove old \"context\" argument from\n custom fields\n\nVersion 1.3.0\n\n- Addressing deprecation warning for conversion functions in Django 2+\n- Detect incorrect INFORMIXSQLHOSTS setting earlier for better error message\n\nVersion 1.2.0\n\n- Fix bug in DecimalField handling under Django 2+\n\nVersion 1.1.0\n\n- Added LOCK_MODE_WAIT option\n\nVersion 1.0.0\n\n- Initial public release\n",
"bugtrack_url": null,
"license": "APLv2",
"summary": "A database driver for Django to connect to an Informix db via ODBC",
"version": "1.11.5",
"project_urls": {
"Homepage": "https://github.com/reecetech/django_informixdb",
"Repository": "https://github.com/reecetech/django_informixdb"
},
"split_keywords": [
"django",
"informix"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "a4ab6db09eb9d6ac2547ca603cf4d3f4414de636fbca471a89dc16739307a755",
"md5": "724e3c9401bb9674c93e4da8eec5b3e7",
"sha256": "0e67bdf0365765d9c2ab7241cd0b706a64dcb05da9ec6223dbac03673bfc03ca"
},
"downloads": -1,
"filename": "django_informixdb-1.11.5.tar.gz",
"has_sig": false,
"md5_digest": "724e3c9401bb9674c93e4da8eec5b3e7",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 31032,
"upload_time": "2023-12-18T23:16:28",
"upload_time_iso_8601": "2023-12-18T23:16:28.175170Z",
"url": "https://files.pythonhosted.org/packages/a4/ab/6db09eb9d6ac2547ca603cf4d3f4414de636fbca471a89dc16739307a755/django_informixdb-1.11.5.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-12-18 23:16:28",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "reecetech",
"github_project": "django_informixdb",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"tox": true,
"lcname": "django-informixdb"
}
