django-pgviews
django-pgviews copied to clipboard
mypebble
Django 3.0 and Python 3 Support
We would really like to support Django 3 in out app but use django-pgviews quite alot and it uses on six which is now removed. From what I can tell the only usages are in views.py and I tried working on a PR but I do not quite understand how the six.with_metaclass function works and how to replace it.
If anyone is able to advise me I would be happy to submit a PR.
In case django-pgviews does not want to abandon python 2 support it might be easier to just add six as dependency of django-pgviews and update the import statement.
If python 2 support is not a requirement, six.with_metaclass can simply be replaced with the python 3 way of defining a metaclass.
In case django-pgviews does not want to abandon python 2 support it might be easier to just add six as dependency of django-pgviews and update the import statement.
If python 2 support is not a requirement, six.with_metaclass can simply be replaced with the python 3 way of defining a metaclass.
It seems that the project is dead ... 😔
Which is a real shame as we use it in production quite heavily. I have been using my branch directly for a while but I feel like I need to start looking elsewhere...
Just wait for a new version of https://github.com/SectorLabs/django-postgres-extra Currently v 2.0 is in alpha stage. You may also help @Photonios with testing and other participation in the project.
I needed this quite badly, so I forked this repo and updated it, including tests etc. (Now Python 3.6+ only, Django 2.2+ only). Feel free to use.
The repo: https://github.com/mikicz/django-pgviews PyPI release: https://pypi.org/project/django-pgviews-redux/
Hey all. Apologies for not replying.
I'd recommend using an alternative source for this repo now as I no longer work for the company that maintained this and, as far as I'm aware, maintaining external repos is no longer a priority for the development team.
