[SPIKE] Make micropipenv an alternative to Pipenv

[fridex]

Is your feature request related to a problem? Please describe.

See upstream discussions as this one pypa/pipenv#2873 (still active comments in 2020). Pipenv seems to be slow in some cases and inaccurate (see for example thoth-station/adviser#1613).

Describe the solution you'd like

I was wondering how expensive and complicated it would be to make micropipenv an alternative to Pipenv. We could take a look at pip's new resolver (available in pip>=20.3) and see if the interface is easy to reuse to create a lightweight alternative to Pipenv.

Describe alternatives you've considered

Use Pipenv.

Additional context

This is solely a spike and just heads up on this topic. I'm not sure now how complicated the change would be and if we could seamlessly reuse the new pip's resolver.

[fridex]

Friendly ping to pip/Pipenv folks if this would be something interesting to them.

@pradyunsg @uranusjr

[uranusjr]

You probably want to talk to pip-tools maintainers, who are working to change their resolver to use pip’s new resolver as well IIUC.

[fridex]

You probably want to talk to pip-tools maintainers, who are working to change their resolver to use pip’s new resolver as well IIUC.

Thanks for the reply. Sounds like the idea is not novel and we could eventually combine efforts. Thanks!

[fridex]

Related: pypa/pipenv#4587 (comment)

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[fridex]

/remove-lifecycle stale

[goern]

/priority important-soon

[goern]

/kind feature
/sig docs