Marvelous! We'll be in touch. Many thanks.

I like your work very much. We definitely want to integrate it.
We're all tied up, perhaps to the end of July. We'll stay in
touch with you, though.

There's no rush. I'll continue testing and tweaking the code meanwhile.

Hi kushal-kumaran, I have one issue that maybe you can resolve (I might have done something wrong). I cloned your changes and am testing them for compatibility with Python 2.7 and 3.2. It works fine on 2.7, but after I run the setup.py script on 3.2, I am unable to use PyPDF2. Here's the output (I tried importing just one class and the whole library to no avail):

[knowah@THINK-NJK PyPDF2]$ python
Python 3.2.3 (default, Apr 23 2012, 23:35:30) 
[GCC 4.7.0 20120414 (prerelease)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from PyPDF2 import PdfFileReader
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "PyPDF2/__init__.py", line 1, in <module>
    from pdf import PdfFileReader, PdfFileWriter
ImportError: No module named pdf
>>> import PyPDF2
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "PyPDF2/__init__.py", line 1, in <module>
    from pdf import PdfFileReader, PdfFileWriter
ImportError: No module named pdf

I don't really have experience with Python 3, so I may be at fault here. To install I just ran python setup.py install. Do you know why it would be unable to load the pdf module?

On Sat, Jul 21, 2012 at 12:01:21PM -0700, knowah wrote:
.
.
.

Hi kushal-kumaran, I have one issue that maybe you can resolve (I might have done something wrong). I cloned your changes and am testing them for compatibility with Python 2.7 and 3.2. It works fine on 2.7, but after I run the setup.py script on 3.2, I am unable to use PyPDF2. Here's the output (I tried importing just one class and the whole library to no avail):

[knowah@THINK-NJK PyPDF2]$ python
Python 3.2.3 (default, Apr 23 2012, 23:35:30) 
[GCC 4.7.0 20120414 (prerelease)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from PyPDF2 import PdfFileReader
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "PyPDF2/__init__.py", line 1, in <module>
    from pdf import PdfFileReader, PdfFileWriter
ImportError: No module named pdf
>>> import PyPDF2
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "PyPDF2/__init__.py", line 1, in <module>
    from pdf import PdfFileReader, PdfFileWriter
ImportError: No module named pdf

I don't really have experience with Python 3, so I may be at fault here. To install I just ran python setup.py install. Do you know why it would be unable to load the pdf module?
.
.
.
I probably won't have time to get involved until mid-week.
Feel free to contact the guy yourself; he's at
reply@reply.github.com

@knowah is it possible you ran setup.py with python2 instead of python3? When running under python3, setup.py invokes 2to3, which would have changed the import statement in __init__.py from this:

from pdf import PdfFileReader, PdfFileWriter

to this:

from .pdf import PdfFileReader, PdfFileWriter

The leading dot in .pdf indicates that the import is a package-relative import (PEP 328).

The conversion to absolute imports is one of the conversions done by 2to3. So, there can be one of three problems:

• setup.py was run using python2
• when running python is somehow picking up the wrong version of PyPDF2
• setup.py was run using python3, but something went wrong (seems unlikely, though, if there were no error messages)

@knowah After running into exactly the same issue myself yesterday, just make sure you are not running python from the directory with the PyPDF2 source. During the build process, 2to3 runs and converts the sources, but the converted files go to the build directory, and the original files are left alone. If you run python from the same directory, it will attempt to look at the PyPDF2 package in the current directory, getting the wrong versions of the files.