Closed jbremer closed 2 years ago
ahah, we should have communicate. I am currently working in the same way, have a cmd tool and have a full lib capabilities. You can check this out here I don't consider it yet finish so I did not PR yet. Main changes are :
I don't consider it as finish because, for example, all pylibemu features are accessible only through peepdf interactive console, and I would like to access it directly.
About the update process, I understood that @jesparza want an internal process to update the tool, so the pip
process seems to don't fit his expectations. But let's talk about it here #56 to centralized the discussion :)
One step at a time :-)
@Titotix I did a major refactoring of stuff which will most likely make merging your commits a bit harder.. see also https://github.com/jbremer/peepdf/commit/628ddc98175dc21ab1595591a51c0ca02f00c755
Would be nice if we can merge this PR. Thanks a lot !
Amazing, thanks for maintaining the library on Pypi ! :tophat:
Hi @jesparza, @Titotix,
This PR includes both PRs from @Titotix and some more love in order to make
peepdf
a true Python package, with its core library accessible throughimport peepdf
and thepeepdf.py
command exposed as the global (or local in case ofvirtualenv
)peepdf
command.In addition to that this PR modifies a few minor things:
0.3.1
). This will have to be increased for every release you do.pip install -U peepdf
.$GIT/errors.txt
to~/.peepdf-error.txt
.I think that's most of it. Now I'd be very happy if you could merge this PR and upload it to PyPI (
python setup.py register
&&python setup.py sdist upload
). I'm also happy to do that for you, but as you're the developer of this library I think it would make most sense if you handle this yourself.Let me know if there are any questions.
Regards, Jurriaan