Coverage decreased (-0.2%) to 67.62% when pulling 72a8383 on Sapbasu15:future into 0d238cb on AuthorizeNet:future.

Why do you decide to do this? It is bad practice.

Don't add versions for requests, lxml, nose, mock. You will create problems for users. You must set the versions of packages in install_requires section only if you know that your app does not work with that versions of apps. install_requires section is for restrictions for app. So users who have version 2.18.5 or 2.18.3 of requests package can not use your app???

Example 1. Maintainers of requests package will make release with new version 2.18.5 tomorrow with small changes in docs. But your package will have restriction 'requests==2.18.4'. Why users can not use new version of requests package? Or you want to update your package on any new release of related packages?

Example 2. Users can use many packages in one project. You added restriction: 'requests==2.18.4'. If owners of other packages will use your practice then user can have 5-10 packages with "requests" in their "install_requires" with different versions. One of the packages of project can not work with requests with version 2.18.4, but can work with 2.18.3, but your package has 2.18.4... Why do you restrict this user? Because your app can work with version 2.18.3

If you want to add versions to install_requires, please do it in this way (example):

install_requires=['pyxb==1.2.5', 'lxml>=4.0.0', 'requests>=2.0.0'],

Don't restrict users to only one certain version of package!

@predatell we'll be allowing the version range but with the same major version as the major version change risks backward compatibility. We'll have to manually test and update before a dependency major version is upgraded.