Allow authors to use different email addresses in different PEPs

[msullivan]

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/

[AA-Turner]

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

[hugovk]

Previously: #3621

[1st1]

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.

Hm, if it's really useful we can map them by some other ID.

But we have a real world use-case here: the PEP we are about to publish is sponsored by the company we work for now, we have to use their email. But we have a bunch of PEPs that were created personally (I have like 8) that I don't want to suddenly show my new work email.

I'd say that having one email <> one name is a very weird restriction and in my current case I'm just not sure what to even do about this.

[AA-Turner]

Is it entirely intractable that you use your current email for the new PEP?

A

[1st1]

Is it entirely intractable that you use your current email for the new PEP?

Well, we've spent months of work on this PEP, it's fair if the employer gets some visibility. It's important. And I think it's in the interest of Python that companies see reason to invest their employees' time into working on PEPs.