Remove __future__
imports and use generated sections in object_classes.py
#1069
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR:
from __future__ import absolute_import, division, print_function
imports. These imports are no longer necessary, as they are used for forwards compatibility with Python 2.x versions and became the default behavior in Python 3.0 (see https://docs.python.org/3/library/__future__.html). Since stripe-python supports Python >=3.6 as of v6.0.0, this is a non-breaking change.stripe/object_classes.py
to use generated sections, allowing us to manually maintain data structure objects likeListObject
(see commit).