Be careful though, comparing these to plain integers should probably be allowed, and we also should make sure that things like serialization via JSON or storing in an SQL database don't break. I personally think it's one of those "learn not to touch the stove" cases and there's limited value in making this API idiot proof.
On Sun, Sep 25, 2016 at 9:05 PM, Nick Coghlan <ncogh...@gmail.com> wrote: > On 26 September 2016 at 10:21, MRAB <pyt...@mrabarnett.plus.com> wrote: >> On 2016-09-26 00:21, Ben Leslie wrote: >>> Are there any downsides to this? I've made some progress developing a >>> patch to change this functionality. Is it worth polishing and >>> submitting? >>> >> An alternative might be a subclass of int. > > It could make sense to use a subclass of int that emitted deprecation > warnings for integer arithmetic, and then eventually disallowed it > entirely. > > Cheers, > Nick. > > -- > Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/guido%40python.org -- --Guido van Rossum (python.org/~guido) _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
