Third-party Slackware packages built with slackrepo on Slackware64-current. Use at your own risk. All packages are signed with my GPG key.
![[ICO]](/icons/blank.gif){kind=icon} | Name | Last modified | Size |
|---|---|---|---|
![[PARENTDIR]](/icons/back.gif){kind=icon} | Parent Directory | - | |
![[TXT]](/icons-pkg/checksum.svg){kind=icon} | python3-h11-0.16.0-x86_64-1_danix.txz.sha256 | 2026-05-06 13:25 | 104 |
| python3-h11-0.16.0-x86_64-1_danix.txz.md5 | 2026-05-12 11:11 | 72 |
![[TXT]](/icons-pkg/signature.svg){kind=icon} | python3-h11-0.16.0-x86_64-1_danix.txz.asc | 2026-05-12 11:11 | 870 |
![[ ]](/icons-pkg/package.svg){kind=icon} | python3-h11-0.16.0-x86_64-1_danix.txz | 2026-05-06 13:25 | 53K |
![[TXT]](/icons-pkg/file.svg){kind=icon} | python3-h11-0.16.0-x86_64-1_danix.txt | 2026-05-12 11:11 | 528 |
| python3-h11-0.16.0-x86_64-1_danix.meta | 2026-05-12 11:11 | 757 |
| python3-h11-0.16.0-x86_64-1_danix.lst | 2026-05-12 11:11 | 4.2K |
python3-h11 (little HTTP/1.1 library written from scratch in Python)
It's a "quot;bring-your-own-I/O"quot; library; h11 contains no IO code
whatsoever. This means you can hook h11 up to your favorite network
API, and that could be anything you want: synchronous, threaded,
asynchronous, or your own implementation of RFC 6214 - h11 won't judge
you.