Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #99575
| From | Chris Lalancette <clalancette@gmail.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Looking for ideas to improve library API |
| Date | 2015-11-26 08:35 -0500 |
| Message-ID | <mailman.139.1448545321.20593.python-list@python.org> (permalink) |
| References | <CABMb9Gu+m9cJXQavXwxc0iouhsKsFSFKVvepLXhJcorc8aUkRw@mail.gmail.com> <CABicbJJkNCTW6PAWw_P5mQmHAwysJaG49N8C+zLV9vKQkWB8_Q@mail.gmail.com> |
On Thu, Nov 26, 2015 at 7:46 AM, Devin Jeanpierre <jeanpierreda@gmail.com> wrote: > Why not take ownership of the file object, instead of requiring users > to manage lifetimes? Yeah, I've kind of been coming to this conclusion. So my question then becomes: how do I "take ownership" of it? I already keep a reference to it, but how would I signal to the API user that they should no longer use that file object (other than documentation)? Thanks, Chris
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Looking for ideas to improve library API Chris Lalancette <clalancette@gmail.com> - 2015-11-26 08:35 -0500
csiph-web