Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Django 3.0 compatability #1041

Merged
merged 1 commit into from
Oct 24, 2019

Conversation

therefromhere
Copy link
Contributor

Remove Django 3.0 from allowed failures now that jsonfield2>=3.0.3 supports Django 3.0

Resolves #821

Remove Django 3.0 from allowed failures now that jsonfield2>=3.0.3 supports Django 3.0

Resolves dj-stripe#821
@codecov
Copy link

codecov bot commented Oct 24, 2019

Codecov Report

Merging #1041 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1041   +/-   ##
=======================================
  Coverage   97.52%   97.52%           
=======================================
  Files          25       25           
  Lines        2384     2384           
  Branches      222      222           
=======================================
  Hits         2325     2325           
  Misses         45       45           
  Partials       14       14

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cd4daee...e895ca0. Read the comment docs.

@therefromhere therefromhere merged commit fa4bd5d into dj-stripe:master Oct 24, 2019
@trey
Copy link

trey commented Dec 6, 2019

This is probably a silly question, but how can I get the Django 3.0 compatible version installed in my project? Installing with pip only gives me the 2.1.1 version before these changes.

Thanks for all you do!

@therefromhere
Copy link
Contributor Author

Hi, you can install master, it should be stable. Just be aware that the dev migrations will be squashed before release - see https://dj-stripe.readthedocs.io/en/latest/project/release_process.html#squash-migrations

So once 2.2 is released, if you're upgrading from 2.2dev to 2.2 you'll need to upgrade to 2.2rc first and migrate to update the migration history in your db.

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.

Django 3.0 Compatability
2 participants