for django3.1 - Githubissues

maxtepkeev / architect

A set of tools which enhances ORMs written in Python with more features

Other

391 stars 57 forks source link

for django3.1 #75

Closed wakita181009 closed 4 years ago

wakita181009 commented 4 years ago

FieldDoesNotExist is removed from django.db.models.fields in django3.1.
psql: could not connect to server error on “travis-ci” (https://stackoverflow.com/questions/49850020/psql-could-not-connect-to-server-error-on-travis-ci)
Not to support python 3.2 and 3.3 because these versions haven't already hosted on GCP

cramaker commented 4 years ago

:1st_place_medal: Thanks for this! It'd be great to have the latest Django support

a1tus commented 4 years ago

Is this repo still maintained or our only choice to use a fork?

We use the same import fix as in this PR and it would be nice to merge it and make a release so that people could use pip.

maxtepkeev commented 4 years ago

@wakita181009 Fantastic job, many thanks for this, merging it as it is.

Just one question, what's wrong with pymysql usage for the latest Django in travis ?

a1tus commented 4 years ago

@maxtepkeev great! Are you going to release 0.5.7 with this?

maxtepkeev commented 4 years ago

@a1tus I will, just wanna check a few more things so it might take a few more days.

a1tus commented 4 years ago

@maxtepkeev that's nice, thanks.

wakita181009 commented 3 years ago

@wakita181009 Fantastic job, many thanks for this, merging it as it is.

Just one question, what's wrong with pymysql usage for the latest Django in travis ?

@maxtepkeev I met some errors to use Django>=3.0 and pymysql and also Django recommended to use mysqlclient as MySQL driver. https://docs.djangoproject.com/en/3.1/ref/databases/#mysql-db-api-drivers