Skip to content

Publish as serpextract-a8c - #36

Closed
xyu wants to merge 1 commit into
masterfrom
publish-as-serpextract-a8c
Closed

xyu wants to merge 1 commit into
masterfrom
publish-as-serpextract-a8c

Conversation

@xyu

@xyu xyu commented Oct 28, 2026

Copy link
Copy Markdown
Member

Proposed changes

serpextract 0.8.0 and later releases install as serpextract-a8c. Code still imports serpextract.

Why are these changes being made?

We no longer have access to the serpextract project on PyPI, so 0.8.0 (#35) cannot go there. Our internal index also passes PyPI versions through, so publishing under a name only we control stops an outside serpextract release from reaching our installs.

Testing

python -m build and twine check in python:3.9-bullseye, then the wheel installed into a clean venv:

serpextract_a8c-0.8.0-py3-none-any.whl
serpextract_a8c-0.8.0.tar.gz
0.8.0 0.8.0 pylru: False Google

(serpextract.__version__, installed serpextract-a8c version, pylru present, engine parsed from a Google search URL.)

Testing instructions

  • After merging, tag the release and upload it to the internal index:

    git tag v0.8.0 && git push origin v0.8.0
    python -m build && twine upload --repository-url <internal index> -u cogtree dist/serpextract_a8c-0.8.0*
    
    Uploading serpextract_a8c-0.8.0-py3-none-any.whl
    Uploading serpextract_a8c-0.8.0.tar.gz
    

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@msukmanowsky

Copy link
Copy Markdown
Contributor

Hi @xyu! Former Parsely employee here and original author for serpextract. I'm happy to move ownership of the PyPI Project to you / the Automattic team instead of you deploying a shadow version. (I was pinged on this PR).

@xyu

xyu commented Oct 28, 2026

Copy link
Copy Markdown
Member Author

@msukmanowsky that would be amazing can you move ownership to https://pypi.org/user/parsely/?

@msukmanowsky

Copy link
Copy Markdown
Contributor

@xyu invite sent!

@xyu xyu closed this Oct 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants