Georges Toth

> I think the ability for it to retry across Elasticsearch instances will be important (though maybe @lmanners or @sim0nx can weigh in, as users). Yes this is definitely important.

I personally agree with @xilopaint that 0.1.0 is best here. I see it very well as fork of the prod-ready pypdf2 but also as a restart, new project, many changes...

> What I have to say in regard to 0.1.0 is ... oops: https://pypi.org/project/PyPDF4/1.27.0/ Is there any realistic way we can move from 1.27.0 to 0.1.0? Hmm it is possible...

@newnone I suggested 0.0.1 just for testing... if it works, delete it again and publish the first version as 0.1.0 ... :-)

> I'm finally back, and ready to dig into PyPDF4. +1 > Is there any need to maintain compatibility still with 2.7? 3.5? I would definitely drop 2.7 and target...

I am not sure which image / path it is exactly; not sure how I would find that out. The first object-id/generation that is affected is (3,0). It seems like...

Hi, What python version are you using ? Where does that *manifest.json* come from ?

It would be nice if you could support web-server authentication... that would allow for easy OIDC or other auth support.

I fully agree with you. Haven't used or seen such usage in Python outside debugging. Reading through https://mail.python.org/pipermail/python-list/2013-November/660568.html , especially the point that assert can be compiled away (through optimisations)...