pyfpdf | Simple PDF generation for Python | Document Editor library

Solution:

Both should be the same (with minor differences).

I like open way, because it is explicit and shorter, OTOH if you want to handle encoding errors (e.g. a way better error to user), one should use decode/encode (maybe after a '\n'.split(s), and keeping line numbers)

Note: if you use the first method (open), you should just use r or w, so without b. For your question's title, it seems you did correct, but check that your example keep b, and probably for this, it used encoding. OTOH the code seems old, and I think the ".encoding" was just done because it would be more natural in Python2 mindset.

Note: I would also replace strict to backslashreplace for debugging. And possibly you may want to check and print (maybe just ord) of the first few characters of the self.buffer on both methods, to see if there are substantial differences before file.write.

I would add a file.flush() on both functions. This is one of the differences: buffering is different, and I'll make sure I close the file. Python will do it, but when debugging, it is important to see the content of the file as quick as possible (and also after an exception). Garbage collector could not guarantee all of this. Maybe you are reading a text file which was not yet flushed.

I did not find the package to test but I added an init to generate an alphabet list that way you can add it while generating the footer based on the

Most probably you are using Python 3.x where x >= 5 .

On the pypi it says that the module has only experimental support for python 3.y where y <= 4 .

Try it with python 2.7 and it might work.

PS: Better try https://pypi.org/project/fpdf2/, the updated version. For bugs or issues see https://github.com/alexanderankin/pyfpdf .

If you really want to use the old version, you can install whatever version you want from the original repo like this