Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #99659 > unrolled thread
| Started by | Devin Jeanpierre <jeanpierreda@gmail.com> |
|---|---|
| First post | 2015-11-28 03:31 -0800 |
| Last post | 2015-11-28 03:31 -0800 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Looking for ideas to improve library API Devin Jeanpierre <jeanpierreda@gmail.com> - 2015-11-28 03:31 -0800
| From | Devin Jeanpierre <jeanpierreda@gmail.com> |
|---|---|
| Date | 2015-11-28 03:31 -0800 |
| Subject | Re: Looking for ideas to improve library API |
| Message-ID | <mailman.186.1448710315.20593.python-list@python.org> |
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 top | Article view | comp.lang.python
csiph-web