Background

Why the pyage/age duality?

The original project is named age and so is the binary of the corresponding Go implementation. I decided to call the Python package and the Pip project age as well, because in these cases it is obvious that it’s Python. The binary however is called pyage in order to avoid naming clashes. By the way, there is also cage (a C implementation) and rage (a Rust implementation). I decided to leave page for the Perl implementation 😉…