08.01.2011, 02:20, "Steven D'Aprano" <steve+comp.lang.pyt...@pearwood.info>: > On Fri, 07 Jan 2011 23:54:24 +0200, kost BebiX wrote: > >> 07.01.2011, 17:47, "Steven D'Aprano" >> <steve+comp.lang.pyt...@pearwood.info>;: >>> On Fri, 07 Jan 2011 16:47:55 +0200, kost BebiX wrote: >>>> Well, actually the code you showed doesn't work) >>> Actually, it does. It just prints a warning message as well. Look >>> carefully: > > [...] > >>> I've tested the above code in Python versions 2.4 through 3.2 and the >>> only one that prints that message is 2.6. >> So maybe it should be fixed in 2.6? When I'll have time I'll look at >> copy.py in different python's. Maybe there's the answer) Thanks anyway. > > Before you spend too much (i.e. any) time trying to fix this, I think > that Python 2.6 is now only accepting security fixes. > > http://www.python.org/download/releases/2.6.6/ > > -- > Steven
Too bad (I mean, it's not too bad, because this thing can break other's 2.6 code that somehow depends on that). Now when I'll install 2.7 I'll have to remember about this bug when coding) -- http://mail.python.org/mailman/listinfo/python-list
