Upgrade to dj-stripe 1.2.4

.gitignore

@@ -43,6 +43,7 @@ nosetests.xml
 
 # Sphinx
 docs/_build
+docs/_static
 htmlcov
 
 # OSX

.travis.yml

@@ -20,6 +20,7 @@ env:
   - TOXENV=py36-djangomaster
   - TOXENV=checkmigrations
   - TOXENV=flake8
+  - TOXENV=docs
 
 matrix:
   fast_finish: true

CONTRIBUTING.rst

@@ -39,10 +39,9 @@ dj-stripe could always use more documentation, whether as part of the
 official dj-stripe docs, in docstrings, or even on the web in blog posts,
 articles, and such.
 
-If you are adding to dj-stripe's documentation, you can see your changes by changing
-into the ``docs`` directory, running ``make html`` (or ``make.bat html`` if you're
-developing on Windows) from the command line, and then opening ``docs/_build/html/index.html``
-in a web browser.
+If you are adding to dj-stripe's documentation, you can see your changes by
+running ``tox -e docs``. The documentation will be generated in the ``docs/``
+directory, and you can open ``docs/_build/html/index.html`` in a web browser.
 
 Submit Feedback
 ~~~~~~~~~~~~~~~

HISTORY.rst

@@ -3,6 +3,143 @@
 History
 =======
 
