Postgres backend throws error when coercing psycopg2 version string to int when version contains non-numeric characters

[Ryan Bagwell]

The postgres backend that ships with Django expects the version string of psycopg2 to contain numeric characters. It then tries to coerce the string to a tuple, i.e. (2, 5, 4,) for '2.5.4'. This throws an error when using the development branch, which has a version string of '2.6.dev0' (you can't coerce "dev0" to a string.

The problem method is located here:

​https://github.com/django/django/blob/master/django/db/backends/postgresql_psycopg2/base.py#L202

@cached_property
def psycopg2_version(self):
    version = psycopg2.__version__.split(' ', 1)[0]
    return tuple(int(v) for v in version.split('.'))

This was a problem for me due to a bug in psycopg2 that was fixed in the dev branch but not in the most recent release.

I don't know how best to address it. Do other applications expect the version tuple to consist entirely of integers?

[Tim Graham]

It seems like a reasonable request. You could look at the strategies use by other database backends in Django (regular expressions in MySQL, for example). It might also be fine simply to discard the value that can't be parsed.

[Tim Graham <timograham@…>]

In 1739ae9edc6e6c07ca20cad36dd15316f18f3f8e:

Fixed #23807 -- Ignored non-digits in psycopg2 version