Skip to content

Conversation

@di
Copy link
Member

di commented Jan 22, 2026

How is this going to work on PyPI for URLs like:

@miketheman
Copy link
Member Author

Good callout - hadn't thought of those, I was so excited to see something available 😓

I'll convert to draft to continue iterating on this - it might be something where we'd look at prefixes or something to make the description anchors distinct from the "outer" anchors.

@miketheman miketheman marked this pull request as draft January 22, 2026 21:30
@di
Copy link
Member

di commented Jan 22, 2026

I did mention it here but that was almost eight years ago, so I don't blame you for missing it 😂

I think switching to a prefix for PyPI + finding a way to prevent anchors with those prefixes from being rendered here is probably a good option.

@miketheman
Copy link
Member Author

Thanks @di - definitely missed that! 🙈

I'm considering a non-pypi-specific prefix of user-content- so that if anyone else uses the library (no clue who, but hey, they might) aren't "polluted" with a PyPI string.

... finding a way to prevent anchors with those prefixes from being rendered here ...

I don't understand your meaning here. Why wouldn't we want to render anchors with prefixes?
Unless you were thinking that we change the anchors on PyPI's project pages?

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support internal links in markdown long_descriptions Should warn about relative URLs in links and images

2 participants