there is no ☁️

Author: mrpollo

.travis.yml

@@ -11,7 +11,6 @@ install:
   - 'sudo pip install -r requirements.txt -UI'
 
 script:
-#  - '[ "${TRAVIS_PULL_REQUEST}" != "false" ] || nosetests -svx dronekit.test.web'
   - 'nosetests -svx dronekit.test.unit'
   - 'nosetests -svx dronekit.test.sitl'
 

appveyor.yml

@@ -15,7 +15,7 @@ install:
       [wheel]
       wheel-dir = c:/Users/appveyor/.pip-wheelhouse
       '@ | out-file -Encoding ascii -FilePath c:\Users\appveyor\pip\pip.ini
-  
+
   - cmd: 'SET PATH=%PYTHON%;c:\\Python27\\Scripts;%PATH%'
   - cmd: 'SET PYTHONUNBUFFERED=1'
 
@@ -24,7 +24,6 @@ install:
   - cmd: 'pip install -r requirements.txt -UI'
 
 build_script:
-#  - cmd: 'nosetests -svx dronekit.test.web'
   - cmd: 'nosetests -svx dronekit.test.unit'
   - cmd: 'nosetests -svx dronekit.test.sitl'
 

circle.yml

@@ -14,7 +14,6 @@ test:
     - 'cd docs; make clean; make html'
 
     # code
-#    - 'nosetests -svx dronekit.test.web'
     - 'nosetests -svx dronekit.test.unit'
     - 'nosetests -svx dronekit.test.sitl'
 

docs/contributing/contributions_api.rst

@@ -6,16 +6,16 @@ Contributing to the API
 
 This article provides a high level overview of how to contribute changes to the DroneKit-Python source code.
 
-.. tip:: 
+.. tip::
 
-    We highly recommend that changes and ideas are `discussed with the project team 
-    <https://github.com/dronekit/dronekit-python/issues>`_ before starting work! 
+    We highly recommend that changes and ideas are `discussed with the project team
+    <https://github.com/dronekit/dronekit-python/issues>`_ before starting work!
 
 
 Submitting changes
 ==================
 
-Contributors should fork the main `dronekit/dronekit-python/ <https://github.com/dronekit/dronekit-python>`_ 
+Contributors should fork the main `dronekit/dronekit-python/ <https://github.com/dronekit/dronekit-python>`_
 repository and contribute changes back to the project master branch using pull requests
 
 * Changes should be :ref:`tested locally <contributing-test-code>` before submission.
@@ -32,9 +32,8 @@ Test code
 
 There are three test suites in DroneKit-Python:
 
-* **Unit tests** (:file:`tests/unit`) — verify all code paths of the API. 
+* **Unit tests** (:file:`tests/unit`) — verify all code paths of the API.
 * **Integration tests** (:file:`tests/sitl`) — verify real-world code, examples, and documentation as they would perform in a real environment.
-* **Web client tests** (:file:`tests/web`) — specifically verify the Python library's capability to talk to `DroneKit Cloud <http://cloud.dronekit.io>`_.
 
 Test code should be used to verify new and changed functionality. New tests should:
 
@@ -46,20 +45,20 @@ Test code should be used to verify new and changed functionality. New tests shou
 Setting up local testing
 ------------------------
 
-Follow the links below to set up a development environment on your Linux or Windows computer. 
+Follow the links below to set up a development environment on your Linux or Windows computer.
 
 * :ref:`dronekit_development_linux`
 * :ref:`dronekit_development_windows`
 
-The tests require additional pip modules, including `nose <https://nose.readthedocs.org/en/latest/>`_, a 
+The tests require additional pip modules, including `nose <https://nose.readthedocs.org/en/latest/>`_, a
 Python library and tool for writing and running test scripts. These can be installed separately using either of the commands below:
 
 .. code:: bash
 
     # Install just the additional requirements for tests
     pip install requests nose mock
 
-    # (or) Install all requirements for dronekit, tests, and building documentation   
+    # (or) Install all requirements for dronekit, tests, and building documentation
     pip install -r requirements.txt
 
 For several tests, you may be required to set an **environment variable**. In your command line, you can set the name of a variable to equal a value using the following invocation, depending on your OS:
@@ -73,35 +72,35 @@ For several tests, you may be required to set an **environment variable**. In yo
 Unit tests
 ----------
 
-All new features should be created with accompanying unit tests. 
+All new features should be created with accompanying unit tests.
 
 DroneKit-Python unit tests are based on the `nose <https://nose.readthedocs.org/en/latest/>`_ test framework,
-and use `mock <https://docs.python.org/dev/library/unittest.mock.html>`_ to simulate objects and APIs and 
+and use `mock <https://docs.python.org/dev/library/unittest.mock.html>`_ to simulate objects and APIs and
 ensure correct results.
 
