RetroSearch Browse

Mon Aug 19 22:11:05 CEST 2013 · https://mail.python.org/pipermail/python-dev/2013-August/128032.html

> The most reasonable thing to do would probably be to share the same
> dummy object between setobject.c and dictobject.c, then.

> Raymond, it would be nice if you could take a look!

Thanks, I will look at it shortly.

Raymond

On Sun, Aug 18, 2013 at 11:46 AM, Antoine Pitrou <solipsis at pitrou.net>wrote:

> On Sun, 18 Aug 2013 17:31:24 +0100
> Mark Shannon <mark at hotpy.org> wrote:
> >
> > By giving the dummy object a custom type, the dummy object can be
> > recognised by testing that its type equals PySetDummy_Type (or
> > whatever it is called)
> >
> > See dictobject.c for an implementation of a suitable dummy object.
>
> The most reasonable thing to do would probably be to share the same
> dummy object between setobject.c and dictobject.c, then.
>
> Raymond, it would be nice if you could take a look!
>
> Regards
>
> Antoine.
>
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> http://mail.python.org/mailman/options/python-dev/raymond.hettinger%40gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20130819/064bfdc6/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2013-August/128032.html below:

Use a known unique object for the dummy entry.