[dev] [jira] [Resolved] (LIBCLOUD-96) Add third-party dependencies management

["Roman Bogorodskiy (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LIBCLOUD-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Bogorodskiy resolved LIBCLOUD-96.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.5.2

I've added a list of dependencies to the 'Testing' section of the HACKING file.

> Add third-party dependencies management
> ---------------------------------------
>
>                 Key: LIBCLOUD-96
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-96
>             Project: Libcloud
>          Issue Type: Improvement
>    Affects Versions: 0.5.1
>            Reporter: Andrey Zhuchkov
>             Fix For: 0.5.2
>
>
> Recently I have faced with a problem during running libcloud tests:
> Traceback (most recent call last):
>   File "setup.py", line 189, in <module>
>     'Topic :: Software Development :: Libraries :: Python Modules'
>   File "/usr/lib/python2.6/distutils/core.py", line 152, in setup
>     dist.run_commands()
>   File "/usr/lib/python2.6/distutils/dist.py", line 975, in run_commands
>     self.run_command(cmd)
>   File "/usr/lib/python2.6/distutils/dist.py", line 995, in run_command
>     cmd_obj.run()
>   File "setup.py", line 57, in run
>     status = self._run_tests()
>   File "setup.py", line 95, in _run_tests
>     tests = TestLoader().loadTestsFromNames(testfiles)
>   File "/usr/lib/python2.6/unittest.py", line 613, in loadTestsFromNames
>     suites = [self.loadTestsFromName(name, module) for name in names]
>   File "/usr/lib/python2.6/unittest.py", line 584, in loadTestsFromName
>     parent, obj = obj, getattr(obj, part)
> AttributeError: 'module' object has no attribute 'test_deployment'
> Since I have already dealt with similar issue, I figured out what the problem is quite quick - the problem is related to imports, particularly to mock library import. This is not core python package and there is no requirements to install this package in project documentation. Since that it could be really difficult to determine the cause of error.
> So I think it would be helpfull to use some dependency management mechanism or at least add requirements section into the documentation.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira