pypng - Project Hosting on Google Code

Yesterday 40 hours ago r206 (Documented the Image class. ) committed by d...@pobox.com - Documented the Image class. Documented the Image class. Last 7 days Jan 05, 2010 r205 (Implemented file descriptor for from_array and some tests. ) committed by d...@pobox.com - Implemented file descriptor for from_array and some tests. Implemented file descriptor for from_array and some tests. Jan 05, 2010 r204 (First implementation of from_array. For issue 57. ) committed by d...@pobox.com - First implementation of from_array. For issue 57. First implementation of from_array. For issue 57. Jan 05, 2010 pypng-0.0.11.tar.gz (Release 0.0.11) file uploaded by d...@pobox.com Jan 05, 2010 r203 (Updates for release 0.0.11 ) committed by d...@pobox.com - Updates for release 0.0.11 Updates for release 0.0.11 Jan 05, 2010 r202 (Edited "how fast is PyPNG?" ) committed by d...@pobox.com - Edited "how fast is PyPNG?" Edited "how fast is PyPNG?" Jan 05, 2010 r201 (png.py command line option -d to set bit-depth on output tes...) committed by d...@pobox.com - png.py command line option -d to set bit-depth on output test image. png.py command line option -d to set bit-depth on output test image. Jan 02, 2010 r200 (tRNS PNGs now generate arrays for rows. And a test to check...) committed by d...@pobox.com - tRNS PNGs now generate arrays for rows. And a test to check that. tRNS PNGs now generate arrays for rows. And a test to check that. Jan 02, 2010 r199 (Added the "How fast is PyPNG?" document. ) committed by d...@pobox.com - Added the "How fast is PyPNG?" document. Added the "How fast is PyPNG?" document. Jan 02, 2010 r198 (Interlaced PNGs now produce arrays for rows. ) committed by d...@pobox.com - Interlaced PNGs now produce arrays for rows. Interlaced PNGs now produce arrays for rows. Jan 02, 2010 r197 (Test that determines that row returned from interlaced PNG i...) committed by d...@pobox.com - Test that determines that row returned from interlaced PNG is array.array. Test that determines that row returned from interlaced PNG is array.array. Last 30 days Dec 30, 2009 r196 (Removing use of "itertoools" module. Which never existed. ) committed by d...@pobox.com - Removing use of "itertoools" module. Which never existed. Removing use of "itertoools" module. Which never existed. Dec 30, 2009 r195 (Very minor doc improvement. ) committed by d...@pobox.com - Very minor doc improvement. Very minor doc improvement. Dec 30, 2009 r194 (Typo. ) committed by d...@pobox.com - Typo. Typo. Dec 27, 2009 issue 57 (Too much code need for writing image file.) reported by d...@pobox.com - When there's just one image file to write from an array, too much code is required. Ian Witham says this (in http://ianwitham.wordpress.com/2009/12/12/pypng-and-the-gimp/ ): PIL: # convert array to 8-bit integers imgarray = np.array(imgArray, np.uint8) # create the image object # "L" is the greyscale mode (luminance) img = Image.fromarray(imgarray, "L") # saving is easy img.save("myFileName.png", "PNG") PyPNG: # PyPNG works with "Writer" objects rather than "Image" objects imgWriter = png.Writer(WIDTH, HEIGHT, greyscale=True, alpha=False, bitdepth=16) # A file must be opened for binary writing ("wb") explicitly f = open("myFileName.png", "wb") # ImgWriter expects a list of lists (rows and columns) as input, # but a numpy array works just as well. # RGB images (a 3D array) require array the to be reshaped into a 2D array first. imgWriter.write(f, imgarray) # remember to close the file! f.close() -- It strikes me that using a PIL style API we could get away with two lines of code: png.fromarray(array, 'L') png.save('foo.png') When there's just one image file to write from an array, too much code is required. Ian Witham says this (in http://ianwitham.wordpress.com/2009/12/12/pypng-and-the-gimp/ ): PIL: # convert array to 8-bit integers imgarray = np.array(imgArray, np.uint8) # create the image object # "L" is the greyscale mode (luminance) img = Image.fromarray(imgarray, "L") # saving is easy img.save("myFileName.png", "PNG") PyPNG: # PyPNG works with "Writer" objects rather than "Image" objects imgWriter = png.Writer(WIDTH, HEIGHT, greyscale=True, alpha=False, bitdepth=16) # A file must be opened for binary writing ("wb") explicitly f = open("myFileName.png", "wb") # ImgWriter expects a list of lists (rows and columns) as input, # but a numpy array works just as well. # RGB images (a 3D array) require array the to be reshaped into a 2D array first. imgWriter.write(f, imgarray) # remember to close the file! f.close() -- It strikes me that using a PIL style API we could get away with two lines of code: png.fromarray(array, 'L') png.save('foo.png') Older Oct 23, 2009 issue 56 (read_flat broken) commented on by d...@pobox.com - release 0.0.10 should be available on the downloads page. Hmm. This is all documented in the release procedure. I wonder how I get myself to follow the procedure all the way to the end? release 0.0.10 should be available on the downloads page. Hmm. This is all documented in the release procedure. I wonder how I get myself to follow the procedure all the way to the end? Oct 23, 2009 pypng-0.0.10.tar.gz (Release 0.0.10) file uploaded by d...@pobox.com Oct 23, 2009 issue 56 (read_flat broken) commented on by d...@pobox.com - Oops. (there is one on PyPI http://pypi.python.org/pypi/pypng/ ). Adding it to google now. Oops. (there is one on PyPI http://pypi.python.org/pypi/pypng/ ). Adding it to google now. Oct 21, 2009 issue 56 (read_flat broken) commented on by nornagon - There doesn't seem to be a download for 0.0.10 on the downloads page... There doesn't seem to be a download for 0.0.10 on the downloads page... Oct 12, 2009 issue 56 (read_flat broken) commented on by d...@pobox.com - Try release 0.0.10 where this should be fixed. Try release 0.0.10 where this should be fixed. Oct 12, 2009 r193 (notes for 0.0.10 ) committed by d...@pobox.com - notes for 0.0.10 notes for 0.0.10 Oct 12, 2009 r192 (rev for version 0.0.10 ) committed by d...@pobox.com - rev for version 0.0.10 rev for version 0.0.10 Oct 12, 2009 r191 (Re-ordered release proc ) committed by d...@pobox.com - Re-ordered release proc Re-ordered release proc Oct 12, 2009 r190 (unimplemented documentation ) committed by d...@pobox.com - unimplemented documentation unimplemented documentation Oct 12, 2009 issue 56 (read_flat broken) changed by d...@pobox.com - This issue was closed by revision r189. Status: Fixed This issue was closed by revision r189. Status: Fixed Oct 12, 2009 r189 (Fixes Issue 56. ) committed by d...@pobox.com - Fixes Issue 56 . Fixes Issue 56 . Oct 12, 2009 r188 (Removing redundant variable. ) committed by d...@pobox.com - Removing redundant variable. Removing redundant variable. Oct 12, 2009 issue 56 (read_flat broken) Status changed by d...@pobox.com - I have reproduced this. Status: Accepted I have reproduced this. Status: Accepted Oct 10, 2009 issue 56 (read_flat broken) reported by nornagon - What steps will reproduce the problem? p = png.Reader(file=open('foo.png')) # where foo.png is non-interlaced r = p.read_flat() What is the expected output? What do you see instead? I should get the pixels in flat array format. Instead: Traceback (most recent call last): File "<stdin>", line 1, in <module> File "pypng-0.0.9/build/lib/png.py", line 1699, in read_flat pixels = self.serialtoflat(self.straightlaced(packedlines)) AttributeError: Reader instance has no attribute 'straightlaced' What version of the product are you using? On what operating system? 0.0.9 on OS X 10.6.1 What steps will reproduce the problem? p = png.Reader(file=open('foo.png')) # where foo.png is non-interlaced r = p.read_flat() What is the expected output? What do you see instead? I should get the pixels in flat array format. Instead: Traceback (most recent call last): File "<stdin>", line 1, in <module> File "pypng-0.0.9/build/lib/png.py", line 1699, in read_flat pixels = self.serialtoflat(self.straightlaced(packedlines)) AttributeError: Reader instance has no attribute 'straightlaced' What version of the product are you using? On what operating system? 0.0.9 on OS X 10.6.1 Sep 30, 2009 r187 (Typos in doc string. ) committed by d...@pobox.com - Typos in doc string. Typos in doc string. Jun 17, 2009 issue 54 (Deprecation warnings when using pypng.) commented on by d...@pobox.com - @vishpat: Thanks for that. So far I have not been able to reproduce this. But I made a change to fix it anyway (r183). This is incorporated into release 0.0.9: http://code.google.com/p/pypng/downloads/list Could you please try that? And report back here in this issue. Thanks. @vishpat: Thanks for that. So far I have not been able to reproduce this. But I made a change to fix it anyway (r183). This is incorporated into release 0.0.9: http://code.google.com/p/pypng/downloads/list Could you please try that? And report back here in this issue. Thanks. Jun 16, 2009 issue 54 (Deprecation warnings when using pypng.) commented on by vishpat - Warning the was produced on the "google app engine" platform and following are the messages from the console log # 06-14 07:16AM 39.185 /base/data/home/apps/charmo-meter/1.334199149815290197/charmometer/png.py:1133: DeprecationWarning: 'i' format requires -2147483648 <= number <= 21474 # E 06-14 07:16AM 39.185 verify = struct.pack('!i', verify) # E 06-14 07:16AM 39.186 /base/data/home/apps/charmo-meter/1.334199149815290197/charmometer/png.py:943: DeprecationWarning: 'i' format requires -2147483648 <= number <= 214748 # E 06-14 07:16AM 39.186 outfile.write(struct.pack("!i", checksum)) Warning the was produced on the "google app engine" platform and following are the messages from the console log # 06-14 07:16AM 39.185 /base/data/home/apps/charmo-meter/1.334199149815290197/charmometer/png.py:1133: DeprecationWarning: 'i' format requires -2147483648 <= number <= 21474 # E 06-14 07:16AM 39.185 verify = struct.pack('!i', verify) # E 06-14 07:16AM 39.186 /base/data/home/apps/charmo-meter/1.334199149815290197/charmometer/png.py:943: DeprecationWarning: 'i' format requires -2147483648 <= number <= 214748 # E 06-14 07:16AM 39.186 outfile.write(struct.pack("!i", checksum)) Jun 16, 2009 pypng-0.0.9.tar.gz (Release 0.0.9) file uploaded by d...@pobox.com Jun 16, 2009 r186 (Version 0.0.9 ) committed by d...@pobox.com - Version 0.0.9 Version 0.0.9 Jun 16, 2009 r185 (Readme. ) committed by d...@pobox.com - Readme. Readme. Jun 16, 2009 issue 54 (Deprecation warnings when using pypng.) Summary changed by d...@pobox.com - Summary: Deprecation warnings when using pypng. Summary: Deprecation warnings when using pypng. Jun 16, 2009 issue 55 (Cannot convert Plan 9 images.) Status changed by d...@pobox.com - Fixed by r184. Status: Fixed Fixed by r184. Status: Fixed Jun 16, 2009 issue 55 (Cannot convert Plan 9 images.) reported by d...@pobox.com - See http://plan9.bell-labs.com/magic/man2html/6/image for a description of the Plan 9 image format. See http://plan9.bell-labs.com/magic/man2html/6/image for a description of the Plan 9 image format. Jun 15, 2009 r184 (Plan9 image conversion tool. ) committed by d...@pobox.com - Plan9 image conversion tool. Plan9 image conversion tool. Jun 10, 2009 issue 54 (Depreciation warnings will using pypng) Status changed by d...@pobox.com - Status: Started Status: Started Jun 10, 2009 issue 54 (Depreciation warnings will using pypng) Status changed by d...@pobox.com - This issue was closed by r183. Status: Fixed This issue was closed by r183. Status: Fixed Jun 10, 2009 r183 (Coerce crc32 to be positive. Fixes Issue 54? ) committed by d...@pobox.com - Coerce crc32 to be positive. Fixes Issue 54? Coerce crc32 to be positive. Fixes Issue 54? Jun 10, 2009 issue 54 (Depreciation warnings will using pypng) commented on by d...@pobox.com - Could you please provide a transcript of code that produces the warning? In other words a cut and paste from a Terminal window that shows the error. Could you also say what Computer, Operating System, and version of Python you are using? I'll hazard a guess and say you're using a 64-bit machine. From the information provided it looks like it could be related to this problem with the CRC32 computation: http://bugs.python.org/issue1202 Could you please provide a transcript of code that produces the warning? In other words a cut and paste from a Terminal window that shows the error. Could you also say what Computer, Operating System, and version of Python you are using? I'll hazard a guess and say you're using a 64-bit machine. From the information provided it looks like it could be related to this problem with the CRC32 computation: http://bugs.python.org/issue1202 Jun 09, 2009 r182 (Adding defaults to iccp.py. ) committed by d...@pobox.com - Adding defaults to iccp.py. Adding defaults to iccp.py. Jun 09, 2009 issue 54 (Depreciation warnings will using pypng) reported by vishpat - What steps will reproduce the problem? 1. Call the asRGB function of the library What is the expected output? What do you see instead? The following python warnings are seen 1) png.py:1133: DeprecationWarning: 'i' format requires -2147483648 <= number <= 2147483647 2) verify = struct.pack('!i', verify) 3) outfile.write(struct.pack("!i", checksum)) What version of the product are you using? On what operating system? Revision number: 110 Please provide any additional information below. None: What steps will reproduce the problem? 1. Call the asRGB function of the library What is the expected output? What do you see instead? The following python warnings are seen 1) png.py:1133: DeprecationWarning: 'i' format requires -2147483648 <= number <= 2147483647 2) verify = struct.pack('!i', verify) 3) outfile.write(struct.pack("!i", checksum)) What version of the product are you using? On what operating system? Revision number: 110 Please provide any additional information below. None: Jun 09, 2009 r181 (Better API for iccp code. ) committed by d...@pobox.com - Better API for iccp code. Better API for iccp code. Jun 09, 2009 r180 (Moving encoders to iccp module. ) committed by d...@pobox.com - Moving encoders to iccp module. Moving encoders to iccp module. Jun 09, 2009 r179 (put encoder functions into a dict. ) committed by d...@pobox.com - put encoder functions into a dict. put encoder functions into a dict. Jun 09, 2009 r178 (Mostly moving ICC code around. ) committed by d...@pobox.com - Mostly moving ICC code around. Mostly moving ICC code around. Jun 09, 2009 issue 53 (Understanding of zlib protocol is baroque and wrong.) Status changed by d...@pobox.com - This issue was closed by r177. Status: Fixed This issue was closed by r177. Status: Fixed

issue 57 (Too much code need for writing image file.) reported by d...@pobox.com - When there's just one image file to write from an array, too much code is required. Ian Witham says this (in http://ianwitham.wordpress.com/2009/12/12/pypng-and-the-gimp/ ): PIL: # convert array to 8-bit integers imgarray = np.array(imgArray, np.uint8) # create the image object # "L" is the greyscale mode (luminance) img = Image.fromarray(imgarray, "L") # saving is easy img.save("myFileName.png", "PNG") PyPNG: # PyPNG works with "Writer" objects rather than "Image" objects imgWriter = png.Writer(WIDTH, HEIGHT, greyscale=True, alpha=False, bitdepth=16) # A file must be opened for binary writing ("wb") explicitly f = open("myFileName.png", "wb") # ImgWriter expects a list of lists (rows and columns) as input, # but a numpy array works just as well. # RGB images (a 3D array) require array the to be reshaped into a 2D array first. imgWriter.write(f, imgarray) # remember to close the file! f.close() -- It strikes me that using a PIL style API we could get away with two lines of code: png.fromarray(array, 'L') png.save('foo.png')

When there's just one image file to write from an array, too much code is required. Ian Witham says this (in http://ianwitham.wordpress.com/2009/12/12/pypng-and-the-gimp/ ): PIL: # convert array to 8-bit integers imgarray = np.array(imgArray, np.uint8) # create the image object # "L" is the greyscale mode (luminance) img = Image.fromarray(imgarray, "L") # saving is easy img.save("myFileName.png", "PNG") PyPNG: # PyPNG works with "Writer" objects rather than "Image" objects imgWriter = png.Writer(WIDTH, HEIGHT, greyscale=True, alpha=False, bitdepth=16) # A file must be opened for binary writing ("wb") explicitly f = open("myFileName.png", "wb") # ImgWriter expects a list of lists (rows and columns) as input, # but a numpy array works just as well. # RGB images (a 3D array) require array the to be reshaped into a 2D array first. imgWriter.write(f, imgarray) # remember to close the file! f.close() -- It strikes me that using a PIL style API we could get away with two lines of code: png.fromarray(array, 'L') png.save('foo.png')

Yesterday

Last 7 days

Last 30 days

Older