Skip to content

PEP 541 Request: PROJECT_NAME #12225

Description

@estcarisimo

Project to be claimed

https://pypi.org/project/PyLevy/

Your PyPI username

estcarisimo

Reasons for the request

I am asking for ownership of the PyPI project PyLevy so that the continued maintenance of that package can be published under its own name.

The name currently belongs to Paul Harrison's original package from 2005. Its three releases on PyPI (0.1, 0.2, 0.3) have no distribution files: nothing installable has ever been published under the name, so pip install pylevy has never worked and a transfer breaks no existing install. The project's homepage, http://www.logarithmic.net/pfh/pylevy, carries the author's own status note, dated 10 May 2016: "I have not updated this package for many years, but José María Miotto has recently made some improvements to it", linking to https://github.com/josemiotto/pylevy. That is the author himself directing users to the repository I am asking to publish from.

That repository is not a fork in the usual sense but the same package, continued. José María Miotto started it from Paul Harrison's code in May 2016 and has maintained it since; it has carried name = "PyLevy" in its own packaging metadata for the whole of that time, and Paul Harrison is credited as an author in pyproject.toml and CITATION.cff. I am a co-maintainer there with write access, granted by José María Miotto on 1 September 2026.

The package is ready to publish. Version 2.0.0 landed on master this month: a typed, validated API alongside the original functions (which still work and return the same numbers), a 1,070-test suite with a golden file of exact floating-point outputs that CI regenerates on every push, CI on Linux, macOS, and Windows on both NumPy 1.x and 2.x, documentation built with -W on every pull request, and a release workflow that publishes through Trusted Publishing. The only thing between that version and users is the name.

Publishing under a different name is not a good outcome for anyone. The package has been PyLevy in its own metadata since 2005, its users know it by that name, and the original author has pointed them to this repository. Renaming it would leave pip install pylevy installing an empty placeholder while the real package sat under a name nobody searches for.

I wrote to Paul Harrison on 1 September 2026 at the address listed on his project page, asking to be added as a maintainer of the PyPI project, but have not received a reply. I would prefer a voluntary transfer and will withdraw this request if he responds.

Requested outcome: add estcarisimo as an owner of the PyPI project. The existing releases, the version history and the original authorship will be preserved.

Maintenance or replacement?

Maintenance

Source code repositories URLs

Current project (the one the PyPI name belongs to)

http://www.logarithmic.net/pfh/pylevy

This is Paul Harrison's original PyLevy, written in 2005. It has no source repository; the page is the only home it ever had, and it lists a tarball
(PyLevy-0.4.tar.gz) that was never uploaded to PyPI. The three releases that exist on PyPI (0.1 to 0.3) carry no distribution files at all. The page's own status note, dated 10 May 2016, reads: "I have not updated this package for many years, but José María Miotto has recently made some improvements to it", and links to the repository below.

Project to publish under the name

https://github.com/josemiotto/pylevy

This is the same package, continued. José María Miotto took Paul Harrison's code as the initial commit in May 2016 (commit "original package modified"), has maintained it since, and the project has carried name = "PyLevy" in its own packaging metadata for the whole of that time. Paul Harrison is credited as an author in pyproject.toml and CITATION.cff. I am a co-maintainer with write access, granted on 1 September 2026, and the work to make it publishable landed on master this month as version 2.0.0:

  • a typed, validated API alongside the original functions, which still work
    and return the same numbers;
  • a 1,070-test suite with a golden file of exact hex floats that CI regenerates
    on every push;
  • CI on Linux, macOS and Windows, on NumPy 1.x and 2.x;
  • documentation built with -W on every pull request;
  • a release workflow that publishes through PyPI Trusted Publishing.

The only thing between that version and pip install pylevy is the name.

Contact and additional research

  • 1 September 2026: I emailed Paul Harrison at the address published on the project page, asking to be added as a maintainer of the PyPI project (PyPI username estcarisimo). No reply as of 11 September.
  • : follow-up via . No reply.

Research:

  • No release of PyLevy on PyPI (0.1 to 0.3) has any distribution files, so nothing installable has ever been published under the name, and a
    transfer breaks no one.
  • The project's homepage, http://www.logarithmic.net/pfh/pylevy, carries the author's own note dated 10 May 2016: "I have not updated this package for many years, but José María Miotto has recently made some improvements to it", pointing at https://github.com/josemiotto/pylevy.
  • That repository is the direct continuation: it has carried the name PyLevy in its own metadata since 2016, credits Paul Harrison as an author in pyproject.toml and CITATION.cff, and was modernized into version 2.0. in September 2026 (typed API, ~1,070-test suite, CI on Linux, macOS and Windows, documentation, Trusted Publishing release workflow). I hold write access there, granted by José María Miotto on 1 September 2026.
  • 2.0.0 cannot be published because the name is held by the dormant project. Publishing under another name would cause pip install pylevy to install an empty 2005 placeholder, while the real package sits under a name nobody searches for.

Requested outcome: add estcarisimo as an owner of the PyPI project. The existing releases and the original authorship will be preserved.

Code of Conduct

  • I agree to follow the PSF Code of Conduct

Activity

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