{5} Assigned, Active Tickets by Owner (Full Description) (9 matches)

From John L. Scarfone <j0@cox.net>:

In using pyPdf1.9 I noticed an issue with rendering a PDF in Acroread 7. I didn't notice the issue in xpdf but Acroread is less forgiving of errors. I traced the error to the fact that in at least one place pyPdf assumes there's always a LF after a CR. Below is a diff that works for me. I haven't investigated any other places in the code where this assumption is made. The PDF I have was originally from some HP scanner and uses bare CRs as line termination. Just reading it in and writing it out causes the first character of the streams to get chopped.

Patch:

--- pyPdf-1.9/pyPdf/generic.py  Fri Dec 15 16:58:08 2006
+++ /home/johns/downloads/pyPdf-1.9/pyPdf/generic.py    Wed Feb  7 20:34:22 2007
@@ -358,7 +358,9 @@
             assert eol in ("\n", "\r")
             if eol == "\r":
                 # read \n after
-                stream.read(1)
+                peek = stream.read(1)
+                if peek != "\n":
+                    stream.seek(-1, 1)
             # this is a stream object, not a dictionary
             assert data.has_key("/Length")
             length = data["/Length"]

The first database I tried connecting to with pg8000 uses SQL_ASCII for the default encoding. The string 'SQL_ASCII' ends up being passed directly to unicode() as client_encoding, resulting in the following traceback:

>>> db = pg8000.Connection(host='localhost', user='pgsql', database='testdb', port=5435)
>>> cursor = pg8000.Cursor(db)
>>> cursor.execute("select label from tbl_test")
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "pg8000.py", line 607, in execute
    self._stmt.execute(*args)
  File "pg8000.py", line 493, in execute
    self._fill_cache()
  File "pg8000.py", line 502, in _fill_cache
    end_of_data, rows = self.c.fetch_rows(self._portal_name, self.row_cache_size, self._row_desc)
  File "pg8000.py", line 1277, in fetch_rows
    rows.append(
  File "pg8000.py", line 1470, in py_value
    return func(v, **kwargs)
  File "pg8000.py", line 1543, in varcharin
    return unicode(data, client_encoding)
LookupError: unknown encoding: SQL_ASCII

I'm using version 1.02.

Scale page content. This could possibly be very easy by wrapping the content with a transformation matrix. Translation will probably also be necessary - target the ability to scale four pages onto one page.

Interested users: Andreas Reuleaux <reuleaux@web.de>

Add support for interval datatype, input and output, and ideally Python-side calculations.

Create an engine file, or modify the existing SQLAlchemy/psycopg2 engine, to allow SQLAlchemy to use pg8000. The goal should be to make all SQLAlchemy tests pass with the new driver. This will stress the DB-API implementation as well which is great for finding new bugs.