Continuing maintenance in a fork due to maintainer inactivity

[mxamin]

Over the past months I have tried multiple ways to reach the maintainer regarding releases, maintenance, and contribution coordination, including:

• PR comments/reviews,
• GitHub issues/comments,
• direct mentions,
• and email.

I have not received any response.

Since the latest PyPI release dates back to August 2022, and there are unresolved compatibility/build issues affecting users, I have decided to continue maintenance work in my own fork so fixes and updated wheels can continue to be published.

The fork has been renamed to pylibmc2 so it can be distributed independently on PyPI while avoiding conflicts with the original package.

This is not intended to fragment the project or replace the original repository. The goal is simply to keep the package usable and maintained for the community while the original project remains inactive from a release/maintenance perspective.

I will continue going through existing issues and open PRs and try to address/fix them over time in the fork.

If the maintainer becomes active again in the future, I would be happy to discontinue the fork and continue contributing directly to the original repository instead.

Fork:

• https://github.com/mxamin/pylibmc2

PyPI:

• https://pypi.org/project/pylibmc2/

Migration guide:

• https://github.com/mxamin/pylibmc2#using-pylibmc2-when-dependencies-request-pylibmc