Message 315669 - Python tracker

Message315669

Author	gvanrossum
Recipients	gvanrossum, josh.r, levkivskyi, rhettinger, sproshev
Date	2018-04-23.15:04:18
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CAP7+vJKHyXa46QKabe-Lg4pj+P7HHU2Qyjuc=D5zynVaRee-oA@mail.gmail.com>
In-reply-to	<1524486581.79.0.682650639539.issue33315@psf.upfronthosting.co.za>

Content
Could you please product a draft PR showing how that would work? It might not be accepted right away but it would be useful to have. On Mon, Apr 23, 2018, 05:29 Semyon Proshev <report@bugs.python.org> wrote: > > Semyon Proshev <s-proshev@ya.ru> added the comment: > > I had been thinking about `__class_getitem__` when the issue were created. > > I suspected it's not difficult to implement and it follows PEP 560. > So I'm +1 for `__class_item__`, quotes and postponed evaluation are also > ok. > > ---------- > > _______________________________________ > Python tracker <report@bugs.python.org> > <https://bugs.python.org/issue33315> > _______________________________________ >

Content

Could you please product a draft PR showing how that would work? It might
not be accepted right away but it would be useful to have.

On Mon, Apr 23, 2018, 05:29 Semyon Proshev <report@bugs.python.org> wrote:

>
> Semyon Proshev <s-proshev@ya.ru> added the comment:
>
> I had been thinking about `__class_getitem__` when the issue were created.
>
> I suspected it's not difficult to implement and it follows PEP 560.
> So I'm +1 for `__class_item__`, quotes and postponed evaluation are also
> ok.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue33315>
> _______________________________________
>

History
Date	User	Action	Args
2018-04-23 15:04:18	gvanrossum	set	recipients: + gvanrossum, rhettinger, josh.r, levkivskyi, sproshev
2018-04-23 15:04:18	gvanrossum	link	issue33315 messages
2018-04-23 15:04:18	gvanrossum	create