Thank you!

This begins version 3.0

All enums were revisisted and updated in accordance to NetworkManager documentation.

Some enums and their fields were renamed:

* `AccessPointCapabilities` -> `WifiAccessPointCapabilities`
* `WirelessCapabilities` -> `WifiCapabilities`
* `WpaSecurityFlags` -> `WifiAccessPointSecurityFlags`
  * `P2P_*` -> `PAIR_*`
  * `BROADCAST_*` -> `GROUP_*`
  * `AUTH_*` -> `KEY_MGMT_*`
* `ConnectionState` -> `ActiveConnectionState`
* `ConnectionStateReason` -> `ActiveConnectionStateReason`
* `ConnectionFlags` -> `SettingsConnectionFlags`
* `ConnectionStateFlags` -> `ActivationStateFlags`
* `DeviceCapabilities` -> `DeviceCapabilitiesFlags`
* `BluetoothCapabilities` -> `BluetoothCapabilitiesFlags`
* `ModemCapabilities` -> `ModemCapabilitiesFlags`
* `SecretAgentCapabilities` -> `SecretAgentCapabilitiesFlags`
* `VpnState` -> `VpnServiceState`
* `VpnFailure`
  * `LOGIN_FAILURE` -> `LOGIN_FAILED`

New enums:

* `NetworkManagerCapabilities`
* `WimaxNSPNetworkType`
* `SecretAgentGetSecretsFlags`
* `CheckpointCreateFlags`
* `CheckpointRollbackResult`
* `SettingsAddConnection2Flags`
* `SettingsUpdate2Flags`
* `DeviceReapplyFlags`
* `NetworkManagerReloadFlags`
* `RadioFlags`
* `MptcpFlags`
* `VpnConnectionState`
* `VpnConnectionStateReason`

Copy pasted from the working sdbus configuration.

The new name is WifiCapabilitiesFlags.
Also add a link to the enums themselves.

It explains the basic objects used in the NetworkManager.

While the master branch undergoing version 3.0.0 development
people will try to run the examples on PyPI version and fail.

Separating them by version will hopefully make it very apparent
which version the examples should be run against.

Otherwise it might be confusing on where the variables come from.

The github URL has changed but it was not updated at least in some
places, so update it now.

Signed-off-by: Raphaël Mélotte <raphael.melotte@mind.be>

The documentation URL in the README.md pointed to
'https://python-sdbus-networkmanager.readthedocs.io', but the one in
setup.py pointed to python-sdbus instead.

Fix the documentation URL, and while at it fix some others that had
the same issue.

Signed-off-by: Raphaël Mélotte <raphael.melotte@mind.be>

Thank you!

Apparently some people struggle with signals. This example should
show them how to use signals.

Add new `NetworkManagerVersionInfoCapability`, `ClientPermission`
and `ClientPermissionResult` enums.

Update `DeviceType`, `DeviceStateReason` and `DeviceMetered`
with new values.

Thank you @diggit for bringins this to my attention.

Closes #74

… was initialized with

The get_connections_by_id does not work properly with explicitly passed bus, and raises the following exception:

    settings_paths = await nm_settings.get_connections_by_id("eth0")
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ".../networkmanager/objects.py", line 177, in get_connections_by_id
    settings_properties = await settings.get_settings()
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File ".../dbus_proxy_async_method.py", line 108, in _dbus_async_call
    reply_message = await bus.call_async(call_message)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
sdbus.dbus_exceptions.DbusServiceUnknownError: The name org.freedesktop.NetworkManager was not provided by any .service files

This exception was discovered with the following test code:

import asyncio
from sdbus import sd_bus_open_system
from sdbus_async.networkmanager import NetworkManagerSettings

async def test_get_connections_by_id():
    system_bus = sd_bus_open_system()
    nm_settings = NetworkManagerSettings(system_bus)
    settings_paths = await nm_settings.get_connections_by_id("eth0")
    print(settings_paths)

if __name__ == "__main__":
    asyncio.run(test_get_connections_by_id())

After this fix, the issue is resolved and get_connections_by_id works correctly without raising an exception.

Fix NetworkManagerSettings.get_connections_by_id not using the bus it was initialized with

Thank you @hkhateb

…type

Thank you!

…d-peers

Thank you!