17
 18🎹 There are two ways to manage the python package:
 19
 201. NO_ASYNC: this way works as expected with delay time between  21`pipewire_python` and the rest of your code.
 22
 232. ASYNC: [⚠️Not yet implemented] this way works delegating

 12for the future of Linux application development.
 13
 14[pipewire_python](https://pypi.org/project/pipewire_python/) 
 15controlls `pipewire` via terminal, creating shell commands  16and executing them as required.
 17
 18🎹 There are two ways to manage the python package:

 11Flatpak we expect PipeWire to provide a core building block 
 12for the future of Linux application development.
 13
 14[pipewire_python](https://pypi.org/project/pipewire_python/)  15controlls `pipewire` via terminal, creating shell commands 
 16and executing them as required.
 17

  8that makes interacting with audio and video devices from 
  9containerized applications easy, with supporting Flatpak
 10applications being the primary goal. Alongside Wayland and
 11Flatpak we expect PipeWire to provide a core building block  12for the future of Linux application development.
 13
 14[pipewire_python](https://pypi.org/project/pipewire_python/) 

  5on top of audio and video devices that can be used to
  6support the use cases currently handled by both pulseaudio
  7and JACK. PipeWire was designed with a powerful security model
  8that makes interacting with audio and video devices from   9containerized applications easy, with supporting Flatpak
 10applications being the primary goal. Alongside Wayland and
 11Flatpak we expect PipeWire to provide a core building block