Skip to content

Conversation

@msullivan
Copy link
Contributor

@msullivan msullivan commented Jan 30, 2026

The context here is that Yury Selivanov and I have a forthcoming PEP
and would prefer to use our current employer's email addresses for it,
but don't want to change our email addresses on earlier PEPs we've
written. (Obviously this affects more PEPs for Yury than for me :P)

There's no serious technical impediment to supporting this, so I have.

I've tested this locally.


📚 Documentation preview 📚: https://pep-previews--4797.org.readthedocs.build/

The context here is that Yury Selivanov and I have a forthcoming PEP
and would prefer to use our current employer's email addresses for it,
but don't want to change our email addresses on earlier PEPs we've
written. (Obviously this affects more PEPs for Yury than for me :P)

There's no serious technical impediment to supporting this, so I have.

I've tested this locally.
@msullivan msullivan requested a review from AA-Turner as a code owner January 30, 2026 20:58
Copy link
Member

@AA-Turner AA-Turner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure we should do this; the name-email pair serves as a unique identifier for authors. We've already had authors with the same surname, and having some way of mapping authors to PEPs in a unique fashion is a useful property.

A

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