GitHub user cgtx opened a pull request:

    https://github.com/apache/libcloud/pull/486

    Consistent logic for dependencies resolution

    Different versions of Python have different dependencies.  These differences
    are parsed in various ways.  This pull request establishes a consistent 
method
    for setting dependencies per version.
    
    In addition, the code from `backports.ssl_match_hostname` has been merged 
into
    the standard library in Python 2.7.9.  The condition for adding that 
dependency
    now takes into account that fact.
    
    https://www.python.org/downloads/release/python-279/
    > The entirety of Python 3.4's ssl module has been backported for Python 
2.7.9.
    > See PEP 466 for justification.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cgtx/libcloud dependency_logic

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/libcloud/pull/486.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #486
    
----
commit 3231772f96208914ba986fee53c23ec80d3731e4
Author: cgtx <[email protected]>
Date:   2015-03-13T21:26:58Z

    Consistent logic for dependencies resolution
    
    Different versions of Python have different dependencies.  These differences
    are parsed in various ways.  This pull request establishes a consistent 
method
    for setting dependencies per version.
    
    In addition, the code from `backports.ssl_match_hostname` has been merged 
into
    the standard library in Python 2.7.9.  The condition for adding that 
dependency
    now takes into account that fact.
    
    https://www.python.org/downloads/release/python-279/
    > The entirety of Python 3.4's ssl module has been backported for Python 
2.7.9.
    > See PEP 466 for justification.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to