Enhance contribution and use without docker

[s-pace]

Introducing the use of pipenv to ease the way to use our tool outside Docker

cc #403

[pixelastic]

And you should also remove requirements.txt now that we have Pipfile, it's no longer needed.

[pixelastic]

Ah wait, you need to update the Travis scripts before merging. They use requirements.txt. They now need to use pipenv

[s-pace]

let's keep requirement.txt then. It is pretty convenient for both usage.

[pixelastic]

Having both a Pipfile and a requirements.txt will be confusing for new users (as they might install the wrong set of dependencies), and we will also have trouble keeping them in sync. Pipfile being a better alternative than requirements.txt we should make sure that our CI uses this setup.

Do you need help with that?

[s-pace]

@pixelastic makes sense. Please update Travis then. I do not know how to do it.

🙏

[pixelastic]

Ok, I'll have a look.

[pixelastic]

@s-pace @maxiloc Could you re-explain how DocSearch works with the different python versions?

I see that the new Pipfile uses python 2.7, and I know I can only run ./docsearch personally when I'm using python 2.7. But I see that the Travis build sets a USE_PYTHON3 to true and the subsequent docker image create uses python 3 for the tests. I also see we have a bunch of compatibility layers (future, six).

Why do we have this mix of python 2 and 3, and what is the recommended version for running DocSearch? My understanding was that DocSearch uses mostly python 2, but we would like to move to python 3 at some point, but the code would need a big rehaul to do so. Could you clarify the current state?

Thanks!

[s-pace]

The scraper only works with python 2.7. I do not know why this env is set

[s-pace]

Closing it in favor of #411