Author takluyver
Recipients Devin Jeanpierre, barry, eric.araujo, eric.snow, mark.dickinson, martin.panter, mbussonn, meador.inge, michael.foord, petri.lehtinen, serhiy.storchaka, takluyver, terry.reedy, trent, vstinner
Date 2018-05-18.07:48:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526629729.6.0.682650639539.issue12486@psf.upfronthosting.co.za>
In-reply-to
Content
I wouldn't say it's a good name, but I think the advantage of documenting an existing name outweighs that. We can start (or continue) using generate_tokens() right away, whereas a new name presumably wouldn't be available until Python 3.8 comes out. And we usually don't require a new Python version until a couple of years after it is released.

If we want to add better names or clearer APIs on top of this, great. But I don't want that discussion to hold up the simple step of committing to keep the existing API.
History
Date User Action Args
2018-05-18 07:48:49takluyversetrecipients: + takluyver, barry, terry.reedy, mark.dickinson, vstinner, Devin Jeanpierre, trent, eric.araujo, michael.foord, meador.inge, eric.snow, petri.lehtinen, martin.panter, serhiy.storchaka, mbussonn
2018-05-18 07:48:49takluyversetmessageid: <1526629729.6.0.682650639539.issue12486@psf.upfronthosting.co.za>
2018-05-18 07:48:49takluyverlinkissue12486 messages
2018-05-18 07:48:49takluyvercreate