+1.2.4 (2019-02-27)
+------------------
+
+This is a bugfix-only version:
+
+- Allow billing_cycle_anchor argument when creating a subscription (#814)
+- Fixup plan amount null with tier plans (#781)
+- Update Cancel subscription view tests to match backport in f64af57
+- Implement Invoice._manipulate_stripe_object_hook for compatability with API 2018-11-08 (#771)
+- Fix product webhook for type="good" (#724)
+- Add trial_from_plan, trial_period_days args to Customer.subscribe() (#709)
+
+
+1.2.3 (2018-10-13)
+------------------
+
+This is a bugfix-only version:
+
+- Updated Subscription.cancel() for compatibility with Stripe 2018-08-23 (#723)
+
+
+1.2.2 (2018-08-11)
+------------------
+
+This is a bugfix-only version:
+
+- Fixed an error with request.urlconf in some setups (#562)
+- Always save text-type fields as empty strings in db instead of null (#713)
+- Fix support for DJSTRIPE_SUBSCRIBER_MODEL_MIGRATION_DEPENDENCY (#707)
+- Fix reactivate() with Stripe API 2018-02-28 and above
+
+
+1.2.1 (2018-07-18)
+------------------
+
+This is a bugfix-only version:
+
+- Fixed various Python 2.7 compatibility issues
+- Fixed issues with max_length of receipt_number
+- Fixed various fields incorrectly marked as required
+- Handle product webhook calls
+- Fix compatibility with stripe-python 2.0.0
+
+
+1.2.0 (2018-06-11)
+------------------
+
+The dj-stripe 1.2.0 release resets all migrations.
+
+**Do not upgrade to 1.2.0 directly from 1.0.1 or below.
+You must upgrade to 1.1.0 first.**
+
+Please read the 1.1.0 release notes below for more information.
+
+
+1.1.0 (2018-06-11)
+------------------
+
+In dj-stripe 1.1.0, we made a *lot* of changes to models in order to
+bring the dj-stripe model state much closer to the upstream API objects.
+If you are a current user of dj-stripe, you will most likely have to
+make changes in order to upgrade. Please read the full changelog below.
+If you are having trouble upgrading, you may ask for help `by filing an
+issue on GitHub`_.
+
+Upgrade notes
+-------------
+
+Migration reset
+~~~~~~~~~~~~~~~
+
+The next version of dj-stripe, **1.2.0**, will reset all the migrations
+to ``0001_initial``. Migrations are currently in an unmaintainable
+state.
+
+**What this means is you will not be able to upgrade directly to
+dj-stripe 1.2.0. You must go through 1.1.0 first, run
+``manage.py migrate djstripe``, then upgrade to 1.2.0.**
+
+Python 2.7 end-of-life
+~~~~~~~~~~~~~~~~~~~~~~
+
+dj-stripe 1.1.0 drops support for Django 1.10 and adds support for
+Django 2.0. Django 1.11+ and Python 2.7+ or 3.4+ are required.
+
+Support for Python versions older than 3.5, and Django versions older
+than 2.0, will be dropped in dj-stripe 1.3.0.
+
+Backwards-incompatible changes and deprecations
+-----------------------------------------------
+
+Removal of polymorphic models
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The model architecture of dj-stripe has been simplified. Polymorphic
+models have been dropped and the old base StripeCustomer, StripeCharge,
+StripeInvoice, etc models have all been merged into the top-level
+Customer, Charge, Invoice, etc models.
+
+Importing those legacy models from ``djstripe.stripe_objects`` will
+yield the new ones. This is deprecated and support for this will be
+dropped in dj-stripe 1.3.0.
+
+Full support for Stripe Sources (Support for v3 stripe.js)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Stripe sources (``src_XXXX``) are objects that can arbitrarily reference
+any of the payment method types that Stripe supports. However, the
+legacy ``Card`` object (with object IDs like ``card_XXXX`` or
+``cc_XXXX``) is not a Source object, and cannot be turned into a Source
+object at this time. In order to support both Card and Source objects in
+ForeignKeys, a new model ``PaymentMethod`` has been devised. That model
+can resolve into a Card, a Source, or a BankAccount object.
+
+-  **The ``default_source`` attribute on ``Customer`` now refers to a
+   ``PaymentMethod`` object**. You will need to call ``.resolve()`` on
+   it to get the Card or Source in question.
+-  References to ``Customer.sources`` expecting a queryset of Card
+   objects should be updated to ``Customer.legacy_cards``.
+-  The legacy ``StripeSource`` name refers to the ``Card`` model. This
+   will be removed in dj-stripe 1.3.0. Update your references to either
+   ``Card`` or ``Source``.
+-  ``enums.SourceType`` has been renamed to ``enums.LegacySourceType``.
+   ``enums.SourceType`` now refers to the actual Stripe Source types
+   enum.
+
+Core fields renamed
+~~~~~~~~~~~~~~~~~~~
+
+-  The numeric ``id`` field has been renamed to ``djstripe_id``. This
+   avoids a clash with the upstream stripe id. Accessing ``.id`` is
+   deprecated and \**will reference the upstream ``stripe_id`` in
+   dj-stripe 1.3.0
+
+.. _by filing an issue on GitHub: https://github.com/dj-stripe/dj-stripe/issues
+
+
 1.0.0 (2017-08-12)
 ------------------
 

README.rst

@@ -39,13 +39,13 @@ Features
 * Single-unit purchases
 * Works with Django >= 1.11
 * Works with Python 3.6, 3.5, 3.4, 2.7
+* Compatible with Stripe API version 2018-05-21
 * Built-in migrations
 * Dead-Easy installation
 * Leverages the best of the 3rd party Django package ecosystem
 * `djstripe` namespace so you can have more than one payments related app
 * Documented
 * 100% Tested
-* Current API version (2017-06-05), in progress of being updated
 
 Constraints
 ------------

djstripe/__init__.py

@@ -6,18 +6,30 @@
 from __future__ import absolute_import, division, print_function, unicode_literals
 import pkg_resources
 
-import stripe
-
-from . import checks  # noqa: Register the checks
+from django.apps import AppConfig
 
 
 __version__ = pkg_resources.require("dj-stripe")[0].version
 
+default_app_config = "djstripe.DjstripeAppConfig"
+
+
+class DjstripeAppConfig(AppConfig):
+    """
+    An AppConfig for dj-stripe which loads system checks
+    and event handlers once Django is ready.
+    """
+
+    name = "djstripe"
+
+    def ready(self):
+        import stripe
+        from . import checks, event_handlers  # noqa: Register the checks and event handlers
 
-# Set app info
-# https://stripe.com/docs/building-plugins#setappinfo
-stripe.set_app_info(
-    "dj-stripe",
-    version=__version__,
-    url="https://github.com/dj-stripe/dj-stripe"
-)
+        # Set app info
+        # https://stripe.com/docs/building-plugins#setappinfo
+        stripe.set_app_info(
+            "dj-stripe",
+            version=__version__,
+            url="https://github.com/dj-stripe/dj-stripe"
+        )