Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #32569 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2012-11-02 05:53 +1100 |
| Last post | 2012-11-02 05:53 +1100 |
| 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: Negative array indicies and slice() Chris Angelico <rosuav@gmail.com> - 2012-11-02 05:53 +1100
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2012-11-02 05:53 +1100 |
| Subject | Re: Negative array indicies and slice() |
| Message-ID | <mailman.3162.1351796038.27098.python-list@python.org> |
On Thu, Nov 1, 2012 at 10:32 PM, Andrew Robinson <andrew3@r3dsolutions.com> wrote: > presently slice() allows memory leaks through GC loops. Forgive me if I've missed something here, but isn't it only possible to make a refloop by decidedly abnormal behaviour? Stuff like: a=[]; a.append(slice(a)) Seriously, who does this? First you have to have a reference to a container in place of an index, and then you have to retain the slice object inside that same container as well. Neither operation is normal use of a slice. Where is the problem? ChrisA
Back to top | Article view | comp.lang.python
csiph-web