Re: Looking for ideas to improve library API

From	Devin Jeanpierre <jeanpierreda@gmail.com>
Newsgroups	comp.lang.python
Subject	Re: Looking for ideas to improve library API
Date	2015-11-28 03:31 -0800
Message-ID	<mailman.186.1448710315.20593.python-list@python.org> (permalink)
References	<CABMb9Gu+m9cJXQavXwxc0iouhsKsFSFKVvepLXhJcorc8aUkRw@mail.gmail.com> <CABicbJJkNCTW6PAWw_P5mQmHAwysJaG49N8C+zLV9vKQkWB8_Q@mail.gmail.com> <CABMb9GtR_WVngUUmNAVP83vXJbUZK40REfUBeBpCn3XL2YFaPw@mail.gmail.com>

Show all headers | View raw

Documentation is all you can do.

-- Devin

On Thu, Nov 26, 2015 at 5:35 AM, Chris Lalancette <clalancette@gmail.com> wrote:
> 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

Thread

Re: Looking for ideas to improve library API Devin Jeanpierre <jeanpierreda@gmail.com> - 2015-11-28 03:31 -0800

csiph-web