I made a Python PDF form library
What is the best project structure for a Python application? - Stack Overflow
Python project need free pdf files
Bro had google, but chose reddit instead
More on reddit.com[Project] I made a pdf invoice generator with beautified Tkinter
How to python project report pdf free download?
How to get free python projects with source code pdf?
Videos
» pip install pypdf
Hello folks! I shared an open source project I have been working on for three years at r/Python and got some very positive feedbacks so I'd love to share it here too. It is a Python library that specializes in processing PDF forms, with the most outstanding feature being programmatically filling a PDF form by simply feeding a Python dictionary.
I used to work at a startup company with Python as our backend stack. We were constantly given paper documents by our clients that we needed to generate into PDFs. We were doing it using reportlab scripts and I quickly found the process tedious and time consuming for more complex PDFs.
This is where the idea of this project came from. Instead of writing lengthy and unmaintainable reportlab scripts to generate PDFs, you can just turn any paper document into a PDF form template and PyPDFForm can fill it easily.
Here are some resources for this project:
GitHub: https://github.com/chinapandaman/PyPDFForm
PyPi: https://pypi.org/project/PyPDFForm/
Docs: https://chinapandaman.github.io/PyPDFForm/
A public speak I did about this project: https://www.youtube.com/watch?v=8t1RdAKwr9w
I hope you guys find the library helpful for your own PDF generation workflow. Feel free to try it, test it, leave comments or suggestions, and open issues. And of course if you are willing, kindly give me a star on GitHub.
Doesn't too much matter. Whatever makes you happy will work. There aren't a lot of silly rules because Python projects can be simple.
/scriptsor/binfor that kind of command-line interface stuff/testsfor your tests/libfor your C-language libraries/docfor most documentation/apidocfor the Epydoc-generated API docs.
And the top-level directory can contain README's, Config's and whatnot.
The hard choice is whether or not to use a /src tree. Python doesn't have a distinction between /src, /lib, and /bin like Java or C has.
Since a top-level /src directory is seen by some as meaningless, your top-level directory can be the top-level architecture of your application.
/foo/bar/baz
I recommend putting all of this under the "name-of-my-product" directory. So, if you're writing an application named quux, the directory that contains all this stuff is named /quux.
Another project's PYTHONPATH, then, can include /path/to/quux/foo to reuse the QUUX.foo module.
In my case, since I use Komodo Edit, my IDE cuft is a single .KPF file. I actually put that in the top-level /quux directory, and omit adding it to SVN.
According to Jean-Paul Calderone's Filesystem structure of a Python project:
Project/
|-- bin/
| |-- project
|
|-- project/
| |-- test/
| | |-- __init__.py
| | |-- test_main.py
| |
| |-- __init__.py
| |-- main.py
|
|-- setup.py
|-- README