You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This package contains the python language bindings for the drone API and the associated MAVProxy module.
10
10
11
11
## Users wanted!
12
12
13
-
We'd love your [feedback and suggestions](https://github.com/diydrones/dronekit-python/issues) about this API and are eager to evolve it to meet your needs.
13
+
We'd love your [feedback and suggestions](https://github.com/dronekit/dronekit-python/issues) about this API and are eager to evolve it to meet your needs.
14
14
15
15
For documentation on how to use this API please see:
.. This document was auto-generated by the get_release_notes.py script using latest-release information from github
2
-
3
-
Release 1.4.0 (July 24, 2015)
4
-
=============================
5
-
1
+
.. This document was auto-generated by the get_release_notes.py script using latest-release information from github
2
+
3
+
Release 1.4.0 (July 24, 2015)
4
+
=============================
5
+
6
6
7
7
**Features:**
8
8
@@ -21,26 +21,26 @@ Release 1.4.0 (July 24, 2015)
21
21
* Added information about clearing ROI (#172)
22
22
* Explicitly documented issues about `Vehicle.commands.clear()` (#213)
23
23
24
-
Commits
25
-
-------
26
-
24
+
Commits
25
+
-------
26
+
27
27
28
28
The commits relevant to this release `are listed here <https://github.com/diydrones/dronekit-python/compare/v1.3.1...v1.4.0>`_ (Github)
29
29
30
-
Bug fixes
31
-
---------
32
-
30
+
Bug fixes
31
+
---------
32
+
33
33
34
34
The bugs that were closed in this release `are listed here <https://github.com/diydrones/dronekit-python/issues?utf8=%E2%9C%93&q=is%3Aclosed+created%3A%3E2015-07-07+is%3Aissue+>`_ (Github).
35
35
36
-
Merged pull requests
37
-
--------------------
38
-
36
+
Merged pull requests
37
+
--------------------
38
+
39
39
40
40
The pull requests merged into this release `are listed here <https://github.com/diydrones/dronekit-python/pulls?utf8=%E2%9C%93&q=is%3Amerged+created%3A%3E2015-07-07+is%3Apr+>`_ (Github).
Copy file name to clipboardExpand all lines: docs/about/license.rst
+1-1
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
Open Source Licence
3
3
=======================
4
4
5
-
DroneKit-Python is licensed under the *Apache License Version 2.0, January 2004 (http://www.apache.org/licenses/). This is present in the `LICENSE <https://github.com/diydrones/dronekit-python/blob/master/LICENSE>`_ file in the source tree, and reproduced below:
5
+
DroneKit-Python is licensed under the *Apache License Version 2.0, January 2004 (http://www.apache.org/licenses/). This is present in the `LICENSE <https://github.com/dronekit/dronekit-python/blob/master/LICENSE>`_ file in the source tree, and reproduced below:
Copy file name to clipboardExpand all lines: docs/about/overview.rst
+2-2
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Open source community
12
12
13
13
DroneKit-Python is an open source and community-driven project.
14
14
15
-
You can find all the source code on `Github here <https://github.com/diydrones/dronekit-python>`_ and check out our permissive :doc:`Apache v2 Licence <license>`.
15
+
You can find all the source code on `Github here <https://github.com/dronekit/dronekit-python>`_ and check out our permissive :doc:`Apache v2 Licence <license>`.
16
16
If you want to join the community, then see our :doc:`contributing section <contributing>` for lots of ideas on how you can help.
17
17
18
18
@@ -46,7 +46,7 @@ Technical support
46
46
This documentation is a great place to get started with developing DroneKit Python APIs.
47
47
48
48
If you run into problems, the `best place to ask questions is Stack Overflow <http://stackoverflow.com/questions/tagged/dronekit-python>`_.
49
-
If your problem turns out to be a bug, then it should be `posted on Github <https://github.com/diydrones/dronekit-python/issues>`_.
49
+
If your problem turns out to be a bug, then it should be `posted on Github <https://github.com/dronekit/dronekit-python/issues>`_.
Copy file name to clipboardExpand all lines: docs/contributing/contributions_api.rst
+5-5
Original file line number
Diff line number
Diff line change
@@ -9,13 +9,13 @@ This article provides a high level overview of how to contribute changes to the
9
9
.. tip::
10
10
11
11
We highly recommend that changes and ideas are `discussed with the project team
12
-
<https://github.com/diydrones/dronekit-python/issues>`_ before starting work!
12
+
<https://github.com/dronekit/dronekit-python/issues>`_ before starting work!
13
13
14
14
15
15
Submitting changes
16
16
==================
17
17
18
-
Contributors should fork the main `diydrones/dronekit-python/ <https://github.com/diydrones/dronekit-python>`_
18
+
Contributors should fork the main `dronekit/dronekit-python/ <https://github.com/dronekit/dronekit-python>`_
19
19
repository and contribute changes back to the project master branch using pull requests
20
20
21
21
* Changes should be :ref:`tested locally <contributing-test-code>` before submission.
@@ -78,7 +78,7 @@ Good unit tests should:
78
78
79
79
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.
80
80
81
-
Tests names should refer directly to a Github issue (for example, ``test_12.py`` would refer to `issue #12 <https://github.com/diydrones/dronekit-python/issues/12>`_ or describe fully what functionality they encompass (for example, ``test_waypoints.py`` would describe a unit test for the waypoints API).
81
+
Tests names should refer directly to a Github issue (for example, ``test_12.py`` would refer to `issue #12 <https://github.com/dronekit/dronekit-python/issues/12>`_ or describe fully what functionality they encompass (for example, ``test_waypoints.py`` would describe a unit test for the waypoints API).
82
82
83
83
Avoiding printing any data from your test. Instead, use assertions to test your code is consistent. You can use the built-in Python ``assert`` macro as well as ``assert_equals`` from the ``nose.tools`` module:
84
84
@@ -137,7 +137,7 @@ You can write a new integrated test by adding a file with the naming scheme :fil
137
137
138
138
This checks to see that the parameter objectis of type`float`.
139
139
140
-
Tests names should refer directly to a Github issue (for example, ``test_12.py`` would refer to `issue #12 <https://github.com/diydrones/dronekit-python/issues/12>`_ or describe fully what functionality they encompass (for example, ``test_waypoints.py`` would describe a unit test for the waypoints API).
140
+
Tests names should refer directly to a Github issue (for example, ``test_12.py`` would refer to `issue #12 <https://github.com/dronekit/dronekit-python/issues/12>`_ or describe fully what functionality they encompass (for example, ``test_waypoints.py`` would describe a unit test for the waypoints API).
141
141
142
142
Avoiding printing any data from your test. Instead, use assertions to test your code is consistent. You can use the built-in Python ``assert`` macro as well as``assert_equals``from the ``testlib`` module:
143
143
@@ -157,7 +157,7 @@ Web client tests
157
157
.. warning::
158
158
159
159
The web client library is being rewritten. Please `discuss with the project team
160
-
<https://github.com/diydrones/dronekit-python/issues>`_ if you intend to develop withorfor the present version of the web client.
160
+
<https://github.com/dronekit/dronekit-python/issues>`_ if you intend to develop withorfor the present version of the web client.
161
161
162
162
Web client tests use *nosetests*. To run these, you will need to sign up forAPI keys from`cloud.dronekit.io <https://cloud.dronekit.io/>`_.
163
163
With these, export a variable named ``DRONEAPI_KEY``with a value in the format``<id>.<key>`` to your environment.
Copy file name to clipboardExpand all lines: docs/examples/drone_delivery.rst
+1-1
Original file line number
Diff line number
Diff line change
@@ -84,7 +84,7 @@ Next we'll look at the basics of using the webservice and the local vehicle API
84
84
Source code
85
85
===========
86
86
87
-
The full source code at documentation build-time is listed below (`current version on github <https://github.com/diydrones/dronekit-python/blob/master/examples/drone_delivery/drone_delivery.py>`_):
87
+
The full source code at documentation build-time is listed below (`current version on github <https://github.com/dronekit/dronekit-python/blob/master/examples/drone_delivery/drone_delivery.py>`_):
Copy file name to clipboardExpand all lines: docs/examples/flight_replay.rst
+1-1
Original file line number
Diff line number
Diff line change
@@ -95,7 +95,7 @@ Next we'll work with existing Linux services (gpsd) to add a new drone based fea
95
95
Source code
96
96
===========
97
97
98
-
The full source code at documentation build-time is listed below (`current version on github <https://github.com/diydrones/dronekit-python/blob/master/examples/flight_replay/flight_replay.py>`_):
98
+
The full source code at documentation build-time is listed below (`current version on github <https://github.com/dronekit/dronekit-python/blob/master/examples/flight_replay/flight_replay.py>`_):
Copy file name to clipboardExpand all lines: docs/examples/follow_me.rst
+1-1
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ Next, take a look at the full :ref:`api_reference` for more information.
42
42
Source code
43
43
===========
44
44
45
-
The full source code at documentation build-time is listed below (`current version on github <https://github.com/diydrones/dronekit-python/blob/master/examples/follow_me/follow_me.py>`_):
45
+
The full source code at documentation build-time is listed below (`current version on github <https://github.com/dronekit/dronekit-python/blob/master/examples/follow_me/follow_me.py>`_):
Copy file name to clipboardExpand all lines: docs/examples/guided-set-speed-yaw-demo.rst
+1-1
Original file line number
Diff line number
Diff line change
@@ -344,7 +344,7 @@ ArduPilot version:
344
344
Source code
345
345
===========
346
346
347
-
The full source code at documentation build-time is listed below (`current version on github <https://github.com/diydrones/dronekit-python/blob/master/examples/guided_set_speed_yaw/guided_set_speed_yaw.py>`_):
347
+
The full source code at documentation build-time is listed below (`current version on github <https://github.com/dronekit/dronekit-python/blob/master/examples/guided_set_speed_yaw/guided_set_speed_yaw.py>`_):
Copy file name to clipboardExpand all lines: docs/examples/simple_goto.rst
+1-1
Original file line number
Diff line number
Diff line change
@@ -133,7 +133,7 @@ To return to the home position and land, we set the mode to ``RTL``:
133
133
Source code
134
134
===========
135
135
136
-
The full source code at documentation build-time is listed below (`current version on github <https://github.com/diydrones/dronekit-python/blob/master/examples/simple_goto/simple_goto.py>`_):
136
+
The full source code at documentation build-time is listed below (`current version on github <https://github.com/dronekit/dronekit-python/blob/master/examples/simple_goto/simple_goto.py>`_):
Copy file name to clipboardExpand all lines: docs/examples/vehicle_state.rst
+3-3
Original file line number
Diff line number
Diff line change
@@ -112,19 +112,19 @@ Provided that the vehicle is connected and able to arm, it should run through to
112
112
Two cases where you may observe issues are:
113
113
114
114
* You will see an error ``Timeout setting THR_MIN to 10.000000``. This can be ignored because the value is actually set.
115
-
See `#12 Timeout error when setting a parameter <https://github.com/diydrones/dronekit-python/issues/12>`_ for information.
115
+
See `#12 Timeout error when setting a parameter <https://github.com/dronekit/dronekit-python/issues/12>`_ for information.
116
116
* When the observer sets the mode callback, it waits two seconds after changing the mode before removing the observer
117
117
(to ensure that the callback function is run before the observer is removed). In this time you may see the callback being
118
118
called twice even though the mode is only changed once.
119
-
See `#60 Attribute observer callbacks are called with heartbeat until disabled - after first called <https://github.com/diydrones/dronekit-python/issues/60>`_
119
+
See `#60 Attribute observer callbacks are called with heartbeat until disabled - after first called <https://github.com/dronekit/dronekit-python/issues/60>`_
120
120
for more information.
121
121
122
122
123
123
124
124
Source code
125
125
===========
126
126
127
-
The full source code at documentation build-time is listed below (`current version on github <https://github.com/diydrones/dronekit-python/blob/master/examples/vehicle_state/vehicle_state.py>`_):
127
+
The full source code at documentation build-time is listed below (`current version on github <https://github.com/dronekit/dronekit-python/blob/master/examples/vehicle_state/vehicle_state.py>`_):
Copy file name to clipboardExpand all lines: docs/guide/copter/guided_mode.rst
+2-2
Original file line number
Diff line number
Diff line change
@@ -353,9 +353,9 @@ The *home location* is updated immediately in ArduPilot, but the change may not
353
353
Command acknowledgements and response values
354
354
--------------------------------------------
355
355
356
-
ArduPilot typically sends a command acknowledgement indicating whether a command was received, and whether it was accepted or rejected. At time of writing there is no way to intercept this acknowledgement in the API (`#168 <https://github.com/diydrones/dronekit-python/pull/168>`_).
356
+
ArduPilot typically sends a command acknowledgement indicating whether a command was received, and whether it was accepted or rejected. At time of writing there is no way to intercept this acknowledgement in the API (`#168 <https://github.com/dronekit/dronekit-python/pull/168>`_).
357
357
358
-
Some MAVLink messages request information from the autopilot, and expect the result to be returned in another message. At time of writing you can send the request (provided the message is handled by the AutoPilot in GUIDED mode) but there is no way to intercept the response in DroneKit-Python (`#169 <https://github.com/diydrones/dronekit-python/issues/169>`_).
358
+
Some MAVLink messages request information from the autopilot, and expect the result to be returned in another message. At time of writing you can send the request (provided the message is handled by the AutoPilot in GUIDED mode) but there is no way to intercept the response in DroneKit-Python (`#169 <https://github.com/dronekit/dronekit-python/issues/169>`_).
0 commit comments