Version 2.7.0-v2-20.3.00 release (#91)

Co-authored-by: DevCenter-DocuSign <dcdev@docusign.com>

Author: harsharahul

.swagger-codegen-ignore

@@ -36,7 +36,7 @@ LICENSE
 requirements.txt
 test-requirements.txt
 setup.cfg
-setup.py
+#setup.py
 
 
 # Specific src and test files

CHANGELOG.md

@@ -3,6 +3,11 @@ All notable changes to this project will be documented in this file.
 
 See [DocuSign Support Center](https://support.docusign.com/en/releasenotes/) for Product Release Notes.
 
+## [2.7.0] - eSignature API v2-20.3.00 - 2020-09-24
+### Changed
+*   Added support for version v2-20.3.00 of the DocuSign eSignature API.
+*   Updated the SDK release version.
+
 ## [2.6.0] - eSignature API v2-20.2.02.02 - 2020-08-21
 ### Changed
 *   Added support for version v2-20.2.02.02 of the DocuSign eSignature API.

README.md

@@ -10,7 +10,7 @@
 
 ## Requirements
 
-- Python 2.7 (3.6+ recommended)
+- Python 2.7 (3.7+ recommended)
 - Free [Developer Sandbox](https://go.docusign.com/sandbox/productshot/?elqCampaignId=16531)
 
 ## Compatibility
@@ -37,7 +37,7 @@ This open-source SDK is provided for cases where you would like to make addition
 
 **Unix/Linux:**
 
-- Type the following command into your console:  
+- Type the following command into your console:
    **export PYTHONPATH = "${PYTHONPATH}:.:/path/to/site-packages"**
 - Optionally, you can add this command to your system profile, which will run the command each time Python is launched.
 
@@ -80,7 +80,7 @@ This client has the following external dependencies:
 
 ### Launchers
 
-DocuSign provides a sample application referred to as a [Launcher](https://github.com/docusign/eg-03-python-auth-code-grant). The Launcher contains a set of 14 common use cases and associated source files. These examples use DocuSign's [Authorization Code Grant](https://developers.docusign.com/esign-rest-api/guides/authentication/oauth2-code-grant) flow.
+DocuSign provides a sample application code referred to as a [Launcher](https://github.com/docusign/code-examples-python). The Launcher contains a set of 31 common use cases and associated source files. These examples use either DocuSign's [Authorization Code Grant](https://developers.docusign.com/esign-rest-api/guides/authentication/oauth2-code-grant) or [JSON Web Tokens (JWT)](https://developers.docusign.com/esign-rest-api/guides/authentication/oauth2-jsonwebtoken) flows.
 
 ## Proof-of-concept applications
 
@@ -92,10 +92,6 @@ For details regarding which type of OAuth grant will work best for your DocuSign
 
 For security purposes, DocuSign recommends using the [Authorization Code Grant](https://developers.docusign.com/esign-rest-api/guides/authentication/oauth2-code-grant) flow.
 
-There are other use-case scenarios, such as **single-page applications** (SPA) that use **Cross-Origin Resource Sharing** (CORS), or where there may not be a user to interact with your Service Account. For these use cases, DocuSign also supports [JWT](https://developers.docusign.com/esign-rest-api/guides/authentication/oauth2-jsonwebtoken) and [Implicit](https://developers.docusign.com/esign-rest-api/guides/authentication/oauth2-implicit) grants. For code examples, see the links below:
-
-- [JWT (JSON Web Token)](https://github.com/docusign/eg-01-python-jwt)
-- Implicit Grant (coming soon)
 
 ## Support
 
@@ -112,3 +108,9 @@ The DocuSign Python Client is licensed under the [MIT License](https://github.co
 [downloads-url]: https://pypi.python.org/pypi/docusign_esign
 [travis-image]: https://img.shields.io/travis/docusign/docusign-python-client.svg?style=flat
 [travis-url]: https://travis-ci.org/docusign/docusign-python-client
+
+### Additional Resources
+* [DocuSign Developer Center](https://developers.docusign.com)
+* [DocuSign API on Twitter](https://twitter.com/docusignapi)
+* [DocuSign For Developers on LinkedIn](https://www.linkedin.com/showcase/docusign-for-developers/)
+* [DocuSign For Developers on YouTube](https://www.youtube.com/channel/UCJSJ2kMs_qeQotmw4-lX2NQ)

requirements.txt

@@ -6,3 +6,4 @@ urllib3 >= 1.15
 PyJWT>=1.7.1
 cryptography>=2.5
 nose>=1.3.7
+importlib-metadata<2,>=0.12

setup.py

@@ -14,15 +14,16 @@
 from setuptools import setup, find_packages, Command, os  # noqa: H301
 
 NAME = "docusign_esign"
-VERSION = "2.7.0rc1"
+VERSION = "2.7.0"
 # To install the library, run the following
 #
 # python setup.py install
 #
 # prerequisite: setuptools
 # http://pypi.python.org/pypi/setuptools
 
-REQUIRES = ["urllib3 >= 1.15", "six >= 1.8.0", "certifi >= 14.05.14", "python-dateutil >= 2.5.3", "setuptools >= 21.0.0", "PyJWT>=1.7.1", "cryptography>=2.5", "nose>=1.3.7"]
+REQUIRES = ["urllib3 >= 1.15", "six >= 1.8.0", "certifi >= 14.05.14", "python-dateutil >= 2.5.3",
+            "setuptools >= 21.0.0", "PyJWT>=1.7.1", "cryptography>=2.5", "nose>=1.3.7", "importlib-metadata<2,>=0.12"]
 
 class CleanCommand(Command):
     """Custom clean command to tidy up the project root."""

test/unit_tests.py

@@ -707,10 +707,10 @@ def testMoveEnvelopes(self):
             folders_api.move_envelopes(self.user_info.accounts[0].account_id, to_folder_id,
                                        folders_request=folders_request)
 
-            # Wait for 3 second to make sure the newly created envelope was moved to the 'sentitems' folder
+            # Wait for 5 second to make sure the newly created envelope was moved to the 'sentitems' folder
             # Note: It's discouraged to use sleep statement or to poll DocuSign for envelope status or folder id
             # In production, use DocuSign Connect to get notified when the status of the envelope have changed.
-            sleep(3)
+            sleep(5)
             # Test if we moved the envelope to the correct folder
             list_from_drafts_folder = folders_api.list_items(self.user_info.accounts[0].account_id, to_folder_id)