Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #63743
| Date | 2014-01-11 18:44 -0800 |
|---|---|
| From | Ethan Furman <ethan@stoneleaf.us> |
| Subject | Re: Python 3 __bytes__ method |
| References | <52D1E0CE.5030906@stoneleaf.us> <CACoeR0yZMGG8zsYKmF4MBjjeh3G-CUpYRbsBdNsufVNkjiap0g@mail.gmail.com> <52D1E830.8070305@stoneleaf.us> <CACoeR0zm6LMAVnoh4y1_pna9rc3+P_cL_u=2FavBz0DL42ehnA@mail.gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.5352.1389494690.18130.python-list@python.org> (permalink) |
On 01/11/2014 06:19 PM, Daniel da Silva wrote: > > One use case is: > Suppose you have existing function that accepts a /bytes/ object. If you subclass /bytes/ and want it to be guaranteed > to work with that function, you can override/__bytes__()/ to use the logistics of your subclass implementation. I don't think so, for two reasons: 1) bytes objects do not have a __bytes__ method, 2) if the function is expecting a bytes object, it is unlikely to call bytes() on it. -- ~Ethan~
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Python 3 __bytes__ method Ethan Furman <ethan@stoneleaf.us> - 2014-01-11 18:44 -0800
csiph-web