Skip to content

Update to Django 4.0#34

Merged
timgraham merged 1 commit intomasterfrom
django40
Feb 18, 2023
Merged

Update to Django 4.0#34
timgraham merged 1 commit intomasterfrom
django40

Conversation

@timgraham
Copy link
Collaborator

@timgraham timgraham commented Dec 5, 2021

No description provided.

@timgraham timgraham force-pushed the django40 branch 2 times, most recently from 805609f to 2be8151 Compare December 5, 2021 23:03
@timgraham timgraham force-pushed the django40 branch 2 times, most recently from cd6c889 to aad9aae Compare March 7, 2022 00:57
@itsthejoker
Copy link

@timgraham Hi, is there anything waiting on merging this?

@timgraham
Copy link
Collaborator Author

Hi Joe, I'm not presently contracted to maintain this project, however there's a company working on the details to sponsor me, so hopefully they'll come through and I'll be able to continue with this. I haven't done extensive testing with Django 4.0. This was a quick test to check if any major changes were required. It looks like the answer is 'no', but I wasn't able to finish checking all of Django's test suite before my last contract ran out (#32 covers some of that).

@mwisconsin
Copy link

@timgraham Any motion on this? It's been nearly a year, and while my company has a homebrew version of a django-snowflake connection, this repo is considerably more robust. The challenge we're facing is that we've now upgraded to Django 4.x

@timgraham
Copy link
Collaborator Author

The problem remains that no one has offered to sponsor continued work here.

@timgraham timgraham merged commit eabc290 into master Feb 18, 2023
@timgraham timgraham deleted the django40 branch February 18, 2023 00:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants