[Python-Dev] Slice as a copy... by design? (original) (raw)
Facundo Batista facundobatista at gmail.com
Fri May 23 02:07:01 CEST 2008
- Previous message: [Python-Dev] Slice as a copy... by design?
- Next message: [Python-Dev] Slice as a copy... by design?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2008/5/22 Facundo Batista <facundobatista at gmail.com>:
I couldn't answer why, so I'm asking here...Is it because the reference counting will be complicated? Is it because it'd be inefficient in other way? It's something else? Or is something that could be done... but is not done yet?
Thank you all for the information provided!
-- . Facundo
Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/
- Previous message: [Python-Dev] Slice as a copy... by design?
- Next message: [Python-Dev] Slice as a copy... by design?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]