Source: https://seerepo.com/compare/aio-libs/aiohttp/vs/getpelican/pelican
Markdown source: https://seerepo.com/compare/aio-libs/aiohttp/vs/getpelican/pelican.md
Description: aiohttp and pelican share 3 technologies: Rich, docutils, and jinja2. Both are written in Python.

# aiohttp vs pelican

aiohttp and pelican share 3 technologies: Rich, docutils, and jinja2. Both are written in Python.

- [aio-libs/aiohttp](https://seerepo.com/r/aio-libs/aiohttp): Asynchronous HTTP client/server framework for asyncio and Python
- [getpelican/pelican](https://seerepo.com/r/getpelican/pelican): Static site generator that supports Markdown and reST syntax. Powered by Python.

## What they share and what sets them apart

- In common: Rich, docutils, jinja2
- Only in aiohttp: valkey, AIOHTTP, alabaster, cryptography, imagesize, markdown-it-py, markupsafe, mdit-py-plugins, mdurl, myst-parser, annotated-types, Pydantic, execnet, Gunicorn, python-on-whales
- Only in pelican: None

## Side by side

| | aiohttp | pelican |
|---|---|---|
| Size | 104,911 lines written, 58 code files | 31,003 lines written, 59 code files |
| Who writes it | 0% of its commits signed by AI. With Claude Code | 0% of its commits signed by AI. With Claude Code |
| Activity | Last push November 7, 2026, 13,628 commits, 16,605 stars | Last push November 9, 2026, 2,966 commits, 13,370 stars |
| Tests | 84 test files. 22.4% of its code files have a test that imports them | 154 test files. 25.4% of its code files have a test that imports them |

- Size: Lines written by people and agents, without generated ones; code files, without tests.
- Who writes it: A commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
- Activity: From GitHub and its history, on the day SeeRepo read it.
- Tests: The files that test the code, and the share of code files a test imports.

## Frequently asked questions

### Which is bigger, aiohttp or pelican?

aiohttp, with 104,911 lines written; pelican has 31,003.

The proof: [aio-libs/aiohttp's code at commit 0ae5b96](https://github.com/aio-libs/aiohttp/tree/0ae5b96be76a0fd8566fed53e7effc294f924add)

### Which has more GitHub stars, aiohttp or pelican?

aiohttp, with 16,605 stars; pelican has 13,370.

The proof: [aio-libs/aiohttp on GitHub](https://github.com/aio-libs/aiohttp)

### Which has more tests, aiohttp or pelican?

pelican, with 154 test files; aiohttp has 84.

The proof: [getpelican/pelican's code at commit e8748ab](https://github.com/getpelican/pelican/tree/e8748aba9ad0907a8801646e957b37a02709240d)

### Which was updated more recently, aiohttp or pelican?

pelican: its last push was on November 9, 2026, and aiohttp's on November 7, 2026.

The proof: [getpelican/pelican's commits on GitHub](https://github.com/getpelican/pelican/commits)

## Sources

- aio-libs/aiohttp: Read on November 7, 2026, at commit 0ae5b96 (https://github.com/aio-libs/aiohttp/tree/0ae5b96be76a0fd8566fed53e7effc294f924add)
- getpelican/pelican: Read on November 10, 2026, at commit e8748ab (https://github.com/getpelican/pelican/tree/e8748aba9ad0907a8801646e957b37a02709240d)

## What is your repo built with?

Any public repo, with no account: https://seerepo.com/r/owner/repo/built, with the owner and name it has on GitHub.