-To run the tests and display a summary of the results (on any OS), 
-navigate to the **dronekit-python** folder and enter the following 
+To run the tests and display a summary of the results (on any OS),
+navigate to the **dronekit-python** folder and enter the following
 command on a terminal/prompt:
 
 .. code:: bash
 
     nosetests dronekit.test.unit
- 
+
 
 
 
 Writing a new unit test
 ^^^^^^^^^^^^^^^^^^^^^^^
 
-Create any file named :file:`test_XXX.py` in the :file:`tests/unit` folder to add it as a test. 
+Create any file named :file:`test_XXX.py` in the :file:`tests/unit` folder to add it as a test.
 Feel free to copy from existing tests to get started. When *nosetests* is run, it will add your new test to its summary.
 
-Tests names should be named based on their associated Github issue (for example, 
-``test_12.py`` for `issue #12 <https://github.com/dronekit/dronekit-python/issues/12>`_) 
-or describe the functionality covered (for example, ``test_waypoints.py`` 
+Tests names should be named based on their associated Github issue (for example,
+``test_12.py`` for `issue #12 <https://github.com/dronekit/dronekit-python/issues/12>`_)
+or describe the functionality covered (for example, ``test_waypoints.py``
 for a unit test for the waypoints API).
-  
-Use assertions to test your code is consistent. You can use the built-in Python ``assert`` macro as well as ``assert_equals`` and ``assert_not_equals`` 
+
+Use assertions to test your code is consistent. You can use the built-in Python ``assert`` macro as well as ``assert_equals`` and ``assert_not_equals``
 from the ``notestools`` module:
 
 .. note::
@@ -116,7 +115,7 @@ from the ``notestools`` module:
         assert the_number_two > 0, '2 should be greater than zero!'
         assert_equals(the_number_two, 2, '2 should equal two!')
         assert_not_equals(the_number_two, 1, '2 should equal one!')
-        
+
 Please add documentation to each test function describing what behavior it verifies.
 
 
@@ -129,8 +128,8 @@ Integrated tests use a custom test runner that is similar to *nosetests*. On any
 
     cd dronekit-python
     nosetests dronekit.test.sitl
-    
-You can choose to run a specific tests. The example below shows how to run 
+
+You can choose to run a specific tests. The example below shows how to run
 **\dronekit-python\dronekit\test\sitl\test_12.py**.
 
 .. code:: bash
@@ -160,12 +159,12 @@ Integration tests should be written or improved whenever:
 
 You can write a new integrated test by adding (or copying) a file with the naming scheme :file:`test_XXX.py` to the :file:`tests/sitl` directory.
 
-Tests names should be named based on their associated Github issue (for example, 
-``test_12.py`` for `issue #12 <https://github.com/dronekit/dronekit-python/issues/12>`_) 
-or describe the functionality covered (for example, ``test_waypoints.py`` 
+Tests names should be named based on their associated Github issue (for example,
+``test_12.py`` for `issue #12 <https://github.com/dronekit/dronekit-python/issues/12>`_)
+or describe the functionality covered (for example, ``test_waypoints.py``
 for an integration test for the waypoints API).
 
-Tests should minimally use the imports shown below and decorate test functions with ``@with_sitl`` 
+Tests should minimally use the imports shown below and decorate test functions with ``@with_sitl``
 (this sets up the test and passes in a connection string for SITL).
 
 .. code:: python
@@ -184,13 +183,13 @@ Tests should minimally use the imports shown below and decorate test functions w
         vehicle.close()
 
 
-Use assertions to test your code is consistent. You can use the built-in Python ``assert`` macro as well as ``assert_equals`` and ``assert_not_equals`` 
+Use assertions to test your code is consistent. You can use the built-in Python ``assert`` macro as well as ``assert_equals`` and ``assert_not_equals``
 from the ``testlib`` module:
 
 .. note::
 
     Avoiding printing any data from your test!
-    
+
 
 
 .. code:: python
@@ -202,21 +201,3 @@ from the ``testlib`` module:
         assert_equals(the_number_two, 2, '2 should equal two!'
 
 Please add documentation to each test function describing what behavior it verifies.
-
-Web client tests
-----------------
-
-.. warning:: 
-
-    The web client library is being rewritten. Please `discuss with the project team 
-    <https://github.com/dronekit/dronekit-python/issues>`_ if you intend to develop with or for the present version of the web client.
-
-Web client tests use *nosetests*. To run these, you will need to sign up for API keys from `cloud.dronekit.io <https://cloud.dronekit.io/>`_. 
-With these, export a variable named ``DRONEAPI_KEY`` with a value in the format ``<id>.<key>`` to your environment.
-
-On any OS, enter the following command on a terminal/prompt to run the web-client tests (and display summary results):
-
-.. code:: bash
-
-    cd dronekit-python
-    nosetests tests/web

dronekit/cloud/CloudClient.py

@@ -26,6 +26,6 @@
       ],
       license='apache',
       packages=[
-          'dronekit', 'dronekit.cloud', 'dronekit.test'
+          'dronekit', 'dronekit.test'
       ],
       ext_modules=[])