Ellison Marks added the comment:
Erm, is there anyone else we should poke for their opinion then?
--
___
Python tracker
<http://bugs.python.org/issue30
Ellison Marks added the comment:
At a guess, when encoder goes out of scope, it closes the underlying file
object. Then, on exiting the with block, the zipfile tries to take some action
with the closed file and errors out?
--
nosy: +Ellison Marks
Ellison Marks added the comment:
I'm not sure I agree with that. The docs for compressobj just say
"Returns a compression object, to be used for compressing data streams that
won’t fit into memory at once."
Which I don't think says much about the complexity aspect. Whether
Ellison Marks added the comment:
I made a try at a patch for this.
My C is rudimentary at best, so I was hoping someone could look it over before
I submitted a PR?
https://github.com/gotyaoi/cpython/commit/2906fc9069ce6ec4888a547b5088ef9177a21c9a
New submission from Ellison Marks:
In the zlib module, three of the methods support the wbits parameter, those
being zlib.compressobj, zlib.decompress and zlib.decompressobj. zlib.compress
does not support the wbits parameter. Looking at the source for these
functions, those that support the
Ellison Marks added the comment:
Just as an update, I've been working around this by manually setting
TurtleScreen._RUNNING to True before calling Turtle() again, which produces the
desired behaviour in both 3.4 and 3.5. Haven't noticed any bad effe
New submission from Ellison Marks:
I noticed some odd behaviour when running some turtle code I wrote using python
3.5. A simplified example:
>>> from turtle import Turtle
>>> t = Turtle()
>>> t.getscreen().bye() # or manually close the turtle window
>>>
