Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.


Python CFFI bindings to libyang.

pypi-project python-versions build-status license code-style


pip install libyang

This assumes is installed in the system and that libyang.h is available in the system include dirs.

You need the following system dependencies installed:

  • Python development headers
  • GCC
  • FFI development headers

On a Debian/Ubuntu system:

sudo apt-get install python3-dev gcc python3-cffi


The current version requires at least C libyang 2.25.

The last version of the bindings that works with C libyang 1.x is v1.7.0.

Compilation Flags

If libyang headers and libraries are installed in a non-standard location, you can specify them with the LIBYANG_HEADERS and LIBYANG_LIBRARIES variables. Additionally, for finer control, you may use LIBYANG_EXTRA_CFLAGS and LIBYANG_EXTRA_LDFLAGS:

LIBYANG_HEADERS=/home/build/opt/ly/include \
LIBYANG_LIBRARIES=/home/build/opt/ly/lib \
LIBYANG_EXTRA_LDFLAGS="-rpath=/opt/ly/lib" \
       pip install libyang


Schema Introspection

>>> import libyang
>>> ctx = libyang.Context('/usr/local/share/yang/modules')
>>> module = ctx.load_module('ietf-system')
>>> print(module)
module: ietf-system
  +--rw system
  |  +--rw contact?          string
  |  +--rw hostname?         ietf-inet-types:domain-name
  |  +--rw location?         string
  |  +--rw clock
  |  |  +--rw (timezone)?
  |  |     +--:(timezone-utc-offset)
  |  |        +--rw timezone-utc-offset?   int16
  |  +--rw dns-resolver
  |     +--rw search*    ietf-inet-types:domain-name
  |     +--rw server* [name]
  |     |  +--rw name          string
  |     |  +--rw (transport)
  |     |     +--:(udp-and-tcp)
  |     |        +--rw udp-and-tcp
  |     |           +--rw address    ietf-inet-types:ip-address
  |     +--rw options
  |        +--rw timeout?    uint8 <5>
  |        +--rw attempts?   uint8 <2>
  +--ro system-state
     +--ro platform
     |  +--ro os-name?      string
     |  +--ro os-release?   string
     |  +--ro os-version?   string
     |  +--ro machine?      string
     +--ro clock
        +--ro current-datetime?   ietf-yang-types:date-and-time
        +--ro boot-datetime?      ietf-yang-types:date-and-time

    +---x set-current-datetime
    |  +---- input
    |     +---w current-datetime    ietf-yang-types:date-and-time
    +---x system-restart
    +---x system-shutdown

>>> xpath = '/ietf-system:system/ietf-system:dns-resolver/ietf-system:server'
>>> dnsserver = next(ctx.find_path(xpath))
>>> dnsserver
<libyang.schema.SList: server [name]>
>>> print(dnsserver.description())
List of the DNS servers that the resolver should query.

When the resolver is invoked by a calling application, it
sends the query to the first name server in this list.  If
no response has been received within 'timeout' seconds,
the resolver continues with the next server in the list.
If no response is received from any server, the resolver
continues with the first server again.  When the resolver
has traversed the list 'attempts' times without receiving
any response, it gives up and returns an error to the
calling application.

Implementations MAY limit the number of entries in this
>>> dnsserver.ordered()
>>> for node in dnsserver:
...     print(repr(node))
<libyang.schema.SLeaf: name string>
<libyang.schema.SContainer: udp-and-tcp>
>>> ctx.destroy()

Data Tree

>>> import libyang
>>> ctx = libyang.Context()
>>> module = ctx.parse_module_str('''
... module example {
...   namespace "urn:example";
...   prefix "ex";
...   container data {
...     list interface {
...       key name;
...       leaf name {
...         type string;
...       }
...       leaf address {
...         type string;
...       }
...     }
...     leaf hostname {
...       type string;
...     }
...   }
... }
... ''')
>>> print(module.print_mem('tree'))
module: example
  +--rw data
     +--rw interface* [name]
     |  +--rw name       string
     |  +--rw address?   string
     +--rw hostname?    string
>>> node = module.parse_data_dict({
...     'data': {
...         'hostname': 'foobar',
...         'interface': [
...             {'name': 'eth0', 'address': ''},
...             {'name': 'lo', 'address': ''},
...         ],
...     },
... })
>>> print(node.print_mem('xml', pretty=True))
<data xmlns="urn:example">
>>> node.print_dict()
{'data': {'interface': [{'name': 'eth0', 'address': ''}, {'name':
'lo', 'address': ''}], 'hostname': 'foobar'}}
>>> ctx.destroy()

See the tests folder for more examples.


This is an open source project and all contributions are welcome.


Please create new issues for any bug you discover at It is not necessary to file a bug if you are preparing a patch.

Pull Requests

Here are the steps for submitting a change in the code base:

  1. Fork the repository:

  2. Clone your own fork into your development machine:

    git clone<you>/libyang-python
  3. Create a new branch named after what your are working on:

    git checkout -b my-topic
  4. Edit the code and call make format to ensure your modifications comply with the coding style.

    Your contribution must be licensed under the MIT License . At least one copyright notice is expected in new files.

  5. If you are adding a new feature or fixing a bug, please consider adding or updating unit tests.

  6. Before creating commits, run make lint and make tests to check if your changes do not break anything. You can also run make which will run both.

  7. Create commits by following these simple guidelines:

    • Solve only one problem per commit.

    • Use a short (less than 72 characters) title on the first line followed by an blank line and a more thorough description body.

    • Wrap the body of the commit message should be wrapped at 72 characters too unless it breaks long URLs or code examples.

    • If the commit fixes a Github issue, include the following line:

      Fixes: #NNNN


  8. Push your topic branch in your forked repository:

    git push origin my-topic

    You should get a message from Github explaining how to create a new pull request.

  9. Wait for a reviewer to merge your work. If minor adjustments are requested, use git commit --fixup $sha1 to make it obvious what commit you are adjusting. If bigger changes are needed, make them in new separate commits. Once the reviewer is happy, please use git rebase --autosquash to amend the commits with their small fixups (if any), and git push --force on your topic branch.

Thank you in advance for your contributions!


Python bindings for the libyang library