[issue18744] pathological performance using tarfile

2013-08-16 Thread K Richard Pixley
K Richard Pixley added the comment: I see your point. The alternative would be to limit the size of archive that can be extracted from to the size of virtual memory, which is essentially what I'm doing manually. Either way, someone will be surprised. I'm not which which way will result

[issue18744] pathological performance using tarfile

2013-08-15 Thread K Richard Pixley
K Richard Pixley added the comment: New info... I see the degradation on most of the linux boxes I've tried: * ubuntu-13.04, (raring), 64-bit * rhel-5.4 64-bit * rhel-5.7 64-bit * suse-11 64-bit I see some degradation on MacOsX-10.8.4 but it's in the acceptable range, more like 2x than 60x

[issue18744] pathological performance using tarfile

2013-08-15 Thread K Richard Pixley
K Richard Pixley added the comment: Here's a script that tests for the problem. -- Added file: http://bugs.python.org/file31303/tarproblem.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18744

[issue18744] pathological performance using tarfile

2013-08-14 Thread K Richard Pixley
New submission from K Richard Pixley: There's a problem with tarfile. Write a program to traverse the contents of a modest sized tar archive. Make sure your tar archive is compressed. Then read the tar archive with your program. I'm finding that allowing tarfile to read a compressed

[issue13590] extension module builds fail with python.org OS X installers on OS X 10.7 and 10.6 with Xcode 4.2

2012-02-08 Thread K Richard Pixley
K Richard Pixley r...@noir.com added the comment: I think a better solution that declaring it to be apple's bug would be to release one binary for pre-10.7, (or maybe 10.6 with the current xcode), and a different binary for post-10.7. This isn't an apple bug in the sense that there's anything

[issue13749] socketserver can't stop

2012-01-09 Thread K Richard Pixley
New submission from K Richard Pixley r...@noir.com: Once I've instantiated my server class, along with a handler class, called server.serve_forever(), handler.handle() has been called, I've done my work, and I'm ready to shut the whole thing down... How do I do that? The doc says

[issue13749] socketserver can't stop

2012-01-09 Thread K Richard Pixley
K Richard Pixley r...@noir.com added the comment: It appears as though the problem is that shutdown() blocks waiting for the serve_forever loop to terminate, which won't happen as long as the process is blocked on shutdown. I'd like to propose that the library be changed to eliminate

[issue13749] socketserver can't stop

2012-01-09 Thread K Richard Pixley
K Richard Pixley r...@noir.com added the comment: On second thought, my proposal is likely to break existing code, so I withdraw it. I don't know how to exit the server in a way that both works in all conditions and also continues to support existing semantics. I expect we'll need to create

[issue13590] Prebuilt python-2.7.2 binaries for macosx can not compile c extensions

2011-12-12 Thread K Richard Pixley
New submission from K Richard Pixley r...@noir.com: Install the Python-2.7.2 mac installer for Lion on Lion. Then attempt easy_install -U psutil. I get: za-dc-dev/bin/easy_install -U psutil install_dir /Users/rich/projects/za-packages/za-dependency-checker/za-dc-dev/lib/python2.7/site

[issue11203] gzip doc is behind

2011-06-07 Thread K Richard Pixley
K Richard Pixley r...@noir.com added the comment: My point was for python-2.7. I haven't stumbled into the buffer protocol yet. So no, it doesn't really. I still think the documentation, especially the 2.7 doc, could be more explicit. My concern here is with the use of close() becoming

[issue11203] gzip doc is behind

2011-06-07 Thread K Richard Pixley
K Richard Pixley r...@noir.com added the comment: An interesting point, although I think that's only relevant if the documentation lists the ABC and a reference to it. (python-3 doc essentially does this.) I see no such reference in the 2.7 gzipfile doc, which leads me to believe, (from

[issue11203] gzip doc is behind

2011-06-07 Thread K Richard Pixley
K Richard Pixley r...@noir.com added the comment: I didn't miss it. I think the close call needs equal treatment to the open call. The mention is certainly present, but seems implicit to me. I would prefer to see it listed explicitly. But I also don't think it's important enough in the 2.7

[issue11203] gzip doc is behind

2011-06-07 Thread K Richard Pixley
K Richard Pixley r...@noir.com added the comment: I'm now convinced this isn't worth fixing in 2.x. -- resolution: - wont fix status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11203

[issue12021] mmap.read requires an argument

2011-05-06 Thread K Richard Pixley
New submission from K Richard Pixley r...@noir.com: mmap.read requires a argument. Since most file-like objects do not, this breaks the file-like object illusion. mmap.read argument should be optional, presumably defaulting to the entire mmap'd area. -- messages: 135362 nosy: rich

[issue3860] GzipFile and BZ2File should support context manager protocol

2011-02-12 Thread K Richard Pixley
K Richard Pixley r...@noir.com added the comment: Documentation needs to be updated to state that these are now context managers. This is important since they aren't in python-2.x. I'm not sure whether this should be added to the new in python blurbs. -- nosy: +teamnoir

[issue11203] gzip doc is behind

2011-02-12 Thread K Richard Pixley
New submission from K Richard Pixley r...@noir.com: The documentation for gzip should include the close method. It's use in the 2.7 documentation implies it's existence but it should also be stated explicitly that it exists. In the 3.x documentation, the use of close not in the examples since

[issue4489] shutil.rmtree is vulnerable to a symlink attack

2010-12-21 Thread K Richard Pixley
K Richard Pixley r...@noir.com added the comment: How does rm -rf address this issue? Or does it? shutils.rmtree should probably do the same thing. -- nosy: +teamnoir ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4489