Skip to content

PEP 541 Request: payjoin #12912

Open
Open

Description

@spacebear21

Project to be claimed

payjoin: https://pypi.org/project/payjoin

Your PyPI username

spacebear21: https://pypi.org/user/spacebear21

Reasons for the request

I am an existing Maintainer on the payjoin project and I am asking to be granted the Owner role. The sole Owner has not responded to contact attempts, and Owner is required to configure trusted publishing, which our release workflow depends on.

The project has a single release, 0.1.0.dev0, uploaded on 2023-12-20. There have been no releases since, and the Home Page listed on the project (https://LtbL.io) shows no activity related to it. The project was an early development snapshot of the Python bindings for the Payjoin Dev Kit, which are now developed and released from https://github.com/payjoin/rust-payjoin, where I am a maintainer.

I can upload with my Maintainer role, but I have deliberately not done so: our releases are published only via trusted publishing (OIDC) with PEP 740 attestations, and only an Owner can add a trusted publisher. I also did not want to muddy the "no releases in twelve months" test while this request is open.

This is the same project under the same name, continuing under the upstream maintainers. Publishing under a different name is not a good option. The package is already published as payjoin from this repository on npm, pub.dev and NuGet. All three are at 0.25.1 and each registry's repository metadata points at https://github.com/payjoin/rust-payjoin. The existing PyPI project is a 2023 development snapshot of this same codebase. A rename on PyPI alone would split the install name across ecosystems for a package that is otherwise consistently named.

Maintenance or replacement?

Maintenance

Source code repositories URLs

Current project (snapshot the 0.1.0.dev0 release was cut from) and the project to be published, which are the same repository:
https://github.com/payjoin/rust-payjoin

Python bindings live in payjoin-ffi/python.

Contact and additional research

  • 8/27/2026: Contacted BZavior on Discord, no reply.
  • 9/29/2026: Reached out on Discord again, no reply.
  • 10/15/2026: Emailed at the address in the project's Author field (BitcoinZavior@GMail.Com), asking either to promote my account to Owner or to add a trusted publisher. No reply as of today.

Project metadata checked via https://pypi.org/pypi/payjoin/json: one release (0.1.0.dev0, 2023-12-20), Author BitcoinZavior, Home Page https://LtbL.io, no Maintainer email set.

I understand that the moderators will contact the owner independently and that this may take six weeks or more. If the owner responds to you and would prefer to remain an Owner alongside me, that is fine.

Code of Conduct

  • I agree to follow the PSF Code of Conduct

Activity

  1. github-actions commented on Oct 29, 2026

    @github-actions

    Thanks for filing.

    There are currently 325 other open PEP 541 issues ahead of this one.

    PyPI support is one paid staffer, plus volunteers, plus whatever part-time hours other PSF staff have to give. Often that's zero. If you'd like to help fund more staffing, the PSF takes donations at https://www.python.org/psf/donations/. Either way, someone will get to your request eventually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    PEP 541Package name support requests

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions